linkedin / linkedin/Burrow

Reporting metrics to http api or stdout

Open
#529 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
4k
Forks
818
Avg merge
1h 14m
Merged PRs (30d)
1

Description

Is there any way to report _all_ metrics? I would happily take stdout or the notifier API. I am _not_ looking to notify only on thresholds and such, just to get all of the data out. Then I can use either an HTTP API endpoint or even a log gatherer like fluentd to push it into my tracking system and alert on my own thresholds, push into other systems, etc.

Somewhat related to #341

Contributor guide

No contributing guide indexed for this repository

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 reviewing Burrow's notifier API and the existing metric collection and output paths. Compare stdout, HTTP API, and notifier-based reporting against the request for all metrics; the issue does not define a preferred interface, affected files, tests, or a precise completion criterion.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
api, observability-sre
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.