Flashduty Docs
中文EnglishRoadmapAPI官网控制台
中文EnglishRoadmapAPI官网控制台
  1. Incidents
  • 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. Incidents

Custom Fields

Learn about, configure, and use custom fields.

Use Cases#


FlashDuty supports integration with most common alert systems, and we display most of the pushed content information in Labels. However, our users may still have extension or customization needs, such as manually marking whether an incident is a false alarm. Therefore, we provide the Custom Fields feature to further enrich incident descriptions.
With custom fields, you can add custom metadata, record specific incident-related information, and transmit and use this information during incident handling. Here are common use cases for custom fields:
Flexible Definition: You can create multiple custom fields and define their names, types, options, and default values according to your needs. Common custom field types include text, dropdown lists, checkboxes, etc.
drawing
Information Association: Through custom fields, you can associate incidents with other related data. For example, you can add custom fields to identify affected systems, geographic locations, associated customers, or whether it's a false alarm.
drawing
Filtering and Classification: The incident list supports filtering and classification views by custom fields. You can create frequently used filters based on custom field values for better organization and handling of incidents.
drawing

Configuring Custom Fields#


Creating Fields#

💡
An account can create up to 15 custom fields.
1.
Go to console Incident Management=>Custom Fields
2.
Click Create Custom Field
3.
Enter the following information
Field Name: Identifies the field in the API, cannot be modified after creation.
Display Name: The field shown on the incident details page, can be modified after creation.
Field Description: Helps incident responders understand and use the field.
4.
Select the field type and add options and default values as needed. Field types include:
Text: Plain text input box, maximum 500 characters.
Single Select: Single-select dropdown, allows up to ten options, each option cannot exceed 200 characters.
Multi Select: Multi-select dropdown, allows up to ten options, each option cannot exceed 200 characters.
Checkbox: Checkbox.
5.
Click Submit to complete
💡
If a field has a default value set, the system will automatically write to that field and assign the default value when an incident is generated. Note that fields only affect new incidents and have no impact on existing incidents.

Updating Fields#

Only the following content can be updated:
1.
Display Name
2.
Field Description
3.
Field Options (only for single and multi-select types)
4.
Default Value
💡
Field updates only affect new incidents and have no impact on existing incidents.

Deleting Fields#

You can initiate deletion operations in the console at any time. However, please note that deletion is a time-consuming operation. When deleting a field, the system will scan historical incidents and asynchronously update to remove the association between the field and incidents. You cannot create a field with the same name until the deletion is complete.

FAQ#


Why can't I search incidents by the fields I created?
Please check if the field type you want to search is a Text type. To ensure system stability, the system currently does not support searching text type fields. We appreciate your understanding.
修改于 2024-11-25 04:05:20
上一页
Escalations and Assignments
下一页
Custom Actions
Built with