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

Add additional metrics #254

Open
Neverlord opened this issue Jul 9, 2022 · 0 comments
Open

Add additional metrics #254

Neverlord opened this issue Jul 9, 2022 · 0 comments
Assignees

Comments

@Neverlord
Copy link
Member

To allow users to better understand what Broker is doing and to understand the health of the system, we need additional metrics. The list we've came up with so far:

  • Unsent messages, i.e., number of buffered messages at the core actor
  • Unsent bytes, i.e., accumulated sizes of buffered messages
  • Input and output channels of stores (a master will have one channel per clone)
  • Number of entries in the data store
  • Number of buffered commands, i.e., command messages that wait for one or more ACKs

Ideas for metrics that would need some extra clarification or are not straightforward to implement:

  • High-water metrics, e.g., largest message yet / highest amount of buffered messages?
  • Latencies: this one is tricky, because ideally this time would be measured from creating an event (in Zeek) to writing the message to a socket; however, messages currently have no timestamps
@Neverlord Neverlord self-assigned this Aug 6, 2022
timwoj added a commit that referenced this issue Sep 20, 2022
* origin/topic/neverlord/gh-254:
  Get initial number of entries from the backend
  Add additional health and performance metrics
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant