When you configure an entity for SolarWinds Observability, log monitoring may automatically begin. Logs and other data may be detected at the same time. For example, SolarWinds Observability may receive logs from a cloud monitored host, as well as logs created by host monitoring agents. You can also send logs directly to SolarWinds Observability for ingestion and analysis.
These logs can be monitored to track activity, analyze trends, and alert you to problems with the host or device from which the logs came.
Monitor logs in SolarWinds Observability
Use the OTel-based SolarWinds Observability Agent to collect and send logs, or configure your application or host to send logs directly to the SolarWinds Observability endpoint URL using an ingestion API token. Logs can be sent via HTTPS or syslog, or from your cloud provider with an AWS lambda function or Azure event function.
To collect logs for a services entity monitored by an APM library, configure the library to include trace context with the application logs, send application logs using syslog, and associate the syslog logs with the service entity. Application logs can also be sent via HTTPS, but the logs may not be able to be associated with the service entity.
To send logs with the SolarWinds Observability Agent or using HTTPS or syslog, complete the following steps:
In SolarWinds Observability, click Add Data at the top.
In the Add Data dialog, click Logs.
Create or select an API ingestion token to use when sending your logs by doing either of the following:
- Select Generate New Token and enter an Ingestion Token Name, then click Next.
- Select Use Existing Token and select an ingestion token from the list, then click Next.
Select a message logging standard to send your logs and click Next.
Follow the configuration instructions provided to start sending logs.
Click View Logs.
For detailed instructions on how to send logs in specific scenarios, see: