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!
Each LM Logs integration article discusses troubleshooting tips for that integration. This section offers tips for identifying and troubleshooting common issues with LM 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.
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.
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.
502 - Bad Gateway
In This Article