Sample request: Metric buffer

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
prometheus, python
Domain
documentation, observability

Research direction

Start by reviewing the repository’s existing sample layout and the metric buffer usage, then compare the proposed prometheus/client_python approach with direct Prometheus usage. Done means the repository shows how to use a metric buffer and explains when direct Prometheus is preferred.

Written by the indexing model from the issue text.

Description

enhancement
Describe the solution you'd like

Show how to use a metric buffer. A decent example may forward metrics to https://github.com/prometheus/client_python, but we should encourage people to use the direct Prometheus approach if they can.

Dominant language
Python
Stars
367
Forks
121
Avg merge
3d 20h
Merged PRs (30d)
11

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 temporalio/samples-python

All issues in temporalio/samples-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.