Come join our live training webinar every other Wednesday at 11am PST and hear LogicMonitor experts explain best practices and answer common questions. We understand these are uncertain times, and we are here to help!
LogicMonitor may require credentials (for example, JDBC passwords, SNMP community strings, SSH username, and so on) in order to collect data from your devices. You can use properties to set this information at the global, group, or device level.
The level where you choose to set properties for your device may depend on how many devices that property applies to. For example, if you use the same SNMP community string for all Linux devices, you may want to set this property at the group level instead of at the device level for each individual Linux device in your account. For strategies and instructions on where and how to set properties, see Resource and Instance Properties.
The following table lists many predefined properties that can be used to store credentials (and authentication details) for various common protocols and systems.
Note: Any values assigned to properties with names ending in .pass .*password, .*credential, .auth, .key, or password will be obfuscated throughout the LogicMonitor interface for security purposes. In addition, values assigned to the following properties will also be obfuscated: snmp.community, snmp.privtoken, snmp.authtoken, aws.accesskey, (\\S+((\\.pass)|(\\.auth)|( .key))), azure .secretkey, (saas .(privatekey|secretkey)), gcp .serviceaccountkey, (collector\\.sqs .(awsaccesskey|awssecretkey)), and (gcccli.accesskey).
In this section we have listed all the system credentials and their values. You may refer the notes for additional information about the property.
In this section we have listed all the protocol credentials and their values. You may refer the notes for additional information about the property.
LogicMonitor can use SNMP versions 1, 2c or 3. If your device supports 2c, it supports 64-bit counters and is preferable over version 1. SNMPv3 adds authentication and encryption, making it more secure, but also more complicated to set up and troubleshoot.
For SNMP versions 1 and 2c, you need to set the snmp.community property (defined in the table above).
For SNMPv3, to communicate with authentication and privacy (referred to as authPriv security level), you need to set the snmp.security, snmp.auth, snmp.authToken, snmp.priv, and snmp.privToken properties (all defined in the table above).
If communicating with authentication only (no privacy), referred to as authNoPriv, include the snmp.priv and snmp.privToken properties, but leave them blank.
SNMPv3 also introduces support for snmp.contextName and snmp.contextEngineID. The snmp.contextEngineID value is a string used to identify the device on which the management information is hosted. The snmp.contextName identifies the individual SNMP context.
In This Article