Haystack

Haystack

  • Docs
  • Contributing
  • Help
  • GitHub
  • Adopters

›Subsystems

About

  • Introduction
  • Getting Started
  • Architecture
  • Clients
  • Blobs

Subsystems

  • Subsystems
  • Traces
  • Trends
  • Collector
  • Service Graph
  • Pipes
  • Anomaly Detection
  • Attribution
  • Console

UI

  • UI
  • Traces
  • Trends
  • Alerts
  • Service Graph
  • Service Insights
  • Universal Search

Deployment

  • Deployment
  • Subsystems
  • Clients
Edit

Anomaly Detection

Note: This topic describes work in progress. The released component may vary from what's described here.

The Anomaly Detection subsystem is responsible for identifying anomalies in services' health and triggering alerts. By default, Anomaly Detection will monitor for anomalies in duration, success percentage, and count (number of operations over time) for all operations of all services sending data to Haystack.

The Trends subsystem is responsible for generating duration, count, and success/failure trends for all services sending tracing data to Haystack. The Anomaly Detection subsystem will consume the Trends data and attempt to automatically learn what normal operation looks like so that it can raise alerts when it detects abnormal operation.

Here is more information about what's coming: https://github.com/ExpediaDotCom/haystack-adaptive-alerting/wiki

← PipesAttribution →
Haystack
Docs
IntroductionGetting StartedArchitecture
Related
Chat on GitterContributing to Haystack
More
GitHubStar
Expedia
Copyright © 2020 Expedia