Prometheus metrics exposotion

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
go, prometheus
Domain
backend, observability

Research direction

Start by locating the Stencil server entry point and reviewing how server requests and other runtime events are handled. Determine which server-use time series should be exposed and how Prometheus instrumentation fits the existing structure. Done means the server exposes useful Prometheus metrics and the relevant behavior is covered by tests, though no specific files or tests are named in the issue.

Written by the indexing model from the issue text.

Description

Is your feature request related to a problem? Please describe.

The stencil server should expose time series metrics to monitor the server's use. It is a feature request to add Prometehues instrumentation to the Stencil server.

Dominant language
Go
Stars
237
Forks
42
No merged PRs in 30d

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.

More from raystack/stencil

All issues in raystack/stencil

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.