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

push, instead of pull #30

Closed
joeblew99 opened this issue Jan 29, 2016 · 2 comments
Closed

push, instead of pull #30

joeblew99 opened this issue Jan 29, 2016 · 2 comments

Comments

@joeblew99
Copy link

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..

  1. Run a Scheduler in golang. Easy. Set by config
  2. Runs the standard stats collector
  3. 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

@mdevan
Copy link
Contributor

mdevan commented Jan 29, 2016

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.

@joeblew99
Copy link
Author

ok thanks

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

2 participants