mozilla-services / mozilla-services/syncstorage-rs

Switch from telegraf to the otel collector

Open
#2,275 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
1.8k
Forks
86
Avg merge
2d 17h
Merged PRs (30d)
21

Description

Per https://mozilla-hub.atlassian.net/wiki/spaces/SRE/pages/1801322497/Generating+metrics+with+StatsD#OpenTelemetry-Collectors-with-statsd-receivers the recommended ingestion for statsd metrics is the recently added otel collector.

We should move to it and disable our telegraf sidecar.

Alternatively we could consider switching our metrics fully to prometheus, but this setup is still somewhat in “preview” https://mozilla-hub.atlassian.net/wiki/spaces/SRE/pages/1767735347/Generating+metrics+with+Prometheus+Preview.

┆Issue is synchronized with this Jira Task

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the Telegraf sidecar and the StatsD metrics configuration in the repository, then compare them with the linked SRE guidance for the OpenTelemetry Collector. Done means StatsD metrics are ingested through the collector, the Telegraf sidecar is disabled, and the existing metrics flow is verified.

Written by the indexing model from the issue text.

Assessment

Domain
infrastructure, observability
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.