Skip to content

Create Issue

Issues are used to integrate sources of anomalies, descriptions, and related members in the workspace. Any anomalies detected by members will be defined as an Issue, and relevant members will be automatically notified for tracking and resolution.

Concepts

Field Description
Delivery Channel Defaults to "All", supports custom addition of other channels.
Title The title of the Issue.
Description A detailed description of the current Issue. Supports @member notifications in the text box or adding #channel to deliver the current Issue to the corresponding channel.
Level Optional; Default level configurations can be selected, where the urgency levels are: P0 > P1 > P2; Manual modification is supported;
Custom levels can also be selected Custom Level.
Source Includes the following sources: Dashboards, Unresolved Events, Events, Explorers, Monitors.
Assignee When creating an Issue, specifying an assignee will trigger an email notification to them.
You can select members or teams from the current workspace as assignees; You can also manually enter external email addresses and press Enter to add them.
Attachments Supports uploading images, videos, and text files (CSV/TXT/JSON/PDF, etc.) in the Issue Details Page;
Supports configuring associated links.
Status The status of the Issue.
open: Not started. Default status when an Issue is created
working: In progress. The Issue has been assigned to an assignee and is being processed
pending: On hold. The Issue is determined to be unsolvable in the short term
resolved: Resolved. The Issue has been resolved
closed: Closed. The Issue does not need to be resolved or is determined to be a normal phenomenon

Create Issue

Issues can be created in two ways:

Manual Creation

Incident

Go to Incident, click Create Issue.

Dashboards

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

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

Explorer

In the workspace, you can click the button in the lower right corner of various Explorer-level feature module pages to create an Issue.

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

Hover over the source to display the source of the Issue. Click to 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 into the details page of a log in Explorer and click the button in the lower right corner to create an Issue. The page automatically displays the current Explorer details page as the source of the Issue. Click Source to 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.

Event

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

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

Click into the details page of an event, then click Create Issue in the lower right corner. The page automatically displays the title of the event as the source name of the Issue. Click Source to automatically jump to the corresponding event details page. If the event no longer exists, it will jump to the default Event display page.

If an Incident Issue has associated event information created by a monitor, the Issue will directly display the number of associated events in the list. Click to directly jump to the Event Explorer to view all related events.

Note

Whether directly triggering an Incident or appending in the comments of an Issue, both are included in the associated event count statistics 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 Configure Threshold Detection as an example:

  1. Issues created by events are defaulted to Open status and unknown level;

  2. The source is the current monitor;

  3. The event title is defaulted as the Issue title;

  4. The event content is defaulted as 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 selected channel and an email notification will be sent to the Issue assignee.

  6. After the event notification rules of the monitor are configured, if an abnormal event is generated under the monitor, an Incident Issue will be created synchronously. You can go to Incident > Selected Channel to view it.

Configuration Notes
  • To @member in the event description, you can click the @ button above the content box, enter @ in the content box, or directly click the @ dropdown box below to select notification members. After selection, when the event is created, an email notification will be automatically sent to the member.
  • @ notification members only take effect in synchronously created Incident Issues. For the normal monitor event alert notification list, please refer to the corresponding alert strategy configuration.
  • The default channel is the All channel in Incident.
  • If you have selected the by grouping condition in the Monitor > Detection Metrics of 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 Logs > Explorer, filter log data with status:unknown. Click Create Issue in the lower right corner.

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

  3. In the description, in addition to entering text, @ relevant members, the @ notified members will receive an email notification of the Issue; You can also enter a channel in the form of #abnormal data in the description for association;

  4. Select the Issue level;

  5. Select the assignee of the Issue as needed; The assignee will receive an email notification of the Issue;

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

Issue Auto Discovery

If Issue Auto Discovery is enabled in APM and RUM, the system will automatically detect errors according to the configured detection frequency and generate Issues. The generated Issues will be delivered to the configured channel with relevant identifiers.

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

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

Feedback

Is this page helpful? ×