Skip to content

Commit 8ac7338

Browse files
committed
small acrolinx/final PR review prep fixes
1 parent 87c6f7b commit 8ac7338

File tree

10 files changed

+8
-8
lines changed

10 files changed

+8
-8
lines changed

articles/azure-monitor/app/create-new-resource.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ Sign in to the [Azure portal](https://portal.azure.com), and create an Applicati
2525
| **Name** | `Unique value` | Name that identifies the app you are monitoring. |
2626
| **Resource Group** | `myResourceGroup` | Name for the new or existing resource group to host App Insights data. |
2727
| **Region** | `East US` | Choose a location near you, or near where your app is hosted. |
28-
| **Resource Mode** | `Classic` or `Workspace-based` | Workspace-based resources are currently in public preview and allow you to send your Application Insights telemetry to a common Log Analytics workspace. For more information see the [article on workspace-based resources](create-workspace-resource.md).
28+
| **Resource Mode** | `Classic` or `Workspace-based` | Workspace-based resources are currently in public preview and allow you to send your Application Insights telemetry to a common Log Analytics workspace. For more information, see the [article on workspace-based resources](create-workspace-resource.md).
2929

3030
> [!NOTE]
3131
> While you can use the same resource name across different resource groups, it can be beneficial to use a globally unique name. This can be useful if you plan to [perform cross resource queries](https://docs.microsoft.com/azure/azure-monitor/log-query/cross-workspace-query#identifying-an-application) as it simplifies the required syntax.
@@ -93,13 +93,13 @@ For the full PowerShell documentation for this cmdlet, and to learn how to retri
9393

9494
### Azure CLI (preview)
9595

96-
To access the preview Application Insights Azure CLI commands you first need to run:
96+
To access the preview Application Insights Azure CLI commands, you first need to run:
9797

9898
```azurecli
9999
az extension add -n application-insights
100100
```
101101

102-
If you don't run the `az extension add` command you will see an error message that states: `az : ERROR: az monitor: 'app-insights' is not in the 'az monitor' command group. See 'az monitor --help'.`
102+
If you don't run the `az extension add` command, you will see an error message that states: `az : ERROR: az monitor: 'app-insights' is not in the 'az monitor' command group. See 'az monitor --help'.`
103103

104104
Now you can run the following to create your Application Insights resource:
105105

Binary file not shown.
11.4 KB
Loading
9.84 KB
Loading
Binary file not shown.
55.6 KB
Loading
44.6 KB
Loading

articles/azure-monitor/app/pricing.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -219,7 +219,7 @@ To [change the daily cap via Azure Resource Manager](../../azure-monitor/app/pow
219219

220220
### Create alerts for the Daily Cap
221221

222-
The Application Insights Daily Cap creates an event in the Azure activity log when the ingested data volumes hits the warning level or the daily cap level. You can [create an alert based on these activity log events](https://docs.microsoft.com/azure/azure-monitor/platform/alerts-activity-log#create-with-the-azure-portal). The signal names for these events are:
222+
The Application Insights Daily Cap creates an event in the Azure activity log when the ingested data volumes reaches the warning level or the daily cap level. You can [create an alert based on these activity log events](https://docs.microsoft.com/azure/azure-monitor/platform/alerts-activity-log#create-with-the-azure-portal). The signal names for these events are:
223223

224224
* Application Insights component daily cap warning threshold reached
225225

articles/azure-monitor/log-query/app-expression.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ The `app` expression is used in an Azure Monitor query to retrieve data from a s
2727

2828
| Identifier | Description | Example
2929
|:---|:---|:---|
30-
| Resource Name | Human readable name of the app (AKA "component name") | app("fabrikamapp") |
30+
| Resource Name | Human readable name of the app (Also known as "component name") | app("fabrikamapp") |
3131
| Qualified Name | Full name of the app in the form: "subscriptionName/resourceGroup/componentName" | app('AI-Prototype/Fabrikam/fabrikamapp') |
3232
| ID | GUID of the app | app("988ba129-363e-4415-8fe7-8cbab5447518") |
3333
| Azure Resource ID | Identifier for the Azure resource |app("/subscriptions/7293b69-db12-44fc-9a66-9c2005c3051d/resourcegroups/Fabrikam/providers/microsoft.insights/components/fabrikamapp") |

articles/azure-monitor/platform/log-standard-properties.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ exceptions
4747
## \_TimeReceived
4848
The **\_TimeReceived** property contains the date and time that the record was received by the Azure Monitor ingestion point in the Azure cloud. This can be useful for identifying latency issues between the data source and the cloud. An example would be a networking issue causing a delay with data being sent from an agent. See [Log data ingestion time in Azure Monitor](data-ingestion-time.md) for more details.
4949

50-
The following query gives the average latency by hour for event records from an agent. This includes the time from the agent to the cloud and and the total time for the record to be available for log queries.
50+
The following query gives the average latency by hour for event records from an agent. This includes the time from the agent to the cloud and the total time for the record to be available for log queries.
5151

5252
```Kusto
5353
Event
@@ -59,7 +59,7 @@ Event
5959
```
6060

6161
## Type and itemType
62-
The **Type** (Log Analytics workspace) and **itemType** (Application Insights application) properties hold the name of the table that the record was retrieved from which can also be thought of as the record type. This property is useful in queries that combine records from multiple table, such as those that use the `search` operator, to distinguish between records of different types. **$table** can be used in place of **Type** in some places.
62+
The **Type** (Log Analytics workspace) and **itemType** (Application Insights application) properties hold the name of the table that the record was retrieved from which can also be thought of as the record type. This property is useful in queries that combine records from multiple tables, such as those that use the `search` operator, to distinguish between records of different types. **$table** can be used in place of **Type** in some places.
6363

6464
### Examples
6565
The following query returns the count of records by type collected over the past hour.
@@ -121,7 +121,7 @@ union withsource = tt *
121121
Use these `union withsource = tt *` queries sparingly as scans across data types are expensive to execute.
122122

123123
## \_IsBillable
124-
The **\_IsBillable** property specifies whether ingested data is billable. Data with **\_IsBillable** equal to _false_ are collected for free and not billed to your Azure account.
124+
The **\_IsBillable** property specifies whether ingested data is billable. Data with **\_IsBillable** equal to `false` are collected for free and not billed to your Azure account.
125125

126126
### Examples
127127
To get a list of computers sending billed data types, use the following query:

0 commit comments

Comments
 (0)