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

Let the Checkmate Capture agent push data to the Hub #1702

Open
jk779 opened this issue Feb 6, 2025 · 1 comment
Open

Let the Checkmate Capture agent push data to the Hub #1702

jk779 opened this issue Feb 6, 2025 · 1 comment
Labels
future-consideration Not currently prioritized

Comments

@jk779
Copy link

jk779 commented Feb 6, 2025

Is your feature request related to a problem? Please describe.

Sometimes, it's a hassle to open the port for the capture agent or you don't have a static ip address to configure. Both would be typical for example in a scenario when you want to monitor a server at your home. I guess there are many other occasions where this could happen, for example in with kubernetes where you would have much configuration to do.

Describe the solution you'd like

Make it possible to configure an capture agent to start the communication with the Checkmate Hub API.
The agent would also need to pull its config from the hub (like: "report every 15 seconds"). With this, it can send the same stats it delivers now on get requets with posts to the hub.

A gratis perk is that the sent data is probably encrypted, because it likely that the hub is running on https, rather then an agent on a system that has not already an infrastructure for serving SSL.

Describe alternatives you've considered

In most situations this would only be convenience feature, so this is not a showstopper anywhere i guess.

Additionally, this could generate a shadow IT in edge cases, e.g. in classic development agencies, because a developer doesn't have to talk to OPS people to open ports.

@gorkem-bwl gorkem-bwl added the future-consideration Not currently prioritized label Feb 6, 2025
@gorkem-bwl
Copy link
Contributor

Thanks for this Michael. We had to make a decision pull vs push, and most of the platforms have gone with pull method, that is how it is implemented. The whole server backend runs with pull method so it'd be a bit cumbersome to be able to change pull vs push for some of the monitors. I've added future-consideration label for now :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
future-consideration Not currently prioritized
Projects
None yet
Development

No branches or pull requests

2 participants