Home
Welcome to the terraform-signalfx-detectors wiki!
This repository is a collection of generic detectors usable in most of the situations. This goal will restrict the scope of available detectors.
It also provides an opinionated way to configure and manage his monitoring with SignalFx. First because it uses Terraform as deployment tool but also because it tries to enforce patterns, follow templating rules and provide a common and repeatable basement for all detectors.
It does not aim to cover too specific usage, setup or implementation because they will not be reusable or do not address a more common need.
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 difficult 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 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, some propositions could not have his place here.
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.
Check the Usage Guidance documentation first, try to import one of the existing module and configure it to suit your need well.
If you are not satisfied but still have similar goal, please open an issue to discuss.
If you want to go further in usage, customization or even contribution, check the Development documentations section.
