Automattic / Automattic/kue

Reporting metrics to Graphite/StatsD

Open
#421 1 comment 0 reactions 0 assignees View on GitHub
Discussion Feature needs pull request
Dominant language
JavaScript
Stars
9.4k
Forks
858
PR merge metrics
No merged PRs in 30d

Description

I'm currently thinking how I can report metrics to our graphite or statsd instance.

What would be a better solution? I could have a periodical push that sends the current counts of active, failed and completed jobs or I could send an increment on each job change.

What I like about the periodical push is, that I would definitely be notified about how many jobs are currently stuck. I could probably calculate that with a difference between the active and completed and failed jobs when I would increment them.

What solutions have you come up with?

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no files, tests, or entry points. First clarify whether metrics should be pushed periodically or incremented per job change, then identify the relevant queue/job lifecycle code and define the reporting behavior and tests before implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
observability-sre
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.