mirror of
https://github.com/hibiken/asynq.git
synced 2026-04-25 23:15:51 +03:00
[GH-ISSUE #206] [FEATURE REQUEST] JSON output flag for asynq stats #72
Labels
No labels
CLI
bug
designing
documentation
duplicate
enhancement
good first issue
good first issue
help wanted
idea
invalid
investigate
needs-more-info
performance
pr-welcome
pull-request
question
wontfix
work in progress
work in progress
work-around-available
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/asynq#72
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @rverton on GitHub (Oct 20, 2020).
Original GitHub issue: https://github.com/hibiken/asynq/issues/206
Originally assigned to: @hibiken on GitHub.
To monitor the asynq queue, it would be nice to periodically retrieve stats (like the
asynq statscommand currently does), but in a format which can be piped into monitoring tools.A simple and easy way to do this would be to add a
--jsonflag toasynq statswhich outputs all gathered stats as json. This stats can then periodically be retrieved (with tools like Telegraf) and then displayed in Grafana.@hibiken commented on GitHub (Oct 21, 2020):
Thanks for opening this issue!
Seems like a good option to have. I'll include this change in the next release.
@c-nv-s commented on GitHub (Apr 23, 2021):
definitely in favor of this feature too!
@c-nv-s commented on GitHub (Nov 30, 2021):
@hibiken any update on this request?
@hibiken commented on GitHub (Nov 30, 2021):
@c-nv-s thank you for the comment!
Sorry, this feature work has been de-prioritized because I had other features to work on. I'm currently working on metrics related work, so I may be able to work on this soon.
But if anyone's interested, feel free to open a PR for this 👍
@mdibaiee commented on GitHub (Dec 31, 2021):
Hello 👋
I just saw this issue and thought it was easy enough to fix in my spare time, so I just created a PR. Happy to apply any feedback you have on it.
P.S.: Happy new year!