Change the Issue Status
You can acknowledge, monitor, or close issues to track progress on resolution. Use the Status button above the timeline to update the status of an issue. Changing the issue's status enables you to focus on the urgent problems, avoid duplicate efforts from teammates, and ease reporting progress in resolving the problems to your stakeholders.
Bigeye Issues have four potential statuses, each with its purpose:
- Triage: A new issue is created in this state by default when a metric detects a value outside the threshold. The issue status in the triage state remains unchanged unless you act upon them.
- Acknowledged (ack'd): Setting an issue to this state implies that you have looked at the issue and that an active investigation is underway. The issue is muted for 24 hours. The status of issues in the acknowledged state remains unchanged unless you act upon them.
- Monitoring: Setting an issue to this state means that a metric must return to a healthy state in future runs before Bigeye auto-closes the issue.
- Maintain threshold: For autothresholds, Bigeye keeps the current autothreshold. If Bigeye detects a similar anomaly, it creates another issue. The issue is auto-closed after the metric returns to a healthy state.
- Adapt threshold: For autothresholds, Bigeye changes the autothreshold based on this data. You see fewer issues based on such anomalies in the future. The issue is auto-closed after the metric returns to a healthy state and the threshold is adapted.
- Closed: The issue is resolved because the metric has returned to a healthy value.
- Maintain threshold: For autothresholds, Bigeye keeps the current autothreshold. If Bigeye detects a similar anomaly, it creates another issue.
- Adapt threshold: For autothresholds, Bigeye changes the autothreshold based on this data. You see fewer issues based on such anomalies in the future.
Updated about 1 year ago