Skip to content

Create Issue

Issue is used to integrate the source, description, and related members of abnormal problems in the workspace. Any abnormal phenomenon detected by a member will be defined as an Issue, and relevant members will be automatically notified for tracking and handling.

Concepts

Field Description
Delivery Channel Delivered to "All" by default, supports custom addition of other channels
Title The Issue title
Description Detailed description of the current Issue phenomenon. Supports mentioning members with @member in the text box to send notifications or adding #channel to deliver the current Issue to the corresponding channel
Level Optional, can be modified later
You can choose the default level configuration, where the urgency levels are: P0 > P1 > P2
You can also choose custom levels
Source Includes the following sources: Dashboards, Unrecovered Events, Events, Explorer, Monitors
Assignee After specifying an assignee when creating an Issue, the system will send an email notification to the assignee
You can choose a member or team from the current workspace as the assignee; you can also manually enter an external email and press Enter to add it as needed
Attachments Supports uploading images, videos, text (CSV/TXT/JSON/PDF, etc.) in the Issue details page
Supports configuring associated links
Status The Issue status
open: Not started. The default status when an Issue is created
working: In progress. The Issue has been received by the assignee and is being processed
pending: Pending. The Issue is judged to be a problem that cannot be resolved in a short time
resolved: Resolved. The Issue has been resolved
closed: Closed. The Issue does not need to be resolved or is judged to be a normal phenomenon

Create Issue

There are two ways to create an Issue:

Manual creation

Automatic creation

Manual creation

Button display

The manual creation entry will only be displayed when you enable the "Create Issue" shortcut button in Preferences.

Incident

Go to Incident and click Create Issue.

Dashboards

Go to Scenarios > Dashboards > Settings, and click Create Issue.

The name of the current dashboard is automatically displayed as the source name of this Issue. Clicking Source will automatically jump to the corresponding dashboard. If the dashboard does not exist, it will jump to the default page of Scenarios.

Explorer

Enter the workspace, and you can click the button in the lower right corner of the page of major Explorer-level functional modules to create a new Issue.

For example, in Log > Explorer, click the Create Issue icon in the lower right corner to enter the creation page.

Hovering over the source will display the source of this Issue. Clicking it will automatically jump to the corresponding Explorer. The system will filter and display based on the time range and search conditions saved in the Explorer when the Issue was created.

You can also click to enter the details page of a specific log in the Explorer and similarly click the button in the lower right corner to create a new Issue. The page automatically displays the current Explorer details page as the source of this Issue. Clicking Source will automatically jump to the corresponding Explorer details page. If the data no longer exists, it will jump to the default display state of the Explorer.

Unrecovered Events

Hover the mouse over an event list, then click Issue that appears on the left.

The page automatically displays the title of this event as the source name of this Issue. Clicking Source will automatically jump to the corresponding event details page. If the event no longer exists, it will jump to the default entry display page of Events.

Click to enter the details page of an event, then click Create Issue in the lower right corner. The title of this event is automatically displayed as the source name of this Issue. Clicking Source will automatically jump to the corresponding event details page. If the event no longer exists, it will jump to the default entry display page of Events.

If an Incident Issue has associated event information created synchronously by a monitor, the number of associated events will be directly displayed in the list for that Issue. Clicking it will directly jump to the Event Explorer to view all related events.

Note

Both directly triggered Incidents and those added in the comments of an Issue are included in the statistics of associated event counts here.

Automatic creation

When configuring a Monitor, you can choose to associate a Channel. When the monitor generates an abnormal event alert, an Issue will be automatically created. Taking Configuring Threshold Detection as an example:

  1. The Issue created by an event trigger has a default status of Open and a default level of Unknown;

  2. The source is the current monitor;

  3. Enter the event title, which defaults to the Issue title;

  4. Enter the event content, which defaults to the Issue description;

  5. In Event Notification > Associate Incident, click the enable button, and select the level, channel, and assignee as needed. After selection, when the event is created, the automatically created Issue will be delivered to the channel you selected here for display, and an email notification will be sent to the assignee of this Issue.

  6. After the event notification rules for the monitor are configured, if an abnormal event is generated under this monitor, an Incident Issue will be created synchronously. You can go to Incident > The channel you selected to view it.

Configuration Notes
  • To @member in the event description, you can click the @ button above the content box, enter @ within the content box, or directly click to select a notification member from the @ dropdown below. After selection, when the event is created, an email notification will be automatically sent to that member;
  • @ notification members only take effect in the synchronously created Incident Issues; the alert notification list for normal monitor events please refer to the corresponding alert strategy configuration;
  • The default channel is the All channel in Incident;
  • If you selected a by grouping condition in the Monitor > Detection Metric corresponding to the current event, and the status of the Issue associated with the current monitor is Open or Pending, then subsequent multiple events from the same source will not create new Issues, but will be appended to the replies of the existing Issue.

Creation Example

  1. In Log > Explorer, filter log data with status:unknown. Click Create Issue in the lower right corner.

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

  3. In the description, in addition to entering text, @ relevant members; members mentioned by @ will receive a notification for this Issue in their email; you can also associate a channel by entering a channel in the form of #abnormal_data in the description;

  4. Select the Issue level;

  5. Select the assignee for this Issue as needed; the assignee will receive a notification for this Issue in their email;

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

Issue Auto Discovery

If Issue Auto Discovery is enabled in the configuration of APM or RUM, the system will automatically perform error discovery according to the configured detection frequency and generate Issues. The generated Issues will be delivered to the configured channel and marked with relevant identifiers.

Incident Issues created through Issue Auto Discovery use the combination dimension as a unique ID. If an Issue with the same combination dimension already exists historically, a new Issue will not be created; instead, the content will be appended to the reply area of the historical Issue for updating. Generally, the status can be identified by special labels such as "New Issue", "Duplicate Issue", and "Regression Issue".

  • Creator: Displayed as "Issue Auto Discovery", indicating its auto-generated property.
  • Combination Dimension: Added combination dimension grouping information, displayed on the Issue card page and details page.
  • Special Labels: Auto-discovered Issues generally have three different special labels: "New Issue", "Duplicate Issue", and "Regression Issue".
    • New Issue: If no historical Issue exists with the same combination dimension, an Issue is created and marked "New Issue" on the right;
    • Duplicate Issue: If a historical Issue already exists with the same combination dimension and its status is Open or Pending, meaning the problem has reappeared, the historical Issue is marked "Duplicate Issue" on the right;
    • Regression Issue: If a historical Issue already exists with the same combination dimension and its status is Resolved, meaning the problem has recurred after being resolved, the historical Issue is marked "Regression Issue" on the right.

Feedback

Is this page helpful? ×