You can troubleshoot faster by drilling into the Logs Browser from charts, alerts, application map, and the Traces Browser.
Drill into Logs from Charts
If you have the Logs permission, you can drill into logs from charts, for example, if you notice data anomalies on a chart and want to debug the issue.
- Even if logging is enabled for your environment, this feature might have to be enabled separately. Contact technical support.
- You must have tagged the metrics and the logs from the same source with equivalent source tag values. If your metrics and logs tags don’t match, users with Accounts permissions can map the metrics tags to logs tags. For details, see Customize Logs Settings.
To drill into the related logs from a chart:
- Position your pointer over the metric for the source of concern, on the location of the anomaly.
- Right-click that point on the chart and select Logs (Beta).
In this example, you right-click the metric chart for source
db-5
at 01:25 PM
.
The Logs Browser opens in a new tab with the following configuration:
- The search time window is a 10-minute period, starting 5 minutes before and ending 5 minutes after the time of the point that you right-clicked on the chart.
- The search query includes the
source
tag as a filter for the source that you right-clicked.
In this example, the Logs Browser opens with the filter
source = db-5
and the time window 01:20 PM to 01:30 PM
(starting 5 minutes before and ending 5 minutes after 01:25 PM
).
![]() |
Drill into Logs from an Alert
If you have the Logs permission, to investigate a firing alert, you can drill into logs from the Alert Viewer. For optimal logs search results, you can configure related logs for an alert.
When you create or edit an alert, in the Related Logs panel, you can add multiple tag filters. This way, you can prepare the logs search query, which runs when the alert fires. |
![]() |
To drill into the related logs of a firing alert:
-
Go to the Alert Viewer for the alert. You have these options:
- Click the link in the alert notification.
- In the Alerts Browser, locate the firing alert and click View firing details.
- Click Show Logs Summary.
- In the Alert Log Summary panel, the
time range
filter is populated with the trigger window during which the alert condition was met and the alert transitioned to a firing state. - The histogram chart shows you the logs for the specific time grouped by the log level, such as, debug, trace, error, server, info, and warn.
- You also get to see the list of exceptions that were fired when the alert was fired. Click an exception to go to the Logs Browser and examine the logs that have the exception you selected.
- In the Alert Log Summary panel, the
-
Optionally, in the Alert Log Summary panel, adjust the filters for the logs search query.
- Click Configure log search.
- Add and remove filters from the Related Logs section, and save the alert.
Click the eye icons of the related logs filters that you want to hide from the logs search query. To unhide a filter, you must click the eye-hide icon. You cannot remove or hide the
time range
filter. -
In the Alert Log Summary panel, click Go to Logs (Beta). The Logs Browser opens in a new tab with the configurations from the Related Logs panel:
- The search time window corresponds to the
time range
value. - The search query contains the unhidden filters (with the eye icons).
- The search time window corresponds to the
![]() |
Drill into Logs from Traces
If you have the Logs permission, you can drill into logs from the application status page and the Traces Browser.
Application Status
If you notice that a service on the application map, table view, or grid view of the Application Status page has a high error percentage, you can drill down into the related logs.
- From the Map View
- Select the time window of interest.
- Click the service on the application map.
- Select View Logs (Beta).
- From the Table View
- Select the time window of interest.
- Click the ellipsis for the service.
- Select View Logs (Beta).
- From the Grid View
- Select the time window of interest.
- In a service tile, click Actions.
- Select View Logs (Beta).
The Logs Browser opens in a new tab with the following configurations:
- The search time window corresponds to the time window on the Application Status page.
- The search query contains the corresponding
service
andapplication
tag filters.
Traces Browser
If you notice a critical path through a trace in the Traces Browser, you can drill down into the related logs.
To see the logs for a trace:
- Click the trace that you want to examine.
- In the Trace Details section, click the service on which you want to focus.
- Expand the IDs section.
- Click Search Logs (Beta).
The Logs Browser opens in a new tab with the following configurations:
- By default, the search time window starts 5 seconds before the trace and ends 5 seconds after the trace.
Note: To change the default search time window for trace logs, contact Technical Support.
- The search query contains the corresponding
traceId
,source
,application
, andservice
tag filters.
To learn more about exploring traces and about finding hot spots at a glance, see Traces Browser.
![]() |
Learn More!
- Send logs.
- View and browse logs.
- Learn how to create a logs chart and add it to a dashboard.
- See Logs troubleshooting.