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

Expose JMX metrics for processing speed #49

Open
blootsvoets opened this issue Jun 18, 2019 · 0 comments
Open

Expose JMX metrics for processing speed #49

blootsvoets opened this issue Jun 18, 2019 · 0 comments

Comments

@blootsvoets
Copy link
Member

There is no reliable way to see how the output generation is performing. We should add metrics to have a better understanding and to monitor this. The following metrics come to mind:

  • isProcessing: whether the service is currently executing something
  • recordsProcessedCount: how many records are being processed. You can use prometheus with rate to get an insight in what the current processing rate is.
  • recordsUnprocessedCount: how many records are currently unprocessed. The baseline for this is only computed at the start of a scan cycle. Probably, this should be baseLineCount - recordsProcessedCountInCurrentBatch.
  • recordsProcessedCountInCurrentBatch
  • etaInCurrentBatch
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

1 participant