Skip to content

Bump cosl so charms that rely on it for generic alert rules have updated alert rules #167

@sinapah

Description

@sinapah

This is a tracking issue.

A recent PR #162 made generic alert rules more detailed to resolve #160. cosl should be bumped where charms rely on it for their generic alert rules (namely, any charm which instantiates a MetricsEndpointProvider or a PrometheusRemoteWriteConsumer.

The list of charms where this will be necessary (PR links to be updated):

  1. Grafana Agent: chore: implement new prometheus remote write requirements grafana-agent-operator#343
  2. Grafana Agent K8s: chore: implement new prometheus remote write requirements grafana-agent-k8s-operator#423
  3. Otel Collector: chore: implement new prometheus remote write requirements opentelemetry-collector-operator#130
  4. Otel Collector K8s: chore: implement new prometheus remote write requirements  opentelemetry-collector-k8s-operator#148
  5. Coordinated workers: chore/bump-cosl cos-coordinated-workers#114
  6. Alertmanager K8s:
  7. Prometheus K8s: chore: bump-cosl prometheus-k8s-operator#754
  8. Tempo operators (only the coordinator needs the change): chore: implement new prometheus remote write lib requirements tempo-operators#248
  9. Mimir coordinator: chore: bump cosl and fetch remote write lib mimir-coordinator-k8s-operator#199
  10. To be completed

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions