Flashduty Docs
中文EnglishRoadmapAPI官网控制台
中文EnglishRoadmapAPI官网控制台
  1. Alerts integration
  • Getting Started
    • Introduction
    • Quick start
    • FAQ
    • Product Comparison
  • Incidents
    • What is an Incident
    • View Incidents
    • Handle Incidents
    • Escalations and Assignments
    • Custom Fields
    • Custom Actions
    • Alert Noise Reduction
    • Past Incidents
    • Outlier Incidents
  • Configure Flashduty
    • Channels
    • Integrate Alerts
    • Alert Noise Reduction
    • Escalation Rules
    • Label Enrichment
    • Schedules
    • Templates
    • Service Calendars
    • Preferences
    • Alert Routing
    • Silence and Inhibition
    • Filters
    • Notification Bots
    • Alert Pipeline
  • Platform
    • Teams and Members
    • Permissions
    • Single Sign-On
    • Insights
  • Advanced Features
    • Referencing Variables
    • Dynamic Assignment
  • Integrations
    • Alerts integration
      • Standard Alert Integration
      • Email Integration
      • Nightingale/FlashCat Integration
      • Prometheus Integration
      • Grafana Integration
      • Zabbix Integration
      • Uptime Kuma Integration
      • Alibaba Cloud ARMS Integration
      • Alibaba Cloud Monitor CM Event Integration
      • Alibaba Cloud Monitor CM Metrics Integration
      • Alibaba Cloud SLS Integration
      • AWS CloudWatch Integration
      • Azure Monitor Integration
      • Baidu Cloud BCM Integration
      • Huawei Cloud CES Integration
      • Influxdata Integration
      • Open Falcon Integration
      • PagerDuty Integration
      • Tencent BlueKing Integration
      • Tencent Cloud CLS Integration
      • Tencent Cloud Monitor CM Integration
      • Tencent Cloud EventBridge
      • OceanBase Integration
      • Graylog Integration
      • Skywalking Integration
      • Sentry Integration
      • Jiankongbao Integration
      • AWS EventBridge Integration
      • Dynatrace Integration
      • Huawei Cloud LTS Integration
      • GCP Integration
      • Splunk Alert Events Integration
      • AppDynamics Alert Integration
      • SolarWinds Alert Events Integration
      • Volcengine CM Alert Events Integration
      • Volcengine CM Event Center Integration
      • Volcengine TLS Integration
      • OpManager Integration
      • Meraki Integration
      • Keep Integration
      • ElastAlert2 Alert Integration
      • StateCloud Alert Events
      • Guance Alert Events
      • Zilliz Alert Events
      • Huawei Cloud APM Alerts
      • zstack integration
    • Change integration
      • Standard Change Event
      • Jira Issue Events
    • IM integration
      • Feishu (Lark) Integration Guide
      • Dingtalk Integration
      • WeCom Integration
      • Slack Integration
      • Microsoft Teams Integration
    • Single Sign-On
      • Authing Integration
      • Keycloak Guide
      • OpenLDAP Guide
    • Webhooks
      • Alert webhook
      • Incident webhook
      • Costom action
  • Terms
    • Terms of Service
    • User Agreement/Privary Policy
    • SLA
    • Data Security
  1. Alerts integration

OpManager Integration

Sync OpManager alert events to Flashduty via webhook for automated alert noise reduction.

In Flashduty


You can obtain an integration push URL through either of these two methods:

Using Private Integration

Choose this method when you don't need to route alerts to different channels - it's simpler.

Expand
  1. Go to the Flashduty console, select Channel, and enter a specific channel's details page
  2. Select the Integrations tab, click Add Integration to enter the integration page
  3. Select OpManager integration and click Save to generate a card
  4. Click the generated card to view the push URL, copy it for later use, and you're done

Using Shared Integration

Choose this method when you need to route alerts to different channels based on the alert payload information.

Expand
  1. Go to the Flashduty console, select Integration Center=>Alert Events to enter the integration selection page
  2. Select OpManager integration:
    • Integration Name: Define a name for this integration
  3. Configure the default route and select the corresponding channel (after the integration is created, you can go to Route to configure more routing rules)
  4. Click Save and copy the newly generated push URL for later use
  5. Done

In OpManager


I. OpManager Alert Push Configuration

  1. Log in to your OpManager console, select Settings => Notification Profiles from the navigation menu
  2. On the Notifications page, click Add and select Invoke a Webhook to add a configuration profile
drawing
  1. Begin configuring specific content on the Webhook editing page
  2. In Hook URL, select POST as the request method and fill in the integration push URL as the URL
  3. Select raw for Data Type and JSON for Payload Type
  4. Fill in the following content for Body Content:
{
     "alarmid":"$alarmid",
     "message":"$message",
     "displayName":"$displayName",
     "category":"$category",
     "severity":"$stringseverity",
     "strModTime":"$strModTime",
     "eventType":"$eventType",
     "entity":"$entity",
     "lastPolledValue":"$lastPolledValue",
     "Intf_ifDescr":"$IntfField(ifDescr)",
     "Intf_displayName":"$IntfField(displayName)",
     "Intf_ifAlias":"$IntfField(ifAlias)",
     "Intf_ifName":"$IntfField(ifName)",
     "Intf_ipAddress":"$IntfField(ipAddress)",
     "Intf_physMedia":"$IntfField(physMedia)",
     "Intf_ifIndex(ifIndex)":"$IntfField(ifIndex)",
     "Intf_ifCircuitID(ifCircuitID)":"$IntfField(ifCircuitID)",
     "Intf_ifSpeedIn(ifSpeedIn)":"$IntfField(ifSpeedIn)",
     "Intf_ifSpeedOut(ifSpeedOut)":"$IntfField(ifSpeedOut)",
     "Intf_lineID":"$IntfCustomField(Circuit ID)",
     "Intf_note":"$IntfCustomField(Comments)",
     "Intf_contacts":"$IntfCustomField(Contact Name)",
     "Intf_SLA":"$IntfCustomField(SLA)",
     "Custom_BuildingNo":"$CustomField(Building)",
     "Custom_cabinet":"$CustomField(Cabinet)",
     "Custom_note":"$CustomField(Comments)",
     "Custom_contacts":"$CustomField(Contact Name)",
     "Custom_department":"$CustomField(Department)",
     "Custom_RoomNo":"$CustomField(Floor)",
     "Custom_serial":"$CustomField(SerialNumbe)",
     "Monitor_monitorName":"$MonitorField(monitorName)",
     "Monitor_instance":"$MonitorField(instance)",
     "Monitor_protocol":"$MonitorField(protocol)",
     "Device_type":"$DeviceField(type)",
     "Device_ipAddress":"$DeviceField(ipAddress)",
     "Device_isSNMP":"$DeviceField(isSNMP)",
     "Device_dependent":"$DeviceField(dependent)",
     "Device_hardDiskSize":"$DeviceField(hardDiskSize)",
     "Device_ramSize":"$DeviceField(ramSize)"
}

Special Note: Custom fields are not currently supported. Even if referenced in the Body Content, they will not take effect.

  1. Keep the Request Headers as default
  2. Fill in any value between 1-300 for Time Out and click next
drawing
  1. On the Choose the criteria configuration page, check Notify when the alarm is cleared and configure other options as needed
drawing
  1. Select the devices you want to apply this configuration to, move them to the selected devices window using the right arrow, then click next
  2. Configure Time Window/Delayed Trigger/Recurring Trigger as needed, then click next
  3. Add the name FlashDuty for this configuration profile, then click Save to complete the setup

II. Status Mapping

OpManagerFlashdutyStatus
CriticalCriticalCritical
Service DownCriticalCritical
TroubleWarningWarning
AttentionInfoInfo
修改于 2025-03-27 07:53:11
上一页
Volcengine TLS Integration
下一页
Meraki Integration
Built with