Skip to content
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

Adds lag_in_actions to metrics #811

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Conversation

viktorerlingsson
Copy link
Member

WHAT is this pull request doing?

Adds number of unsynced actions as lag_in_actions to metrics, by checking the size of the @actions channel's internal Dequeue.

HOW can this pull request be tested?

Manual

@carlhoerberg
Copy link
Member

But it's not the whole story, right? Actions could still be in the tcp send buffer, or being processed at the follower.

@viktorerlingsson
Copy link
Member Author

But it's not the whole story, right? Actions could still be in the tcp send buffer, or being processed at the follower.

Hmm, yeah that's true. And I guess there's no good way for us to know how many actions are there. 🤔

@@ -177,6 +177,7 @@ module LavinMQ
sent_bytes: @sent_bytes,
acked_bytes: @acked_bytes,
lag_in_bytes: lag_in_bytes,
lag_in_actions: lag_in_actions,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We talked about calling it clustering_actions_queue_size instead

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

Successfully merging this pull request may close these issues.

max_lag is in nr of actions but lag is in nr of bytes
4 participants