Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Issue with Nagios2Opsgenie Edited

I'm just starting to integrate our Nagios with Opsgenie.  I created a service template and assigned it to a test service.  In the logs, when switching to criticals I see nagios2opsgenie being called but I get the following warning:

WARNING Stopping, Nagios NOTIFICATIONTYPE param has no value, please make sure your Nagios and OpsGenie files pass necessary parameters


My service is defined with the following:

define service {
   name ops-genie-notify
   service_description /usr/local/nagios/bin/nagios2opsgenie
   display_name Nagiso to OpsGenie
   use passive_service
   check_command notify-service-by-opsgenie
   is_volatile 0
   max_check_attempts 1
   active_checks_enabled 0
   passive_checks_enabled 1
   check_period 24x7
   check_freshness 0
   event_handler notify-service-by-opsgenie
   event_handler_enabled 1
   flap_detection_enabled 0
   retain_status_information 1
   retain_nonstatus_information 1
   notification_interval 60
   notification_period 24x7
   notification_options c,r
   notifications_enabled 1
   stalking_options c
   _AlertTeam MOC
   register 0


The command is defined as:

define command {
command_name notify-service-by-opsgenie
register 1


In looking at the golang script notification type is set with the flag t but that doesn't do anything.  

I've tried with the arguments, without, pretty much everything I can think of but doesn't seem like my service command is configured correctly.  

Does anyone have an example that I can use to see what I'm missing here?  


1 answer

Neverrmind, apparently NOTIFICATIONTYPE is not used in service checks so it's sending an empty string.  I just switched it to be "PROBLEM" and that worked fine.  Though I guess my question would be if I want to send OpsGenie a message when a service goes to critical using a check service command, why is nagios2opsgenie expecting a non-empty string in the notification type field?

Hi - did you ever work out a fix - we're having the same issue with service alerts into opsgenie.


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Opsgenie

New GitLab integration in Incident Investigation view

We launched the first version of the Incident investigation view in April of 2020 for Bitbucket Pipelines. Shortly after that, we added the ability to investigate deployment-related incidents in Opsg...

339 views 0 4
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you