Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alertmanager Exporter #862

Closed
Tracked by #854
tanveergill opened this issue Nov 1, 2022 · 0 comments · Fixed by #966
Closed
Tracked by #854

Alertmanager Exporter #862

tanveergill opened this issue Nov 1, 2022 · 0 comments · Fixed by #966
Assignees

Comments

@tanveergill
Copy link
Contributor

tanveergill commented Nov 1, 2022

Spec

  • 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.

Runtime

  • Use the Alertmanager client
  • 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.
  • The Alertmanager client(s) will be invoked from the OTEL pipeline for Alerts, refer Alertmanager Compatible Stream #861
@kwapik kwapik changed the title Alertmanager Config Alertmanager Exporter Nov 7, 2022
This was referenced Nov 7, 2022
kwapik added a commit that referenced this issue Nov 7, 2022
### 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants