Skip to content

Commit

Permalink
fix(logs): Fix some messed-up link syntax (#5823)
Browse files Browse the repository at this point in the history
  • Loading branch information
austin-schaefer committed Feb 2, 2022
1 parent 34f2287 commit e753886
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions src/content/docs/logs/ui-data/use-logs-ui.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ redirects:
- /docs/logs/log-management/ui-and-data
---

Use the Logs UI at **[one.newrelic.com](https://one.newrelic.com)** or our [EU region data center](/docs/using-new-relic/welcome-new-relic/get-started/our-eu-us-region-data-centers/) (if applicable) at **[one.eu.newrelic.com/](https://one.eu.newrelic.com)** to:
Use the Logs UI at **[one.newrelic.com](https://one.newrelic.com)** or our [EU region data center](/docs/using-new-relic/welcome-new-relic/get-started/our-eu-us-region-data-centers/) (if applicable) at **[one.eu.newrelic.com](https://one.eu.newrelic.com)** to:

* Spot interesting or significant patterns in your logs.
* Examine more context around a particular log line.
Expand Down Expand Up @@ -133,7 +133,7 @@ Here are a few examples of how you can use the Logs UI to get detailed informati
id="troubleshoot-error"
title="Troubleshoot an error (logs in context)"
>
To troubleshoot errors this way, you must be able to see [logs in context]/docs/logs/logs-context/configure-logs-context-apm-agents/). Then, to have a better understanding of what was happening on the host at the time an error occurred in your app:
To troubleshoot errors this way, you must be able to see [logs in context](/docs/logs/logs-context/configure-logs-context-apm-agents/). Then, to have a better understanding of what was happening on the host at the time an error occurred in your app:

1. Go to **APM > (select an app) > Events > Error analytics** and select an error trace.
2. From the error trace **Details**, click **See logs**.
Expand Down

0 comments on commit e753886

Please sign in to comment.