FlashDuty, as a unified alert management platform, does not generate alert data by itself. It requires integration with third-party monitoring platforms to achieve unified alert reception, noise reduction, assignment, notification, resolution, analysis, and automation. This includes platforms like N9E/FlashCat, Zabbix, Prometheus, and various cloud providers' alert systems. For more integration types, please refer to Alert Integration.Integration Methods#
Private Integration#
Access path for Private Integration: Channel Details => Integrations => Private Integration.Private Integrations can be added when creating a channel or within an existing channel.
Alerts received through Private Integrations do not require routing rules, as all alerts are distributed to that channel (excluding filtered alerts) and cannot be shared with other channels.
Choose Private Integration when alerts don't need to be distributed to multiple channels.
Shared Integration#
Access path for shared integration: Integration Center => Alert Events.Alert event types created in the Integration Center are global and must use routing rules to direct alerts to one or multiple channels.
Each integration must be configured with at least one receiving channel, otherwise the integration will not be effective and cannot receive alert events.
Both dedicated and shared integrations generate a push URL after creation. Copy this URL to the corresponding platform to complete the integration.
Each alert source integration has different data types. For specific integration methods, refer to the Integration Guide. To ensure system stability, we limit the frequency of event requests for each integration. Currently, the limits are 100 requests per second (QPS) and 1000 requests per minute (QPM) per integration.If your requests exceed these limits, you will receive a 429 status code response. In such cases, wait for a while before retrying.These limits may be adjusted in the future. Please contact us if you need higher limits.
FAQ#
Why am I not receiving alerts from integrations created in the Integration Center?
1.
Please verify that routing rules are configured.
2.
Confirm that the source platform is triggering alerts and generating them properly.
Is there a limit on the number of integrations?
Currently, there is no limit.How are alert labels generated?
FlashDuty extracts all key information as labels, descriptions, or titles for each integration type. If you want to dynamically generate additional labels, configure label enrichment rules. For details, see: https://docs.flashcat.cloud/en/flashduty/label-enrichment-settingsHow are alert titles determined? Can I modify them?
FlashDuty uses specific title generation methods for each integration, typically combining "Strategy Name / Alert Object". To customize title generation rules, please refer to: https://docs.flashcat.cloud/en/flashduty/customize-incident-attrsHow can I check which integration type an alert event came from?
Click incident -> Enter incident details -> Associated alerts -> Alert source. 