You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 :)
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.
The text was updated successfully, but these errors were encountered: