LibreNMS Agent


#1

So, the plan is to implement an “official” agent for LibreNMS, to supplement, but not replace, the existing monitoring featues, and to better support applications, and sort of “consolidate” the application support we have now.

High Level Plan:

1. Make list of important / desired feature set for the agent
2. create comparison of agents based on determined criteria
3. Determine if chosen solution will meet needs, or if changes need to be made
4. Test and evaluate
5. make decision

#2

Official might not be the best word for it. Maybe preferred or premiere (not a wordsmith).

But, steps look good I can’t wait to have some feedback.


#3

Yeah, fair enough. I was confident I’d have you to give me feedback on such things :wink:


#4

Is this in place of (or in addition to) the intention to more tightly integrate collectd/munnin?


#5

Yeah, I think so - well, possibly. At this stage, we are looking at what we want to use as our “agent”. So possibly collectd, OR munin, but while we plan on keeping existing integrations, I think the plan is to pick ONE and focus on it.


#6

Is there a reason we can’t use the same extension headers for both the agent AND snmp extensions?


#7

extension headers? “e agent”? you mean “the agent”?


#8

I mean can we not have the poller pick up the information for whatever is in <<>>
regardless of where it comes from?


#9

sure, but I think the problem here is, you have to write custom code to handle that information. If you use something like collectd, it writes the rrds for you…


#10

maybe we can also think about a possibility to get a client remote install done form the LibreNMS server?


#11

from the server side or the web ui? Shouldn’t be too hard to store the client install script on the server and SCP it to a client, just would need to prompt for credentials.


#12

What is the status of your Project because o you have been looking at it for a while and wondered if you are still working on it?