Profile cover photo
Profile photo
Shinken
128 followers -
Shinken is an advanced monitoring system that is based on Nagios, but redesigned and rewritten from scratch while maintaining compatibility. It can monitor all IT devices from systems to end user applications. In case of a failure, Shinken can alert the operation engineers so they can promptly repair it. It has the same capabilities as Nagios along with more advanced built-in facilities such as load balanced and high availability monitoring.
Shinken is an advanced monitoring system that is based on Nagios, but redesigned and rewritten from scratch while maintaining compatibility. It can monitor all IT devices from systems to end user applications. In case of a failure, Shinken can alert the operation engineers so they can promptly repair it. It has the same capabilities as Nagios along with more advanced built-in facilities such as load balanced and high availability monitoring.

128 followers
About
Shinken's posts

Post has attachment
Wow, there is a new visualization interface for Shinken available!

Post has attachment
Shinken 2.0 release

The Shinken team is happy to announce the final release of Shinken 2.0.

More information at http://shinkenlab.io/2-0-release/

Once again, an eventful year is coming to a close. We wish you all a peaceful and contemplative holiday season and a successful New Year.

Your Shinken Team

Post has attachment
The new shinken version is out. This version focus on the enhancement of the Web interface, advanced distributed modes, and to dynamically change your thresholds based on the time!

Post has attachment
Livestatus
Did you know that you can choose between SQlite and MongoDB as your logstore for your Livestatus module?

define module{
      module_name      Livestatus
      module_type        livestatus
      host                      *       ; * = listen on all configured ip addresses
      port                      50000   ; port to listen
      socket                  /usr/local/shinken/var/rw/live
      modules               logsqlite
}

Available modules:
- logsqlite: send historical logs to a local sqlite database
- mongologs: send historical logs to a mongodb database
- nulllogs : send historical logs to a black hole


You need more informations? Visit Shinken Forum or Shinken Wiki.

Post has attachment
Using Shinken with Thruk

Requirements:
- A Thruk installation. If you do not have one, have a look at Thruk installation documentation.
- An enabled Livestatus module. If not present, have a look at enable Livestatus module or Google+ Link.

Declaring Shinken peer in Thruk

Edit /etc/thruk/thruk_local.conf and declare the Shinken peer:
    <peer>
       name   = External Shinken
       type   = livestatus
       <options>
           peer    = 127.0.0.01:50000
      </options>
    </peer>

Or use the backend wizard which starts automatically upon first installation.

Don't forget to alter “127.0.0.1” into the IP/name of your broker if it is installed on an different host, or if you are using a distributed architecture with multiple brokers!

Special Thanks to sni

You need more information? Visit Shinken Forum or Shinken Wiki (http://goo.gl/VjzaG).
Feel free to comment!

#shinken #thruk  

Post has attachment
Livestatus and Shinken
It’s pretty easy to enable Livestatus on your Shinken environment.

Step 1: Open shinken-specific.cfg with your favorite editor and find the object “Broker”.

Step 2: Add “Livestatus“ to modules

e.g
define broker{
      broker_name      broker-1
[...]
      modules          Simple-log, Livestatus
}

Step 3: Disable human readable logs. For that, please set the option human_timestamp_log to 0

That's it! If you need more information about Shinken or other awesome modules. Please visit our Forum or Wiki. http://goo.gl/VjzaG

Post has attachment
Send all your logs to a local or remote syslog server in only two steps!

Step 1: Configure your syslog demone on your Shinken Server.

Step 2: Enable the syslog function under shinken-specific.cfg -> BROKER (S1_Broker) by adding Syslog to the modules.

for example:
define broker {
    broker_name broker-1
    address localhost
    port 7772
    spare 0
    ...
    modules Livestatus, Simple-log, WebUI,  Syslog
    ...
}

You need more information? Visit Shinken Forum or Shinken Wiki or leave a comment below.

define broker {
    broker_name Holiday-Wishes
    address 22-12-2012
    port 7772
    spare 0
    modules Xmas, NewYear
    message “We wish you a merry christmas and a happy new year 2013!”
}

Post has attachment
Troubleshooting: How to set my daemons in debug mode to review the logs?

A daemon is a Shinken process. Each daemon generates a log file by default. The daemon configuration is set in the .ini configuration file (e.g. brokerd.ini). Logging is enabled and set to level INFO by default.

Default log file location local_log=%(workdir)s/<daemon-name>.log

The log file will contain information on the Shinken process and any problems the daemon encounters.

Option 1: Changing the log level during runtime

shinken-admin is a command line script that can change the logging level of a running daemon.

linux-server# ./shinken-admin …

Option 2: Changing the log level in the configuration

Edit the <daemon-name>.ini file, where daemon name is pollerd, schedulerd, arbiterd, reactionnerd, receiverd. Set the log level for example to: DEBUG

Possible values: DEBUG, INFO, WARNING, ERROR, CRITICAL

Re-start the Shinken process.

If you are interested in more, you can find out the real power of Shinken daemons and Shinken architecture under following Link http://goo.gl/X7hfO
Wait while more posts are being loaded