+1 On May 23, 2016 4:53 PM, "Eric Kuhnke" <eric.kuh...@gmail.com> wrote:
> This doesn't scale on a large cacti installation with hundreds of hosts and > 60-second poller intervals. Cacti data input method scripts spawn a new php > worker for each data acquisition target (they do NOT use the 'spine' SNMP > poller). > > Exposing the data via SNMP on the host to be monitored distributes the CPU > load individually onto each host (example: an 'extend' script in the > snmpd.conf which runs "curl http://localhost/server-status"; for apache2 > status and parses the results) rather than centralizing it on the cacti > host. > > This allows cacti or opennms or anything else to poll the hosts to be > monitored via something that scales better than php script workers, using > the 'spine' SNMP data acquisition method and the equivalent in other snmp > polling platforms. > > > On Sat, May 21, 2016 at 6:03 AM, Eric Lindsjö <e...@emj.se> wrote: > > > Hi Nathan, > > > > You should probably write a cacti script to ingest the data instead of > > this SNMP proxy thing. Writing scripts to ingest data into cacti is > simple, > > you just need to output the values you want in key: value format and then > > do some clicking in cacti. There are good docs for how to do this. > > > > -- emj > > > > > > On 05/21/2016 08:11 AM, Nathan Anderson wrote: > > > >> Hey, thanks guys! I had never really looked that deeply into Net-SNMP > >> and had only ever installed it either to use as a client > (snmpget/snmpwalk) > >> or a basic agent w/ standard MIBs for the host it's running on, so I was > >> unaware of its extensibility. And it even looks like it ships with a > Perl > >> module. That sounds like a perfect solution; thanks for pointing me in > the > >> right direction. > >> > >> -- Nathan > >> > > > > >
