Skip to content

Commit 4f494c2

Browse files
committed
Merge branch 'horizontals-cosmos-db' of https://github.com/AbbyMSFT/azure-docs-pr into horz-monitor-cosmosdb
2 parents 3ad31bd + 5fe8e0c commit 4f494c2

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

44 files changed

+1124
-1255
lines changed

.openpublishing.redirection.azure-monitor.json

Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1515,6 +1515,46 @@
15151515
"redirect_url": "/azure/azure-monitor/app/usage-workbooks",
15161516
"redirect_document_id": false
15171517
},
1518+
{
1519+
"source_path_from_root": "/articles/azure-monitor/app/usage-overview.md",
1520+
"redirect_url": "/azure/azure-monitor/app/usage",
1521+
"redirect_document_id": false
1522+
},
1523+
{
1524+
"source_path_from_root": "/articles/azure-monitor/app/usage-segmentation.md",
1525+
"redirect_url": "/azure/azure-monitor/app/usage",
1526+
"redirect_document_id": false
1527+
},
1528+
{
1529+
"source_path_from_root": "/articles/azure-monitor/app/usage-funnels.md",
1530+
"redirect_url": "/azure/azure-monitor/app/usage",
1531+
"redirect_document_id": false
1532+
},
1533+
{
1534+
"source_path_from_root": "/articles/azure-monitor/app/usage-cohorts.md",
1535+
"redirect_url": "/azure/azure-monitor/app/usage",
1536+
"redirect_document_id": false
1537+
},
1538+
{
1539+
"source_path_from_root": "/articles/azure-monitor/app/usage-impact.md",
1540+
"redirect_url": "/azure/azure-monitor/app/usage",
1541+
"redirect_document_id": false
1542+
},
1543+
{
1544+
"source_path_from_root": "/articles/azure-monitor/app/usage-retention.md",
1545+
"redirect_url": "/azure/azure-monitor/app/usage",
1546+
"redirect_document_id": false
1547+
},
1548+
{
1549+
"source_path_from_root": "/articles/azure-monitor/app/usage-flows.md",
1550+
"redirect_url": "/azure/azure-monitor/app/usage",
1551+
"redirect_document_id": false
1552+
},
1553+
{
1554+
"source_path_from_root": "/articles/azure-monitor/app/usage-heart.md",
1555+
"redirect_url": "/azure/azure-monitor/app/usage",
1556+
"redirect_document_id": false
1557+
},
15181558
{
15191559
"source_path_from_root": "/articles/application-insights/app-insights-visual-studio.md",
15201560
"redirect_url": "/azure/azure-monitor/app/visual-studio",

articles/azure-monitor/alerts/proactive-application-security-detection-pack.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.reviewer: yagil
1111

1212
Smart detection automatically analyzes the telemetry generated by your application, and detects potential security issues. It enables you to identify potential security problems. You can mitigate these problems by fixing the application, or by taking the necessary security measures.
1313

14-
This feature requires no special setup, other than [configuring your app to send telemetry](../app/usage-overview.md).
14+
This feature requires no special setup, other than [configuring your app to send telemetry](../app/usage.md).
1515

1616
## When would I get this type of smart detection notification?
1717
There are three types of security issues that are detected:

articles/azure-monitor/app/api-custom-events-metrics.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -147,7 +147,7 @@ telemetry.trackEvent({name: "WinGame"});
147147

148148
### Custom events in Log Analytics
149149

150-
The telemetry is available in the `customEvents` table on the [Application Insights Logs tab](../logs/log-query-overview.md) or [usage experience](usage-overview.md). Events might come from `trackEvent(..)` or the [Click Analytics Auto-collection plug-in](javascript-feature-extensions.md).
150+
The telemetry is available in the `customEvents` table on the [Application Insights Logs tab](../logs/log-query-overview.md) or [usage experience](usage.md). Events might come from `trackEvent(..)` or the [Click Analytics Auto-collection plug-in](javascript-feature-extensions.md).
151151

152152
If [sampling](./sampling.md) is in operation, the `itemCount` property shows a value greater than `1`. For example, `itemCount==10` means that of 10 calls to `trackEvent()`, the sampling process transmitted only one of them. To get a correct count of custom events, use code such as `customEvents | summarize sum(itemCount)`.
153153

@@ -683,7 +683,7 @@ The function is asynchronous for the [server telemetry channel](https://www.nuge
683683
684684
## Authenticated users
685685

686-
In a web app, users are [identified by cookies](./usage-segmentation.md#the-users-sessions-and-events-segmentation-tool) by default. A user might be counted more than once if they access your app from a different machine or browser, or if they delete cookies.
686+
In a web app, users are [identified by cookies](./usage.md#users-sessions-and-events---analyze-telemetry-from-three-perspectives) by default. A user might be counted more than once if they access your app from a different machine or browser, or if they delete cookies.
687687

688688
If users sign in to your app, you can get a more accurate count by setting the authenticated user ID in the browser code:
689689

articles/azure-monitor/app/app-insights-overview.md

Lines changed: 24 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -16,31 +16,35 @@ Azure Monitor Application Insights, a feature of [Azure Monitor](..\overview.md)
1616
Application Insights provides many experiences to enhance the performance, reliability, and quality of your applications.
1717

1818
### Investigate
19-
- [Application dashboard](overview-dashboard.md): An at-a-glance assessment of your application's health and performance.
20-
- [Application map](app-map.md): A visual overview of application architecture and components' interactions.
21-
- [Live metrics](live-stream.md): A real-time analytics dashboard for insight into application activity and performance.
22-
- [Transaction search](transaction-search-and-diagnostics.md?tabs=transaction-search): Trace and diagnose transactions to identify issues and optimize performance.
23-
- [Availability view](availability-overview.md): Proactively monitor and test the availability and responsiveness of application endpoints.
24-
- [Failures view](failures-and-performance-views.md?tabs=failures-view): Identify and analyze failures in your application to minimize downtime.
25-
- [Performance view](failures-and-performance-views.md?tabs=performance-view): Review application performance metrics and potential bottlenecks.
19+
20+
* [Application dashboard](overview-dashboard.md): An at-a-glance assessment of your application's health and performance.
21+
* [Application map](app-map.md): A visual overview of application architecture and components' interactions.
22+
* [Live metrics](live-stream.md): A real-time analytics dashboard for insight into application activity and performance.
23+
* [Transaction search](transaction-search-and-diagnostics.md?tabs=transaction-search): Trace and diagnose transactions to identify issues and optimize performance.
24+
* [Availability view](availability-overview.md): Proactively monitor and test the availability and responsiveness of application endpoints.
25+
* [Failures view](failures-and-performance-views.md?tabs=failures-view): Identify and analyze failures in your application to minimize downtime.
26+
* [Performance view](failures-and-performance-views.md?tabs=performance-view): Review application performance metrics and potential bottlenecks.
2627

2728
### Monitoring
28-
- [Alerts](../alerts/alerts-overview.md): Monitor a wide range of aspects of your application and trigger various actions.
29-
- [Metrics](../essentials/metrics-getting-started.md): Dive deep into metrics data to understand usage patterns and trends.
30-
- [Diagnostic settings](../essentials/diagnostic-settings.md): Configure streaming export of platform logs and metrics to the destination of your choice.
31-
- [Logs](../logs/log-analytics-overview.md): Retrieve, consolidate, and analyze all data collected into Azure Monitoring Logs.
32-
- [Workbooks](../visualize/workbooks-overview.md): Create interactive reports and dashboards that visualize application monitoring data.
29+
30+
* [Alerts](../alerts/alerts-overview.md): Monitor a wide range of aspects of your application and trigger various actions.
31+
* [Metrics](../essentials/metrics-getting-started.md): Dive deep into metrics data to understand usage patterns and trends.
32+
* [Diagnostic settings](../essentials/diagnostic-settings.md): Configure streaming export of platform logs and metrics to the destination of your choice.
33+
* [Logs](../logs/log-analytics-overview.md): Retrieve, consolidate, and analyze all data collected into Azure Monitoring Logs.
34+
* [Workbooks](../visualize/workbooks-overview.md): Create interactive reports and dashboards that visualize application monitoring data.
3335

3436
### Usage
35-
- [Users, sessions, and events](usage-segmentation.md): Determine when, where, and how users interact with your web app.
36-
- [Funnels](usage-funnels.md): Analyze conversion rates to identify where users progress or drop off in the funnel.
37-
- [Flows](usage-flows.md): Visualize user paths on your site to identify high engagement areas and exit points.
38-
- [Cohorts](usage-cohorts.md): Group users by shared characteristics to simplify trend identification, segmentation, and performance troubleshooting.
37+
38+
* [Users, sessions, and events](usage.md#users-sessions-and-events---analyze-telemetry-from-three-perspectives): Determine when, where, and how users interact with your web app.
39+
* [Funnels](usage.md#funnels---discover-how-customers-use-your-application): Analyze conversion rates to identify where users progress or drop off in the funnel.
40+
* [Flows](usage.md#user-flows---analyze-user-navigation-patterns): Visualize user paths on your site to identify high engagement areas and exit points.
41+
* [Cohorts](usage.md#cohorts---analyze-a-specific-set-of-users-sessions-events-or-operations): Group users by shared characteristics to simplify trend identification, segmentation, and performance troubleshooting.
3942

4043
### Code analysis
41-
- [Profiler](../profiler/profiler-overview.md): Capture, identify, and view performance traces for your application.
42-
- [Code optimizations](../insights/code-optimizations.md): Harness AI to create better and more efficient applications.
43-
- [Snapshot debugger](../snapshot-debugger/snapshot-debugger.md): Automatically collect debug snapshots when exceptions occur in .NET application
44+
45+
* [Profiler](../profiler/profiler-overview.md): Capture, identify, and view performance traces for your application.
46+
* [Code optimizations](../insights/code-optimizations.md): Harness AI to create better and more efficient applications.
47+
* [Snapshot debugger](../snapshot-debugger/snapshot-debugger.md): Automatically collect debug snapshots when exceptions occur in .NET application
4448

4549
## Logic model
4650

@@ -265,4 +269,4 @@ Review dedicated [troubleshooting articles](/troubleshoot/azure/azure-monitor/we
265269
- [Live metrics](live-stream.md)
266270
- [Transaction search](transaction-search-and-diagnostics.md?tabs=transaction-search)
267271
- [Availability overview](availability-overview.md)
268-
- [Users, sessions, and events](usage-segmentation.md)
272+
- [Users, sessions, and events](usage.md)

articles/azure-monitor/app/asp-net-core.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -256,7 +256,7 @@ HttpContext.Features.Get<RequestTelemetry>().Properties["myProp"] = someData
256256

257257
## Enable client-side telemetry for web applications
258258

259-
The preceding steps are enough to help you start collecting server-side telemetry. If your application has client-side components, follow the next steps to start collecting [usage telemetry](./usage-overview.md) using JavaScript (Web) SDK Loader Script injection by configuration.
259+
The preceding steps are enough to help you start collecting server-side telemetry. If your application has client-side components, follow the next steps to start collecting [usage telemetry](./usage.md) using JavaScript (Web) SDK Loader Script injection by configuration.
260260

261261
1. In `_ViewImports.cshtml`, add injection:
262262

@@ -874,7 +874,7 @@ Our [Service Updates](https://azure.microsoft.com/updates/?service=application-i
874874
875875
## Next steps
876876

877-
* [Explore user flows](./usage-flows.md) to understand how users move through your app.
877+
* [Explore user flows](./usage.md#user-flows---analyze-user-navigation-patterns) to understand how users move through your app.
878878
* [Configure a snapshot collection](./snapshot-debugger.md) to see the state of source code and variables at the moment an exception is thrown.
879879
* [Use the API](./api-custom-events-metrics.md) to send your own events and metrics for a detailed view of your app's performance and usage.
880880
* Use [availability tests](./availability-overview.md) to check your app constantly from around the world.

0 commit comments

Comments
 (0)