Home
Welcome to the terraform-signalfx-detectors wiki!
The generic purpose goal of detectors in this repository will always limit the scope and the capabilities of these modules and also the approval criteria for changes.
It does not aim to cover too specific usage, setup or implementation because they will not be reusable.
It is a good start for a new project, to detect known anomalies and usual problems, in common situations. Each module is focused on monitor one target from its own internal view.
The metric collection is good to understand this:
- using highly complex formulas on multiple metrics from the same source is not a problem while it remains easy to setup and could be used in common situations.
- but a very simple detector using only two metrics from different sources could be too dificult to setup or require dependencies not available for most of the people.
For example, correlate a simple CPU usage of an host (fully generic) with the latency of his own application (collected by a custom metric or apm metric): the detector is simple, easy to deploy but requirements cannot be generic by design.
Given that this scope and because we want to preserve homogeneity and maintainability every propositions could not be accepted. Also, the behavior which corresponds to the most of the people will always be favored compared to a better or more accurate approach which will only work in few situations.
This is also why we always recommend to create his own detectors, specific to his use case, data sources and situations. They will be a good complement to get a global monitoring coverage.
