You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-monitor/platform/diagnostic-logs-schema.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,17 +25,17 @@ A combination of the resource type (available in the `resourceId` property) and
25
25
| tenantId | Required for tenant logs | The tenant ID of the Active Directory tenant that this event is tied to. This property is only used for tenant-level logs, it does not appear in resource-level logs. |
26
26
| operationName | Required | The name of the operation represented by this event. If the event represents an RBAC operation, this is the RBAC operation name (eg. Microsoft.Storage/storageAccounts/blobServices/blobs/Read). Typically modeled in the form of a Resource Manager operation, even if they are not actual documented Resource Manager operations (`Microsoft.<providerName>/<resourceType>/<subtype>/<Write/Read/Delete/Action>`) |
27
27
| operationVersion | Optional | The api-version associated with the operation, if the operationName was performed using an API (eg. `http://myservice.windowsazure.net/object?api-version=2016-06-01`). If there is no API that corresponds to this operation, the version represents the version of that operation in case the properties associated with the operation change in the future. |
28
-
| category | Required | The log category of the event. Category is the granularity at which you can enable or disable logs on a particular resource. The properties that appear within the properties blob of an event are the same within a particular log category and resource type. Typical log categories are “Audit” “Operational” “Execution” and “Request.”|
28
+
| category | Required | The log category of the event. Category is the granularity at which you can enable or disable logs on a particular resource. The properties that appear within the properties blob of an event are the same within a particular log category and resource type. Typical log categories are "Audit" "Operational" "Execution" and "Request."|
29
29
| resultType | Optional | The status of the event. Typical values include Started, In Progress, Succeeded, Failed, Active, and Resolved. |
30
30
| resultSignature | Optional | The sub status of the event. If this operation corresponds to a REST API call, this is the HTTP status code of the corresponding REST call. |
31
-
| resultDescription | Optional | The static text description of this operation, eg. “Get storage file.”|
31
+
| resultDescription | Optional | The static text description of this operation, eg. "Get storage file."|
32
32
| durationMs | Optional | The duration of the operation in milliseconds. |
33
33
| callerIpAddress | Optional | The caller IP address, if the operation corresponds to an API call that would come from an entity with a publicly-available IP address. |
34
-
| correlationId | Optional | A GUID used to group together a set of related events. Typically, if two events have the same operationName but two different statuses (eg. “Started” and “Succeeded”), they share the same correlation ID. This may also represent other relationships between events. |
34
+
| correlationId | Optional | A GUID used to group together a set of related events. Typically, if two events have the same operationName but two different statuses (eg. "Started" and "Succeeded"), they share the same correlation ID. This may also represent other relationships between events. |
35
35
| identity | Optional | A JSON blob that describes the identity of the user or application that performed the operation. Typically this will include the authorization and claims / JWT token from active directory. |
36
36
| Level | Optional | The severity level of the event. Must be one of Informational, Warning, Error, or Critical. |
37
-
| location | Optional | The region of the resource emitting the event, eg. “East US” or “France South”|
38
-
| properties | Optional | Any extended properties related to this particular category of events. All custom/unique properties must be put inside this “Part B” of the schema. |
37
+
| location | Optional | The region of the resource emitting the event, eg. "East US" or "France South"|
38
+
| properties | Optional | Any extended properties related to this particular category of events. All custom/unique properties must be put inside this "Part B" of the schema. |
39
39
40
40
## Service-specific schemas for resource logs
41
41
The schema for resource diagnostic logs varies depending on the resource and log category. This list shows all services that make available resource logs and links to the service and category-specific schema where available.
@@ -50,7 +50,7 @@ The schema for resource diagnostic logs varies depending on the resource and log
Copy file name to clipboardExpand all lines: articles/data-factory/connector-azure-data-explorer.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,10 +16,10 @@ ms.date: 02/18/2020
16
16
17
17
# Copy data to or from Azure Data Explorer by using Azure Data Factory
18
18
19
-
This article describes how to use the copy activity in Azure Data Factory to copy data to or from [Azure Data Explorer](../data-explorer/data-explorer-overview.md). It builds on the [copy activity overview](copy-activity-overview.md) article, which offers a general overview of copy activity.
19
+
This article describes how to use the copy activity in Azure Data Factory to copy data to or from [Azure Data Explorer](/azure/data-explorer/data-explorer-overview). It builds on the [copy activity overview](copy-activity-overview.md) article, which offers a general overview of copy activity.
20
20
21
21
>[!TIP]
22
-
>For Azure Data Factory and Azure Data Explorer integration in general, learn more from [Integrate Azure Data Explorer with Azure Data Factory](../data-explorer/data-factory-integration.md).
22
+
>For Azure Data Factory and Azure Data Explorer integration in general, learn more from [Integrate Azure Data Explorer with Azure Data Factory](/azure/data-explorer/data-factory-integration).
23
23
24
24
## Supported capabilities
25
25
@@ -42,7 +42,7 @@ With the Azure Data Explorer connector, you can do the following:
42
42
## Getting started
43
43
44
44
>[!TIP]
45
-
>For a walkthrough of Azure Data Explorer connector, see [Copy data to/from Azure Data Explorer using Azure Data Factory](../data-explorer/data-factory-load-data.md) and [Bulk copy from a database to Azure Data Explorer](../data-explorer/data-factory-template.md).
45
+
>For a walkthrough of Azure Data Explorer connector, see [Copy data to/from Azure Data Explorer using Azure Data Factory](/azure/data-explorer/data-factory-load-data) and [Bulk copy from a database to Azure Data Explorer](/azure/data-explorer/data-factory-template).
@@ -58,13 +58,13 @@ The Azure Data Explorer connector uses service principal authentication. Follow
58
58
- Application key
59
59
- Tenant ID
60
60
61
-
2. Grant the service principal the correct permissions in Azure Data Explorer. See [Manage Azure Data Explorer database permissions](../data-explorer/manage-database-permissions.md) for detailed information about roles and permissions and about managing permissions. In general, you must:
61
+
2. Grant the service principal the correct permissions in Azure Data Explorer. See [Manage Azure Data Explorer database permissions](/azure/data-explorer/manage-database-permissions) for detailed information about roles and permissions and about managing permissions. In general, you must:
62
62
63
63
-**As source**, grant at least the **Database viewer** role to your database
64
64
-**As sink**, grant at least the **Database ingestor** role to your database
65
65
66
66
>[!NOTE]
67
-
>When you use the Data Factory UI to author, your login user account is used to list Azure Data Explorer clusters, databases, and tables. Manually enter the name if you don’t have permission for these operations.
67
+
>When you use the Data Factory UI to author, your login user account is used to list Azure Data Explorer clusters, databases, and tables. Manually enter the name if you don't have permission for these operations.
68
68
69
69
The following properties are supported for the Azure Data Explorer linked service:
70
70
@@ -189,7 +189,7 @@ To copy data to Azure Data Explorer, set the type property in the copy activity
189
189
|:--- |:--- |:--- |
190
190
| type | The **type** property of the copy activity sink must be set to: **AzureDataExplorerSink**. | Yes |
191
191
| ingestionMappingName | Name of a pre-created [mapping](/azure/kusto/management/mappings#csv-mapping) on a Kusto table. To map the columns from source to Azure Data Explorer (which applies to [all supported source stores and formats](copy-activity-overview.md#supported-data-stores-and-formats), including CSV/JSON/Avro formats), you can use the copy activity [column mapping](copy-activity-schema-and-type-mapping.md) (implicitly by name or explicitly as configured) and/or Azure Data Explorer mappings. | No |
192
-
| additionalProperties | A property bag which can be used for specifying any of the ingestion properties which aren’t being set already by the Azure Data Explorer Sink. Specifically, it can be useful for specifying ingestion tags. Learn more from [Azure Data Explore data ingestion doc](https://kusto.azurewebsites.net/docs/management/data-ingestion/index.html). | No |
192
+
| additionalProperties | A property bag which can be used for specifying any of the ingestion properties which aren't being set already by the Azure Data Explorer Sink. Specifically, it can be useful for specifying ingestion tags. Learn more from [Azure Data Explore data ingestion doc](https://kusto.azurewebsites.net/docs/management/data-ingestion/index.html). | No |
Copy file name to clipboardExpand all lines: articles/governance/resource-graph/overview.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,7 +63,7 @@ updated outside of Resource Manager.
63
63
Now that you have a better understanding of what Azure Resource Graph is, let's dive into how to
64
64
construct queries.
65
65
66
-
It's important to understand that Azure Resource Graph's query language is based on the [Kusto query language](../../data-explorer/data-explorer-overview.md)
66
+
It's important to understand that Azure Resource Graph's query language is based on the [Kusto query language](/azure/data-explorer/data-explorer-overview)
67
67
used by Azure Data Explorer.
68
68
69
69
First, for details on operations and functions that can be used with Azure Resource Graph, see [Resource Graph query language](./concepts/query-language.md).
0 commit comments