Troubleshooting

Each LM Logs integration article has discusses troubleshooting tips for that integration. This section offers tips for identifying and troubleshooting common issues with LM Logs.

Not seeing logs?

If you are not seeing any logs after you’ve set up ingestion, it may be caused by bad resource mapping or your LogicMonitor portal may be in maintenance mode.

Bad resource mapping

Resource mapping can fail when either a resource is not found or there are multiple resources found with the same ID. Events that cannot be associated with a LogicMonitor resource are dropped. 

• For logs that are forwarded from Amazon CloudWatch using the AWS integration, the LogicMonitor resource is mapped to the AWS ARN value by default. 
• For logs forwarded from the Fluentd plugin, you will need to define the resource mapping when you configure the plugin.

LogicMonitor is unavailable

You will not see new logs arrive when your LogicMonitor portal is in maintenance mode and LogicMonitor will return a 502 - Bad Gateway status code. During this time, logs should be cached by the client.