Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upCheck whether queue reporting should be adapted for new array-based channels #206
Comments
This comment has been minimized.
This comment has been minimized.
|
I am OK with purely the queue capacity and occupancy. That is fundamentally the bottleneck. |
This comment has been minimized.
This comment has been minimized.
|
Ok, cool. Closing this then. |
juliusv
closed this
Apr 29, 2013
simonpasquier
pushed a commit
to simonpasquier/prometheus
that referenced
this issue
Oct 12, 2017
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 25, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 25, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
juliusv commentedApr 29, 2013
/cc @matttproud we still only report the length/capacity of the queue channels, not how many samples each sample array in the channel contains. Should the exported value still show the total amount of samples in the channel? Then we have to change how reporting works, because we can't peek into the channel and count subelements without removing elements from the channel.