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

ENH: idea - keep event rate (events/sec) in bot and show in intelmq-manager #361

Open
aaronkaplan opened this issue Oct 7, 2015 · 1 comment
Labels
component: bots feature Indicates new feature requests or new features usability

Comments

@aaronkaplan
Copy link
Member

While observing intelmq-manager and monitoring the throughput of different bots, I noticed that you can only get a snapshot in time of the queue length. However, the snapshot really depends on the processing speed of the bot and when the snapshot is done. This does not tell you very well, how fast a bot is processing data.
Therefore, I'd like to propose that each bot keeps an internal counter for an event rate (events/sec) and that it exposes that info to intelmq-manager.

@aaronkaplan aaronkaplan added feature Indicates new feature requests or new features not priority component: bots labels Oct 7, 2015
@aaronkaplan aaronkaplan added this to the Release 3 milestone Oct 7, 2015
@sebix
Copy link
Member

sebix commented Mar 1, 2016

We had the idea to save such statistical data and status information in redis as simple keys. The bot writes his data there after one process()-call.

@ghost ghost mentioned this issue Jul 17, 2018
e3rd added a commit that referenced this issue Jul 20, 2018
@ghost ghost modified the milestones: 2.0.0, 2.1.0 Apr 10, 2019
@ghost ghost modified the milestones: 2.1.0, 2.2.0 Oct 25, 2019
@ghost ghost removed this from the 2.2.0 milestone Jun 17, 2020
@ghost ghost removed the not priority label Aug 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: bots feature Indicates new feature requests or new features usability
Projects
None yet
Development

No branches or pull requests

2 participants