Documentation forServer & Application Monitor
Monitoring your applications and environment is a key capability of Hybrid Cloud Observability and is also available in a standalone module, Server & Application Monitor (SAM). Hybrid Cloud Observability and SAM are built on the self-hosted SolarWinds Platform.

Use the Certificate Credentials Library to store SSH keys for Linux/Unix script monitors

Typically, you must associate credentials with component monitors to enable them to retrieve application data. For added security, SAM also includes a Certificate Credential Library where you can store certificate details for SSH keys required for script monitoring, including:

  • User Name
  • Private Key: Upload a private key file or paste the private key in PEM format.
  • Key Type: RSA or DSA
  • Password (optional)

Certificates can be used to authenticate Linux devices monitored in SAM. Linux, Unix, and Nagios script monitors also support certificate-based authentication.

The Certificate Credentials Library differs from the Credentials Library that stores standard authentication credentials for component monitors. For example, a WMI component monitor may need to run as a particular user (or service account) to collect information. See Use the Credentials Library for SAM component monitor credentials and the Setting Credentials in SAM video.

To access the Certificate Credentials Library:

  1. Click Settings > All Settings.
  2. Under Product Specific Settings, click SAM Settings.
  3. Click Certificate Credentials Library.

Assign certificate credentials

There are several ways to assign Certificate Credentials:

Before you begin, choose the right method

  • If each node uses unique private keys, editing the application after it's assigned is the best option.
  • If most nodes use the same private key, edit the credentials directly in the template.

You'll be prompted to provide the following details for each credential:

  • Credential Name: User-defined text that identifies the credential for later use in templates.
  • User Name: The user who is associated with the public key certificate on the target computer.
  • Key: Text content of the private certificate file in Privacy Enhanced Mail (PEM) format.
  • Key type: The algorithm the certificate used to generate the certificate pair. Those details are usually included in the header. For example, --- BEGIN RSA PRIVATE KEY---.
  • Key password: The password used to protect the certificate file

Assign certificate credentials when assigning a template to a node

  1. Assign a template to a node.
  2. When asked to choose credentials, select the "Inherit credentials" from template option.
  3. Click Assign Application Monitors and then click Edit next to the template name.

  4. Select one or more Linux/Unix/Nagios script component monitors to edit by checking the boxes to the left of each monitor and clicking Multi-Edit.
  5. Check the Authentication Type box and select User name and PrivateKey from the drop-down menu.
  6. Check the Credential for Monitoring box, select the credentials from the drop-down menu, and click Save.

Assign certificate credentials when editing a template directly

  1. Click Settings > All Settings > Settings > Manage Templates.

  2. Select the template and click Edit.

  3. Change the Authentication Type option to User name and PrivateKey for each component monitor that uses that type of authentication.
  4. In the Credential for Monitoring field drop-down menu, select a set of credentials.
  5. Click Submit.