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-app-configuration/faq.yml
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -118,17 +118,17 @@ sections:
118
118
119
119
Premium tier stores also have a daily usage charge and include a replica. The first 800,000 requests for the origin and the first 800,000 requests for the replica each day are included in the daily charge. Requests exceeding this daily allocation incur an overage charge.
120
120
121
-
- question: How do I track who is accessing my App Configuration store?
121
+
- question: How do I identify who has accessed my App Configuration store?
122
122
answer: |
123
-
Azure App Configuration provides logs that can help track who is accessing your App Configuration store. To learn how to enable log collection see the [log collection](./monitor-app-configuration.md#log-collection) section in the 'Monitoring App Configuration' document. For considerations on which specific logs to use to track access, refer to the [data access tracking](./monitor-app-configuration.md#data-access-tracking) section.
123
+
To see who has accessed your App Configuration store, see [Activity logs](./monitor-app-configuration.md#activity-logs). To see who has accessed your data plane resources, see [Resource logs](./monitor-app-configuration.md#resource-logs).
124
124
125
125
- question: Can I upgrade or downgrade an App Configuration store?
126
126
answer: |
127
127
You can upgrade an App Configuration store at any time, for example, from the Free tier to the Developer, Standard or Premium tier, or from the Developer, Standard tier to the Premium tier.
128
128
129
129
You can downgrade an App Configuration store from the Premium tier to the Standard tier, as both tiers are designed for production usage. However, downgrading to a non-production tier, such as the Free tier, isn't supported. To achieve this, you can create a new store in the desired tier and then [import configuration data into that store](howto-import-export-data.md).
130
130
131
-
Before downgrading an App Configuration store from the Premium tier to the Standard tier, ensure that your usage of regular storage and snapshot storage is below the limits of the Standard tier. You can verify your current usage through the [Azure Monitor metrics](monitor-app-configuration.md#metric-analysis), Daily Storage Usage and Snapshot Storage Size, of your App Configuration store in the Azure portal.
131
+
Before downgrading an App Configuration store from the Premium tier to the Standard tier, ensure that your usage of regular storage and snapshot storage is below the limits of the Standard tier. You can verify your current usage through the [Azure Monitor metrics](monitor-app-configuration.md#metrics-analysis), Daily Storage Usage and Snapshot Storage Size, of your App Configuration store in the Azure portal.
132
132
133
133
- question: Where does data stored in App Configuration reside?
Copy file name to clipboardExpand all lines: articles/azure-app-configuration/monitor-app-configuration-reference.md
+42-15Lines changed: 42 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,21 +15,22 @@ ms.custom: horz-monitor
15
15
16
16
This article is a reference for the monitoring data collected by App Configuration. See [Monitoring App Configuration](monitor-app-configuration.md) for how to collect and analyze monitoring data for App Configuration.
Resource Provider and Type: [App Configuration Platform Metrics](/azure/azure-monitor/essentials/metrics-supported#microsoftappconfigurationconfigurationstores)
20
20
21
21
| Metric | Unit | Description |
22
22
|-------|-----| ----- |
23
-
| HTTP Incoming Request Count | Count | Total number of incoming HTTP requests|
23
+
| HTTP Incoming Request Count | Count | Total number of incoming HTTP Request|
24
24
| HTTP Incoming Request Duration | Milliseconds | Server side duration of an HTTP Request |
25
25
| Throttled HTTP Request Count | Count | Throttled requests are HTTP requests that receive a response with a status code of 429 |
26
26
| Daily Storage Usage | Percent | Represents the amount of storage in use as a percentage of the maximum allowance. This metric is updated at least once daily. |
27
27
| Request Quota Usage | Percent | Represents the current total request usage in percentage. |
28
28
| Replication Latency | Milliseconds | Represents the average time it takes for a replica to be consistent with current state. |
29
-
| Snapshot Storage Size | Count | Represents the total storage usage of configuration snapshots in bytes. |
29
+
| Snapshot Storage Size | Count | Represents the total storage usage of configuration snapshot(s) in bytes. |
30
30
31
31
For more information, see a list of [all platform metrics supported in Azure Monitor](/azure/azure-monitor/essentials/metrics-supported).
32
32
33
+
33
34
## Metric Dimensions
34
35
App Configuration has the following dimensions associated with its metrics.
35
36
@@ -38,23 +39,21 @@ App Configuration has the following dimensions associated with its metr
38
39
| HTTP Incoming Request Count | The supported dimensions are the **HttpStatusCode**, **AuthenticationScheme**, and **Endpoint** of each request. **AuthenticationScheme** can be filtered by "AAD" or "HMAC" authentication. |
39
40
| HTTP Incoming Request Duration | The supported dimensions are the **HttpStatusCode**, **AuthenticationScheme**, and **Endpoint** of each request. **AuthenticationScheme** can be filtered by "AAD" or "HMAC" authentication. |
40
41
| Throttled HTTP Request Count | The **Endpoint** of each request is included as a dimension. |
41
-
| Daily Storage Usage | This metric doesn't have any dimensions. |
42
+
| Daily Storage Usage | This metric does not have any dimensions. |
42
43
| Request Quota Usage | The supported dimensions are the **OperationType** ("Read"or "Write") and **Endpoint** of each request. |
43
-
| Replication Latency |This metric includes an **Endpoint**dimension that identifies the replica to which data was replicated. |
44
-
| Snapshot Storage Size | This metric doesn't have any dimensions. |
44
+
| Replication Latency |The **Endpoint**of the replica that data was replicated to is included as a dimension. |
45
+
| Snapshot Storage Size | This metric does not have any dimensions. |
45
46
46
47
For more information on what metric dimensions are, see [Multi-dimensional metrics](/azure/azure-monitor/essentials/data-platform-metrics#multi-dimensional-metrics).
47
48
48
49
## Resource logs
49
50
This section lists the category types of resource log collected for App Configuration.
50
51
51
-
### Supported logs for Microsoft.AppConfiguration/configurationStores
52
-
| Category | Category display name | Log table |
53
-
|-------|-----|-----|
54
-
|`HttpRequest`| HTTP Requests |[AACHttpRequest](/azure/azure-monitor/reference/tables/AACHttpRequest)<br>Incoming requests to Azure App Configuration. The records in this table are aggregated. The 'HitCount' field describes the number of requests that each record accounts for. |
For more schema information, see a list of [Common and service-specific schemas for Azure resourcelogs](/azure/azure-monitor/essentials/resource-logs-schema).
56
+
For more information, see a list of [all resourcelogs category types supported in Azure Monitor](/azure/azure-monitor/essentials/resource-logs-schema).
58
57
59
58
## Azure Monitor Logs tables
60
59
@@ -66,9 +65,37 @@ This section refers to all of the Azure Monitor Logs Kusto tables re
66
65
|[AACHttpRequest](/azure/azure-monitor/reference/tables/AACHttpRequest)| Entries of every HTTP request sent to a selected app configuration resource. |
67
66
|[AzureActivity](/azure/azure-monitor/reference/tables/AzureActivity)| Entries from the Azure Activity log that provide insight into any subscription-level or management group level events that have occurred in Azure. |
68
67
69
-
For a reference of all Azure Monitor Logs / Log Analytics tables for App Configuration, see the [Log Analytics tables for microsoft.appconfiguration/configurationstores](/azure/azure-monitor/reference/tables/microsoft-appconfiguration_configurationstores).
68
+
For a reference of all Azure Monitor Logs / Log Analytics tables, see the [Azure Monitor Log Table Reference](/azure/azure-monitor/reference/tables/microsoft-appconfiguration_configurationstores).
69
+
70
+
### Diagnostics tables
71
+
72
+
App Configuration uses the [AACHttpRequest Table](/azure/azure-monitor/reference/tables/aachttprequest) to store resource log information.
73
+
74
+
**HTTP Requests**
75
+
76
+
|Property | Type | Description |
77
+
|-------|-----| ----- |
78
+
|Category |string |The log category of the event, always HttpRequest.
79
+
|ClientIPAddress | string| IP Address of the client that sent the request.
80
+
|ClientRequestId| string| Request ID provided by client.
81
+
|CorrelationId| string| An ID provided by the client to correlate multiple requests.
82
+
|DurationMs| int |The duration of the operation in milliseconds.
83
+
|HitCount| int |The number of requests that the record is associated with.
84
+
|Method string| HTTP| HTTP request method (get or post)
85
+
|RequestId| string| Unique request ID generated by server.
86
+
|RequestLength| int |Length in bytes of the HTTP request.
87
+
|RequestURI| string| URI of the request, can include key and label name.
88
+
|_ResourceId| string| A unique identifier for the resource that the record is associated with
89
+
|ResponseLength| int| Length in bytes of the HTTP response.
90
+
|SourceSystem| string|
91
+
|StatusCode| int |HTTP Status Code of the request.
92
+
|TenantId| string |WorkspaceId of the request.
93
+
|TimeGenerated| datetime| Timestamp (UTC) when log was generated because a request was sent
94
+
|Type |string| The name of the table
95
+
|UserAgent| string| User Agent provided by the client.
96
+
70
97
71
98
## See Also
72
99
73
100
* See [Monitoring Azure App Configuration](monitor-app-configuration.md) for a description of monitoring Azure App Configuration.
74
-
* See [Monitoring Azure resources with Azure Monitor](/azure/azure-monitor/essentials/monitor-azure-resource) for details on monitoring Azure resources.
101
+
* See [Monitoring Azure resources with Azure Monitor](/azure/azure-monitor/essentials/monitor-azure-resource) for details on monitoring Azure resources.
0 commit comments