Traces, metrics and health checks

Open
  • Is something wrong?
#20 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp, distributed-systems, postgresql
Domain
distributed-systems, observability

Research direction

Start by locating the producer, broker, and consumer paths, then find where pending messages are stored and processed. The issue calls for trace context across that flow, metrics for pending count, lag, and dead letters, and a health check based on the oldest pending message. Done means all four observability additions are implemented; the issue names no files or tests to guide that work.

Written by the indexing model from the issue text.

Description

enhancement

Trace context from producer through the broker to the consumer; pending count, lag and dead letters as metrics; a health check on the oldest pending message.

Dominant language
C#
Stars
0
Forks
0
Avg merge
1h 4m
Merged PRs (30d)
8

Getting set up

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 softvasco/outbox-kit

All issues in softvasco/outbox-kit

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.