Skip to content

Commit d67ac2c

Browse files
committed
fixing broken bookmark
1 parent aa97950 commit d67ac2c

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

articles/azure-monitor/app/opentelemetry-enable.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ OpenTelemetry offerings are available for .NET, Node.js, Python and Java applica
2727
- <a name="PREVIEW"> :warning: 2</a>: OpenTelemetry is available as a public preview. [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/)
2828

2929
> [!NOTE]
30-
> For a feature-by-feature release status, see the [FAQ](../faq.yml#what-is-the-current-release-state-of-features-within-each-opentelemetry-offering-).
30+
> For a feature-by-feature release status, see the [FAQ](../faq.yml#what-s-the-current-release-state-of-features-within-each-opentelemetry-offering-).
3131
3232
## Get started
3333

@@ -748,7 +748,7 @@ Depending on your language and signal type, there are different ways to collect
748748

749749
The following table represents the currently supported custom telemetry types:
750750

751-
| | Custom Events | Custom Metrics | Dependencies | Exceptions | Page Views | Requests | Traces |
751+
| Custom Telemetry Types | Custom Events | Custom Metrics | Dependencies | Exceptions | Page Views | Requests | Traces |
752752
|-------------------------------------------|---------------|----------------|--------------|------------|------------|----------|--------|
753753
| **.NET** | | | | | | | |
754754
| &nbsp;&nbsp;&nbsp;OpenTelemetry API | | | Yes | Yes | | Yes | |

articles/azure-monitor/faq.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -142,7 +142,7 @@ sections:
142142
You can move a workspace between resource groups or subscriptions but not to a different region. See [Move a Log Analytics workspace to a different subscription or resource group](logs/move-workspace.md).
143143
144144
- question: |
145-
Why can't I see **Query Explorer** and **Save** buttons in Log Analytics?
145+
Why can't I see Query Explorer and Save buttons in Log Analytics?
146146
answer: |
147147
**Query Explorer**, **Save**, and **New alert rule** buttons aren't available when the [query scope](logs/scope.md) is set to a specific resource. To create alerts or save or load a query, Log Analytics must be scoped to a workspace. To open Log Analytics in workspace context, select **Logs** from the **Azure Monitor** menu. The last used workspace is selected, but you can select any other workspace. See [Log query scope and time range in Azure Monitor Log Analytics](logs/scope.md).
148148
@@ -257,7 +257,7 @@ sections:
257257
Azure Monitor Agent is the new, improved agent that consolidates features from all the other legacy monitoring agents. It also provides extra benefits like centralized data collection, filtering, and multihoming. See [Overview of the Azure Monitor agents](agents/agents-overview.md).
258258
259259
The legacy agents include:
260-
- Azure Diagnostics extension is for Azure virtual machines and collects data to Azure Monitor Metrics, Azure Storage, and Azure Event Hubs.
260+
- Azure Diagnostics extension is for Azure Virtual Machines and collects data to Azure Monitor Metrics, Azure Storage, and Azure Event Hubs.
261261
- The Log Analytics agent is for virtual machines in Azure, another cloud environment, or on-premises and collects data to Azure Monitor Logs. These agents will be deprecated by August 2024.
262262
263263
- question: |

0 commit comments

Comments
 (0)