Sponsored Content
Full Discussion: Monitoring Solution
Top Forums UNIX for Advanced & Expert Users Monitoring Solution Post 302970242 by bobochacha29 on Monday 4th of April 2016 08:44:01 AM
Old 04-04-2016
Quote:
Originally Posted by cjcox
snmp is your friend. A lot of those "tools" are not much more than "pretty" snmp based tools. Cacti might be an ok option just because the community often has add-ons for many enterprise things (like switches, routers, SAN, storage, hypervisors).

If you study what others have done you'll find you can write or modify Cacti to fit specific needs.

Could you give me a software, a name ... that I can find to test. Thanks
 

2 More Discussions You Might Find Interesting

1. Cybersecurity

best monitoring solution

Hi people, i would like to know your opinion about the best monitor solution that can: - monitor OS (could be ubuntu, AIX, HP-UX, redhat,...) - monitor BD (ORACLE, Mysql,...) - monitor specific services - scipts that i develop for monitoring them - have parent and child architecture, for... (1 Reply)
Discussion started by: gfca
1 Replies

2. Infrastructure Monitoring

How to install Cacti (a system monitoring and graphing solution) with Nginx?

Here's a short tutorial on installing Cacti with Nginx on Linux. (0 Replies)
Discussion started by: notblog
0 Replies
snmp.conf(5)							    Apple Inc.							      snmp.conf(5)

NAME
snmp.conf - snmp configuration file for cups DESCRIPTION
The snmp.conf file configures how the standard CUPS network backends (http, https, ipp, ipps, lpd, snmp, and socket) access printer infor- mation using SNMPv1 and is normally located in the /etc/cups directory. Each line in the file can be a configuration directive, a blank line, or a comment. Comment lines start with the # character. The Community and DebugLevel directives are used by all backends. The remainder apply only to the SNMP backend (cups-snmp(8)). DIRECTIVES
The following directives are understood by the CUPS network backends. Consult the on-line help for detailed descriptions: Address @IF(name) Address @LOCAL Address address Sends SNMP broadcast queries to the specified address(es). There is no default for the broadcast address. Community name Specifies the community name to use. Only a single community name may be specified. The default community name is "public". DebugLevel number Specifies the logging level from 0 (none) to 3 (everything). Typically only used for debugging (thus the name). The default debug level is 0. DeviceURI "regular expression" device-uri [... device-uri] Specifies one or more device URIs that should be used for a given make and model string. The regular expression is used to match the detected make and model, and the device URI strings must be of the form "scheme://%s[:port]/[path]", where "%s" represents the detected address or hostname. There are no default device URI matching rules. HostNameLookups on HostNameLookups off Specifies whether the addresses of printers should be converted to hostnames or left as numeric IP addresses. The default is "off". MaxRunTime seconds Specifies the maximum number of seconds that the SNMP backend will scan the network for printers. The default is 120 seconds (2 min- utes). SEE ALSO
cups-snmp(8), http://localhost:631/help COPYRIGHT
Copyright 2007-2013 by Apple Inc. 23 April 2012 CUPS snmp.conf(5)
All times are GMT -4. The time now is 03:25 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy