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
As i understand it, RTOP is a pull based model where a central server ssh's in on some schedule and runs and grabs data. But i am thinking about adapting the model. Dont kil me, but just discussing....
It should be pretty easy to make it just a config setting perhaps..
Run a Scheduler in golang. Easy. Set by config
Runs the standard stats collector
Pushes the data up to the standard endpoint.
The reason for this Question 7 Issue, is because i have devices out in the field, with the IP address dynamic. Its IOT style world :)
dont want to break all the other bits to this - for example the central server can be make to work with both push and pull model.
Would be curious of your thoughts. DO you support this ? DO you want to kill me for suggesting this ? etc
The text was updated successfully, but these errors were encountered:
There already are such software out there -- try collectd or munin if you want open source, or RapidLoop's own software OpsDash as a commercial option.
As i understand it, RTOP is a pull based model where a central server ssh's in on some schedule and runs and grabs data. But i am thinking about adapting the model. Dont kil me, but just discussing....
It should be pretty easy to make it just a config setting perhaps..
The reason for this Question 7 Issue, is because i have devices out in the field, with the IP address dynamic. Its IOT style world :)
dont want to break all the other bits to this - for example the central server can be make to work with both push and pull model.
Would be curious of your thoughts. DO you support this ? DO you want to kill me for suggesting this ? etc
The text was updated successfully, but these errors were encountered: