Source
APM, tracing & profiling — found from sitemap — AppSignal
Checked for AppSignal on 6 Nov 2026
- Page
- https://docs.appsignal.com/anomaly-detection
- Checked
- 6 Nov 2026, 04:19 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:69abac44d4749581df58df84ae2e4528c3bea673f8c7087bebeac91885a0593a
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Anomaly detection description Report an error
“With Anomaly detection, you can configure triggers to send notifications when a metric value goes over or dips below a threshold value.”
-
Anomaly detection check frequency Report an error
“Anomaly detection checks metric values once per minute.”
-
Anomaly detection alert states Report an error
“Alerts can have five states:”
-
Anomaly detection notification transitions Report an error
“AppSignal notifies you on two state transitions: when an alert opens, and when it is resolved.”
-
Anomaly detection email reminders Report an error
“Email can also send reminders while an alert stays open. Every other channel, including Slack, PagerDuty, Opsgenie, and webhooks, is notified only on the open and resolved transitions.”
-
Anomaly detection no frequency options Report an error
“Unlike error incidents, alerts have no notification frequency options. There is no Never Notify or Every Nth per Hour setting, because notifications follow the alert state machine rather than a count of occurrences.”
-
Anomaly detection trigger types Report an error
“Select Add trigger to open the metric picker, then choose a trigger type from Tracing, Host metrics, or Other. Custom metric triggers are listed under Other as Custom metrics.”
-
Anomaly detection tracing metrics Report an error
“Error rates Error (absolute) counts App throughput Performance of actions (slow actions) Queue time”
-
Anomaly detection host metrics Report an error
“CPU load Disk I/O Disk usage Load averages Memory usage Network usage”
-
Anomaly detection warmup Report an error
“When a trigger has a warm-up period, AppSignal opens the alert only after the threshold condition has stayed true for the whole warm-up period.”
-
Anomaly detection cooldown Report an error
“If you configure a cooldown period, AppSignal will not create a new alert unless the trigger condition is met again after the cooldown period expires.”
-
Anomaly detection multi alert per trigger Report an error
“A trigger opens one alert per matching series, not one alert in total. A trigger that matches 30 hosts opens 30 alerts when all 30 cross the threshold.”
-
Anomaly detection hostname wildcards Report an error
“Host metric triggers make this easy to overlook, because the hostname field supports wildcards and its default value of * matches every host reporting to the app.”
-
Anomaly detection tags Report an error
“Tag values can be exact values like namespace=web or wildcards like queue=*.”
-
Anomaly detection tag warning Report an error
“AppSignal lists the tag combinations it has seen for that metric and warns you when the combination you entered has not been seen in the last hour.”
-
Anomaly detection missing datapoints as zero Report an error
“In these cases, enable Treat missing datapoints as 0. AppSignal then treats a missing data point as zero, which helps an alert close when no data arrives in the next minute.”
-
Anomaly detection processing delay Report an error
“The processor then waits* until all the data for a minute has arrived before processing that data and creating or updating alerts.”
-
Anomaly detection ntp recommendation Report an error
“ensure that your application’s servers report simultaneously by configuring them using NTP. Incorrect or different reported times from multiple app servers can prevent alerts from opening or closing.”
-
Anomaly detection issues page Report an error
“You can view all alert incidents on the Anomaly Issues page in the AppSignal app. The Issues page displays an overview of all open alert incidents, ordered by their last occurrence, with columns for the anomaly:”
-
Anomaly detection incident summary Report an error
“Alert information: The metric name, alert state, and tags of the alert.”
-
Anomaly detection incident settings Report an error
“Incident Settings: Ability to close the alert, set its severity, and assign it to a team member.”
-
Anomaly detection logbook Report an error
“Logbook: A logbook for logging important alert information about this alert for your team or future self.”
-
Anomaly detection time detective Report an error
“Access to the Time Detective: Use the Time Detective tool to view the state of your application when the alert last occurred.”
-
Anomaly detection edit archive effects Report an error
“Alerts still in their warm-up phase are discarded.”
-
Anomaly detection edit incident linking Report an error
“When you edit a trigger, open anomaly incidents for the previous trigger are linked to the new trigger so the incident history and logbook stay available across the edit.”
-
Anomaly detection archive closes incidents Report an error
“When you archive a trigger without replacing it, open anomaly incidents for that trigger are closed.”
-
Anomaly detection notifier routing Report an error
“Alerts are sent to the notifiers selected on the trigger, not to every notifier configured on the app.”
Scores citing this record
- The Agency Tech Lead APM, tracing & profiling
- The Agency Tech Lead Alerting, integrations & developer workflow
- The Data Protection Officer APM, tracing & profiling
- The Data Protection Officer Alerting, integrations & developer workflow
- The Mobile Team Lead APM, tracing & profiling
- The Mobile Team Lead Alerting, integrations & developer workflow
- The SaaS CTO APM, tracing & profiling
- The SaaS CTO Alerting, integrations & developer workflow
- The Skeptic APM, tracing & profiling
- The Skeptic Alerting, integrations & developer workflow
- The Site Reliability Engineer APM, tracing & profiling
- The Site Reliability Engineer Alerting, integrations & developer workflow