Explore the site


Ready to start

Shinken packages will allow you to:

  • Quickly start to monitor your servers and applications
  • Reuse your Nagios configuration
  • Easily apply best practice from the monitoring community
  • Get modules for loading frm new sources (Puppet, Mysql, ...) or new exports (Graphite, PNP4NAgios, ...)
  • Exchange your own best pracices

Get into Shinken.io!

  • AIX
  • Apache
  • Cisco
  • Citrix
  • Collectd
  • Dell
  • EMC
  • Exchange
  • HP
  • IBM
  • Juniper
  • Linux
  • MongoDB
  • Mssql
  • Mysql
  • NetApp
  • Oracle
  • Puppet
  • RedHat
  • Solaris
  • Vmware
  • windows
  • Xen

Extend to the infinity and beyond

  • Extend your monitoring platform

    The monitoring node is do not have what you need? You can easily extend it with configuration packs and modules.

  • Configuration Packs

    The configuration packs are basically nagios configurations files, with templates and commands. If you know how to write Nagios configuration, you know how to write configuration packs.

  • Shinken modules

    Shinken is very flexible and modular. If you want to load your configuration from you specific CMDB or export data into your new performance data tool, you will be able to write modules to do so. Get a look at sample modules, it's in python and it's very easy.


Scale without limits

  • Easy scalability for all

    Discover a world where the scalability is easy and is done by design by the tool. Shinken got no distributed limits, it's done to be scale on your LAN, your DMZ and even across several datacenters!

  • Raid like availability

    You can be sure Shinken won't stop: you can easily define some nodes as spare, and if a mastergoes down, a spare will take the job.

  • Mixed architecturtes

    It's always easier to monitor a Windows from a windows host, and a linux from a linux based server. Hopefully, Shinken won't force you to choose between Linux and Windows, just got both! You will be able to easily checks your windows with the WMI protocol with a domain account (no password!) from a Windows poller, and network and Linux servers from a Linux poller!


DMZ monitoring: no more a security nigthmare!


How to make your security admins happy:

  1. Place a poller in the DMZ
  2. Tag your hosts so they should be checks by the DMZ's poller.
  3. Enjoy : all your connexions will be from LAN to the DMZ for Shinken, and from the DMZ poller to your hosts for the checks. Period.

Learn more about this

Monitor several datacenters? Yes you can

Got a structural view of your datacenters:

  • Got only one central configuration for all your datacenters
  • Got one global view of your monitoring, one on each datacenter, or both!
  • Scale one datacenter or another, it's up to you
  • Organize your self with sub-datacenters to map your internal organization


Focus on your business

  • IT is not important. End users apps are.

    End users apps are delivered through your IT, and this one is shared between very important apps like your mails or your CRM, and low important ones like your dev env. With Shinken you will be able to describe your IT from the physical servers to the high level apps.

  • Find the root problem

    Getting a full page of 500+ red lines is useless if only one is interesting : 499 are for impacts, 1 is for the root problem! Shinken will filter for you all of this, and you will be able to solve your problem in no time. This will also solve your "too much" alerts problems.

  • Sort by the business impact

    Did you remember about an admin running on server room to fix a dev server? No of course. But they will for production ones. You need to get in few second which root problem is impacting a production apps, and which one can wait after your coffee break.

Business rules

Production can't wait. (And only production)

Did you remember about admins running on server room to fix a dev server? No. But replace dev by production and this will change. Your team should focus on production, and manage the others env later. Give them the tools that understand this.

  • Filtering testing/production alerts

    Production need email and/os SMS. But maybe testing env don't need this, or at least no SMS of course. You can now easily filter root problem alarms so you will only receive alarms that need actions, and only them.

  • Day != Night

    You maybe don't care about SMS the day, and email the night. Now you can easily manage such notification canals without having to complexify your configuration.

  • Sometime it's critical for business, sometime it's not

    Let's take a paid application. Do you need to awake an admin at 3PM because the apps is down outside the paid period? No of course, but will need during these period. Now you will be able to define business impact modulation based on the period, like the 3 days during the month for the paid :)

Smart filtering is waiting for you


Because an ESXi host can fail

  • What if an ESXi host crash?

    Why if an ESXi host crash? Do you want to receive 50+ alerts about all your poor VMs that are DOWN, or just one critical alert about the fact that your ESX is DOWN? Only the root problem of course.

    It is what the VMWare module will solve for you : it will automatically look at your vSphere on which ESX are the VM, and create notification dependecies from it.

  • What about VMotion?

    Don't worry about VMotion, if your VM is moved to another ESX, the VMWare module will detect it, and automatically update the link without restart Shinken.

  • VMWare is great, but I use Xen/KVM/OpenStack/...

    No problem for this, in fact Xen and KVM are already managed, and new virtualization framework is easy to add. If it got an API, we can integer it!

EC2 is great. Monitor the apps on theses hosts is great too.

  • Why monitor EC2?

    With the EC2 module you won't monitor EC2 itself, but you will be able to automatically monitor the apps like Mysql or Apache that are running on them.

  • No double configuration

    This module will automatically load all your EC2 instances, and will use the EC2 tags to configure your hosts in Shinken. When your EC2 tags are filled, your configuration is done.

  • Not only EC2

    From now only the EC2 module is available, but can be very easy to extend it to other cloud providers, like Rackspace, OVH or Gandi. Feel free to contribute on The Monitoring Station, we can help you for this.

Learn more

EC2 and Shinken