Skip to content

Telemetry support #228

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
keeganwitt opened this issue Dec 10, 2024 · 1 comment
Open

Telemetry support #228

keeganwitt opened this issue Dec 10, 2024 · 1 comment

Comments

@keeganwitt
Copy link
Contributor

I wonder if we should support publishing telemetry metrics. The only metric I can think of offhand is to keep a metric for each rotated file (and whether it succeeded).

@ringerc
Copy link
Contributor

ringerc commented Feb 2, 2025

Off the top of my head useful values would include:

  • successful rotation count (counter)
  • last rotation timestamp (gauge, unix epoch timestamp)
  • is cmd running (gauge, bool)
  • last exit code of cmd if it has exited since being launched, NaN otherwise (gauge)
  • number of times pid in pid_file_name signalling attempted (counter)
  • number of times pid in pid_file_name signalling failed with an error (counter)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants