You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Alertmanager exporter, which converts the log events into POST /alerts calls to Alertmanager API (if Alertmanager is configured)
A top level alertmanagers section in Agent and Controller config similar to this config in Prometheus. It should utilize aperture common http client configuration.
Alertmanager clients should be created separately from the Alertmanager exporter - see how this is done for K8s clients and passed as a parameter to the alertmanager exporter.
### Description of change
This introduces basic pipelines for Alerts including the following.
#### `alerts.Alerter` interface
This interface is being propagated as part of the platform. It can be
used by any party interested by calling `AddAlert(*alerts.Alert)`
method. In particular, it will be used by components like
#863.
There are helper functions and methods provided to `alerts.Alert` struct
for easy construction of such alerts.
#### Alerts receiver
This receiver calls `AlertsChan()` method of `alerts.Alerter`, converts
received `alert.Alert` structs into OpenTelemetry Logs format and pushes
into the next consumer.
There are convenient functions provided for easy conversions in both
ways, to be used in the Alertmanager exporter
#862.
#### Alerts processors
Alerts processor add proper labels to the alerts i.e. `agent_group`,
`instance` and `controller_id`.
Ref: GH-861
##### Checklist
- [x] Tested in playground or other setup
- [x] Documentation is changed or added
- [x] Tests and/or benchmarks are included
Spec
alertmanagers
section in Agent and Controller config similar to this config in Prometheus. It should utilize aperture common http client configuration.Runtime
The text was updated successfully, but these errors were encountered: