Nagios/Ichinga integration plans?

[ffeingold-clmke]

Hello,

I know that we could do it with the API, but any plans to more directly integrate with Nagios/Ichinga?

Thanks!

[Dushyant-rahangdale]

Hi @ffeingold-clmke! 👋

Yes, native integrations for both Nagios (Core & XI) and Icinga 2 are actively planned and currently in development.

These will provide dedicated endpoints (/api/integrations/nagios and /api/integrations/icinga) that natively parse Nagios macros, Icinga JSON notification payloads, handle automatic incident triggering/resolving, and manage deterministic deduplication keys out-of-the-box.

---

In the meantime: Quick Setup Guide for Nagios & Icinga 2

You can connect Nagios or Icinga 2 to OpsKnight today using standard notification commands that forward alerts to your OpsKnight service endpoint:

1. Nagios (Core / XI) Setup

Create a notification command in your Nagios configuration (e.g., /etc/nagios/objects/commands.cfg):

define command {
    command_name    notify-service-by-opsknight
    command_line    /usr/bin/curl -X POST "https://your-opsknight-domain/api/integrations/v1/events"                     -H "Content-Type: application/json"                     -H "Authorization: Bearer YOUR_INTEGRATION_KEY"                     -d '{                       "event_action": "'$NOTIFICATIONTYPE$'",                       "dedup_key": "nagios-'$HOSTNAME$'-'$SERVICEDESC$'",                       "payload": {                         "summary": "'$SERVICEDESC$' on '$HOSTNAME$' is '$SERVICESTATE$': '$SERVICEOUTPUT$'",                         "source": "Nagios",                         "severity": "'$SERVICESTATE$'",                         "custom_details": {                           "hostname": "'$HOSTNAME$'",                           "hostaddress": "'$HOSTADDRESS$'",                           "service": "'$SERVICEDESC$'",                           "state": "'$SERVICESTATE$'",                           "output": "'$SERVICEOUTPUT$'"                         }                       }                     }'
}

2. Icinga 2 Setup

Add a NotificationCommand definition to your Icinga 2 configuration (e.g., /etc/icinga2/conf.d/opsknight.conf):

object NotificationCommand "opsknight-service-notification" {
  import "plugin-notification-command"

  command = [
    "curl", "-s", "-X", "POST",
    "https://your-opsknight-domain/api/integrations/v1/events",
    "-H", "Content-Type: application/json",
    "-H", "Authorization: Bearer YOUR_INTEGRATION_KEY",
    "-d", "{ \"event_action\": \"" + notification.type + "\", \"dedup_key\": \"icinga-" + host.name + "-" + service.name + "\", \"payload\": { \"summary\": \"" + service.name + " on " + host.name + " is " + service.state + "\", \"source\": \"Icinga\", \"severity\": \"" + service.state + "\", \"custom_details\": { \"host\": \"" + host.name + "\", \"service\": \"" + service.name + "\", \"output\": \"" + service.output + "\" } } }"
  ]
}

---

We will update this discussion once the native plug-and-play UI integrations are released in an upcoming build! Let us know if you have specific macro/payload customizations or requirements you would like supported.

[Dushyant-rahangdale]

🚀 Update: Native Nagios & Icinga 2 Integrations Ready for v1.3.0!

Exciting news! Native, first-class integrations for both Nagios (Core & XI) and Icinga 2 have been fully developed and tested.

They will be officially released in OpsKnight v1.3.0 in a few days! 🎉

---

What to Expect in v1.3.0:

1. Dedicated Webhook Endpoints:

   • /api/integrations/nagios — Natively parses Nagios macro payloads (NOTIFICATIONTYPE, HOSTNAME, SERVICEDESC, SERVICESTATE, SERVICEOUTPUT, etc.), normalizes both lowercase and uppercase variations, and handles automatic service/host incident lifecycles (PROBLEM, ACKNOWLEDGEMENT, RECOVERY).
   • /api/integrations/icinga — Natively parses Icinga 2 notification payloads (notification_type, service_state, host_state, service_output, check_command), with support for camelCase and snake_case formatting.

2. Enterprise HMAC-SHA256 Security:

   • Optional webhook shared secrets with x-signature HMAC verification to ensure zero tampering and authenticity.

3. Deterministic Deduplication:

   • Automatic alert deduplication (nagios-${host}-${service} and icinga-${host}-${service}) to avoid alert fatigue while maintaining full audit trails and War Room linking.

4. One-Click UI Catalog:

   • Native Nagios and Icinga 2 cards with branded icons under Monitoring & APM in the Service Integration setup flow.

---

The implementation and test suites are tracked in Pull Request #303. Stay tuned for the v1.3.0 release announcement!

[Dushyant-rahangdale]

Hey @community! 👋

Great news — native Nagios Core & XI and Icinga 2 integrations are officially live in OpsKnight v1.3.0! 🚀

You can now connect both Nagios and Icinga 2 directly to OpsKnight with 0 custom scripts or API glue.

---

🔌 What was added:

1. Nagios Core & Nagios XI (/api/integrations/nagios)

• Host & Service States: Full bi-directional parsing for CRITICAL, WARNING, DOWN, UP, OK, and UNKNOWN.
• Macro Support: Ingests standard Nagios macros ($HOSTNAME$, $SERVICEDESC$, $SERVICESTATE$, $SERVICEOUTPUT$, $NOTIFICATIONTYPE$).
• Deduplication: Automatic collision-resistant fingerprinting by host and service.
• 📖 Nagios Setup Guide

2. Icinga 2 (/api/integrations/icinga)

• Check Results & Notifications: Ingests check result events, notification hooks, and downtime filters.
• State Mapping: Clean mapping of service check results directly into OpsKnight incident urgencies.
• 📖 Icinga 2 Setup Guide

---

📦 How to get it:

Pull the latest Docker image:

docker pull ghcr.io/opsknight-labs/opsknight:1.3.0
# or
docker pull ghcr.io/opsknight-labs/opsknight:latest

Check out the full v1.3 Documentation or try it out in your service integration settings! Thanks for the feature request! 🙌