-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Puppet Agent Monitoring #10827
Puppet Agent Monitoring #10827
Conversation
@SourceDoctor Please keep the PR structure :) |
@PipoCanaja |
Absolutely, Whatever is after |
ok :) |
@maintainer |
@PipoCanaja still not labeled after 2 month? |
Hi @SourceDoctor |
Hi @PipoCanaja You'll love Puppet if running a lot of Linux Systems. Similar continuous delivery Systems are Chef, Ansible and Saltstack. |
I am a poor network engineer :) not in charge of the systems :p But I'll have a look at some time. Until then, we need to find out a tester for this :D |
@PipoCanaja |
That's a very good beginning indeed :) |
@SourceDoctor ah, crap. Forgot to ask you to generate testdata. Could you open a pr with that? |
@Jellyfrog |
* puppet agent monitoring * change position of last run graph * device overview panel * updating documentation * mouseover for Overview Dashboard * adding blank line for code climate
This pull request has been mentioned on LibreNMS Community. There might be relevant details there: https://community.librenms.org/t/v1-61-release-changelog-february-2020/11145/1 |
monitoring puppet Agents
About Puppet:
Puppet is a mighty continuous delivery System to keep all your Servers up to date and in sync.
Also reinstallation/configuration will be massivly speeded up.
A good description/example what puppet is and can do:
https://www.guru99.com/puppet-tutorial.html
Official Page:
https://puppet.com/docs/
matching librenms-agent:
librenms/librenms-agent#258
DO NOT DELETE THIS TEXT
Please note
Testers
If you would like to test this pull request then please run:
./scripts/github-apply <pr_id>
, i.e./scripts/github-apply 10827
After you are done testing, you can remove the changes with
./scripts/github-remove
. If there are schema changes, you can ask on discord how to revert.