Icon

Comments have been closed on this page. Please use AppMon & UEM Plugins forum for questions about this plugin.

This plugin allows dynaTrace to send alerts to a Nagios server using NSCA. Alerts can be posted locally or remotely to Nagios. This plugin based on the jsendnsca java library and tested with Nagios, OP5, Icinga.

 Special thanks to Peter Szegedi, who helped me in connection with Nagios and NSCA configuration.

Name

Nagios Alerting Plugin 3.0

Version

3.0.0 (2016.12.20)

dynaTrace Version

>= 6.0

Download

hu.bakaibalazs.dynatrace.nagios.NagiosAlerting_3.0.0.jar

Githubhttps://github.com/dynaTrace/Dynatrace-Nagios-Alerting-Plugin

License

LGPL v3

SupportNot Supported
Author

Balázs Bakai (balazs.bakai@telvice.hu)

www.bakaibalazs.hu

www.bakailab.hu

Telvice Kft.

Release Notes

3.0 - 2016.12.20

- remove not alphanumeric characters from the incident rule name

- add description using this plugin with RedHat7/Centos7 - xinetd based nsca support

- Nagios core, Nagios XI and OP5 support is tested with dynaTrace 6.3

2.0 - 2015.03.26

- Easier configuration

- The additional helper scripts are removed thanks to jsendnsca

- Supports local and remote Nagios server

- Timeouts added as parameter

1.0 - 2014.06.26

- Send "ok" notification to Nagios when the incident ends

Plugin installation

  • Use dynaTrace client to install (Settings/dynaTrace Servers/Plugins/Install Plugin) the attached plugin binary jar file and activate the plugin
  • Click on the properties button and setup the NSCSA and Nagios related parameters of the plugin. (TRIPLE_DES NSCA Encryption is suggested)
  • If you need more information select the FINE log level else the INFO log level. Logs are available at System Information/dynaTrace Server/Support Information/Log Files

Incident Configuration

  • Add the Nagios Action Plugin of each of the incident rule you want to generate Nagios alerts for. (System Profile/Incidents/select an Incident Rule/Edit/Advanced Configuration/add/Nagios Alerting)
  • Important to set up the execution list to: on incident begin and end, so dynaTrace can informs Nagios when an incident starts and finishes.
  • The value of the Action Severity will be sent to the Nagios Server when the inident begins. 
    • dynaTrace Servere => Nagios Critical
    • dynaTrace Warning => Nagios Warning
    • dynaTrace Informational => Nagios OK
  • The value of the Incident Severity will be shown on the dynaTrace Incident dashlet

 

  • You can deviate from the default parameters pressing the edit button, however, TRIPLE_DES encryption is suggested to use.

 

RedHat7 (Centos7) xinetd - nsca support

  • You have to define the IP address of the dynaTrace server at the only_from part of the /etc/xinetd.d/nsca configuration file.

 

  • You have to comment out the server_address in the /usr/local/nsca/nsca.cfg file

            #server_address=192.168.1.1

Nagios Service/Host configuration

  • On the Nagios side, you need to declare the host and the services which you will generate alerts for. The host is arbitrary as you will be able to configure it for each alert you will generate from dynaTrace. The service description on the other hand must match the name of the incident that will trigger the alert. 


 

Nagios Overview

  1. Anonymous (login to see details)

    Hello Team,

     

    Is there any way to integrate dynaTrace with Nagios using nsca client buit in 64-bits? I found out nsclient++ (64-bits), but it doesn't  working.  

     

    Thanks and Regards,

     

    Monica

     

    1. Anonymous (login to see details)

      Dear Monica!

      Soon I am going to update this plugin. Please give it a try!

      1. Anonymous (login to see details)

        Hi Balazs,

        As Monica said, i need to know if the integration between Nagios and DynaTrace is possible.

        Our customer need to integrate the informations from nagios to the interface of DynaTrace.

        If it's possible wich plugin we should use, and what kind of informations is possible to see on DT from Nagios.

        Best regards.

        Thanks

        1. Anonymous (login to see details)

          Hi!

          Currently the dynaTrace ->Nagios direction works with alerting. 

          If you need the Nagios -> dynaTrace integraton direction we can develop and customize it to your needs but not within this free plugin.

  2. Anonymous (login to see details)

    we are getting below errors. We are using Nagios Xi 

     

    2015-09-02 16:02:45 INFO [NagiosAction@hu.bakaibalazs.dynatrace.nagios.action] Nagios Alerting Execute

    2015-09-02 16:02:45 FINE [NagiosAction@hu.bakaibalazs.dynatrace.nagios.action] LEVEL:OK
    2015-09-02 16:02:45 FINE [NagiosAction@hu.bakaibalazs.dynatrace.nagios.action] RULE:Application Process Shut Down
    2015-09-02 16:02:45 FINE [NagiosAction@hu.bakaibalazs.dynatrace.nagios.action] MSG:Agent 'XXXXXXServer Shutdown' shut down
    2015-09-02 16:02:45 FINE [NagiosAction@hu.bakaibalazs.dynatrace.nagios.action] SERVER: dynaTrace_Dev_System_profile
    2015-09-02 16:02:45 INFO [NagiosAction@hu.bakaibalazs.dynatrace.nagios.action] Incident Agent 'XXXXServer' shut down triggered.
    2015-09-02 16:02:50 SEVERE [NagiosAction@hu.bakaibalazs.dynatrace.nagios.action] Exception message: connect timed out
    2015-09-02 16:02:50 SEVERE [NagiosAction@hu.bakaibalazs.dynatrace.nagios.action] Exception trace: java.net.PlainSocketImpl.socketConnect(Native Method)
    java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
    java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
    java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
    java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
    java.net.Socket.connect(Socket.java:579)
    com.googlecode.jsendnsca.NagiosPassiveCheckSender.connectedToNagios(NagiosPassiveCheckSender.java:80)
    com.googlecode.jsendnsca.NagiosPassiveCheckSender.send(NagiosPassiveCheckSender.java:62)
    hu.bakaibalazs.dynatrace.nagios.NagiosAction.execute(NagiosAction.java:71)
    com.dynatrace.diagnostics.sdk.UserPluginManager.executePlugin(SourceFile:745)
    com.dynatrace.diagnostics.sdk.ActionPluginExecutor.execute(SourceFile:31)
    com.dynatrace.diagnostics.sdk.ActionPluginExecutor.execute(SourceFile:13)
    com.dynatrace.diagnostics.scheduling.impl.ServerJobCenterRegistry.a(SourceFile:189)
    com.dynatrace.diagnostics.scheduling.impl.ServerJobCenterRegistry.a(SourceFile:412)
    com.dynatrace.diagnostics.scheduling.impl.ServerJobCenterRegistry.execute(SourceFile:336)
    com.dynatrace.diagnostics.scheduling.impl.SchedulerJob.a(SourceFile:101)
    com.dynatrace.diagnostics.scheduling.impl.SchedulerJob.work(SourceFile:92)
    com.dynatrace.diagnostics.scheduling.impl.SchedulerJob.executeJobInfo(SourceFile:241)
    com.dynatrace.diagnostics.scheduling.impl.QuartzJob.execute(SourceFile:45)
    org.quartz.core.JobRunShell.run(JobRunShell.java:202)
    com.dynatrace.diagnostics.scheduling.impl.QuartzThreadPool$WorkerThread.run(SourceFile:788)

    1. Anonymous (login to see details)

      it seems your dynaTrace can not reach the Nagios server. (connect timed out).

  3. Anonymous (login to see details)

    Hi,  

    has anyone worked on nrdp support yet ?

    thanks

    --

    Laurent