Skip to content

Create Issue

An Issue is used to consolidate information about sources of anomalies, descriptions, and related members within a workspace. Any anomaly detected by any member will be defined as an Issue and automatically notify relevant members for tracking and handling.

Concepts

Field Description
Delivery Channel By default, delivered to "All"; supports custom addition of other channels.
Title The title of the Issue.
Description A detailed description of the current issue; supports @mentioning members in the text box to send notifications or adding #channel to deliver the Issue to the corresponding channel.
Level Optional; you can choose the default level configuration, with urgency levels ranked as follows: P0 > P1 > P2; manual modification is supported;
you can also select custom levels.
Source Includes the following sources: Dashboard, Unresolved Incident, Incident, Explorer, Monitor.
Assignee When creating an Issue, if an assignee is specified, the system will send an email notification to the assignee.
You can select members or teams from the current workspace as the assignee; alternatively, you can manually enter an external email address and press Enter to add it.
Attachments Supports uploading images, videos, and text files (CSV/TXT/JSON/PDF, etc.) on the Issue Details page;
supports configuring associated links.
Status The status of the Issue.
open: Not started. This is the default status when an Issue is created.
working: In progress. The Issue has been accepted and is being handled by the assignee.
pending: Pending. The Issue has been determined to be a problem that cannot be resolved in the short term.
resolved: Resolved. The Issue has been resolved.
closed: Closed. The Issue does not need to be resolved or has been determined to be normal.

Create Issue

Creating an Issue supports two methods: manual creation, automatic creation.

Manual Creation

Incident Tracking

Navigate to Incident Tracking, click Create Issue.

Dashboard

Go to Scenarios > Dashboard > Settings, click Create Issue;

The current dashboard name is automatically displayed as the source name for this Issue. Click Source to automatically navigate to the corresponding dashboard. If the dashboard no longer exists, it will redirect to the default Scenarios page.

Explorer

In the workspace, you can click the bottom-right button to create an Issue from various Explorer-level feature module pages.

For example, in Logs > Explorer, click the Create Issue icon at the bottom right to enter the new Issue page.

Hover over the source to display the source of this Issue. Clicking it will automatically navigate to the corresponding Explorer. The system will filter and display according to the time range and search conditions saved in the Explorer at the time of Issue creation.

You can also click into the details page of a specific log entry under the Explorer, and similarly click the bottom-right button to create an Issue. The current Explorer detail page will be automatically displayed as the source of this Issue. Click Source to automatically navigate to the corresponding Explorer detail page. If the data no longer exists, it will redirect to the default display state of the Explorer.

Incident

Hover over an incident list item to see the Issue button appear on the left; click it to proceed.

The title of the selected incident will be automatically displayed as the source name for this Issue. Clicking Source will automatically navigate to the corresponding incident details page. If the incident no longer exists, it will redirect to the default Incident display page.

Navigate to the details page of a specific incident and click the Create Issue button at the bottom right. The title of the incident will be automatically displayed as the source name for this Issue. Clicking Source will automatically navigate to the corresponding incident details page. If the incident no longer exists, it will redirect to the default Incident display page.

If an Incident Tracking Issue was created through a monitor synchronization, the number of associated incidents will be directly displayed in the list. Clicking it will allow direct navigation to the Incident Explorer to view all related incidents.

Note

Both directly triggered incidents and those appended in Issue comments are included in the count of associated incidents here.

Automatic Creation

When configuring a Monitor, you can choose to associate a channel. When the monitor triggers an alert due to an anomalous event, an Issue will be automatically created. Taking threshold detection configuration as an example:

  1. Issues created by triggered events have a default status of Open and an unspecified level.
  2. The source is the current monitor.
  3. The event title is used as the default Issue title.
  4. The event content is used as the default Issue description.

  5. Under Event Notifications > Associate Incident Tracking, click the enable button and optionally select the level, channel, and assignee. Once selected, when the event is created, the associated Issue will be delivered to the selected channel and an email notification will be sent to the Issue assignee.

  6. After the event notification rule for the monitor is configured, if an anomalous event occurs under the monitor, an Issue will be synchronously created. You can go to Incident Tracking > Your Selected Channel to view it.

Configuration Notes
  • To @mention members in the event description, you can click the @ button above the input field, type @ inside the input field, or directly click the @ dropdown below to select members to notify. Once selected, the mentioned member will receive an email notification upon event creation.
  • @ mentions only take effect in the synchronously created Incident Tracking issues, not in the regular monitor alert lists. For those, please refer to the corresponding alert strategy configuration.
  • The default channel is the All channel in Incident Tracking.
  • If you have set a by grouping condition in the Detection Metrics section of the current event's monitor, and the associated Issue status is Open or Pending, subsequent multiple events from the same source will not create new Issues but will be appended as replies to the existing Issue.

Creation Example

  1. In Logs > Explorer, filter for logs with status:unknown. Click the Create Issue button at the bottom right.

  2. Input the Issue title as "Test Data" and set the level to P2.

  3. In the description, in addition to entering text, mention relevant members using @; these members will receive email notifications about the Issue. You can also associate a channel by entering something like #AnomalyData.

  4. Select the Issue level.

  5. Optionally select an assignee for the Issue; the assignee will receive an email notification.

  6. After saving, you can view the Issue in Incident Tracking > Channel or in the associated channel.

Issue Auto Discovery

If you have enabled Issue Auto Discovery in APM or RUM, the system will automatically detect errors based on the configured frequency and generate Issues accordingly. These generated Issues will be delivered to the configured channel and marked with relevant tags.

Issues created via Issue Auto Discovery use a composite dimension as the unique identifier. If a historical Issue already exists with the same composite dimension, a new Issue will not be created; instead, the new content will be appended to the historical Issue's reply area for updates. Typically, you can identify the status through special markers such as “New Problem”, “Recurring Problem”, or “Regression Problem”.

  • Creator: Displayed as “Issue Auto Discovery”, indicating its auto-generated nature.
  • Composite Dimension: Additional grouping information is shown on the Issue card and detail pages.
  • Special Markers: Automatically discovered Issues generally carry one of three special markers: “New Problem”, “Recurring Problem”, or “Regression Problem”.
    • New Problem: If no historical Issue exists with the same composite dimension, the Issue is created and marked as “New Problem” on the right side.
    • Recurring Problem: If a historical Issue already exists with the same composite dimension and the status is Open or Pending, meaning the problem reoccurs, the historical Issue is marked as “Recurring Problem” on the right side.
    • Regression Problem: If a historical Issue already exists with the same composite dimension and the status is Resolved, meaning the problem reappears after resolution, the historical Issue is marked as “Regression Problem” on the right side.