Skip to content

Commit 26a5c52

Browse files
authored
Merge pull request #112409 from rboucher/DLogtoRLog
rename diagnostic logs to resource logs part 1
2 parents acda18e + f5232d8 commit 26a5c52

File tree

67 files changed

+232
-232
lines changed

Some content is hidden

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

67 files changed

+232
-232
lines changed

articles/active-directory/reports-monitoring/howto-integrate-activity-logs-with-arcsight.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ Download and open the [configuration guide for ArcSight SmartConnector for Azure
5050
* The application settings from your deployment are persisted in the Application Settings in Azure Function Apps.
5151
* A new resource group for ArcSight is created in Azure, with an Azure AD application for the ArcSight connector and storage accounts containing the mapped files in CEF format.
5252

53-
4. Finally, complete the post-deployment steps in the **Post-Deployment Configurations** of the configuration guide. This section explains how to perform additional configuration if you are on an App Service Plan to prevent the function apps from going idle after a timeout period, configure streaming of diagnostic logs from the event hub, and update the SysLog NG Daemon SmartConnector keystore certificate to associate it with the newly created storage account.
53+
4. Finally, complete the post-deployment steps in the **Post-Deployment Configurations** of the configuration guide. This section explains how to perform additional configuration if you are on an App Service Plan to prevent the function apps from going idle after a timeout period, configure streaming of resource logs from the event hub, and update the SysLog NG Daemon SmartConnector keystore certificate to associate it with the newly created storage account.
5454

5555
5. The configuration guide also explains how to customize the connector properties in Azure, and how to upgrade and uninstall the connector. There is also a section on performance improvements, including upgrading to an [Azure Consumption plan](https://azure.microsoft.com/pricing/details/functions) and configuring an ArcSight Load Balancer if the event load is greater than what a single Syslog NG Daemon SmartConnector can handle.
5656

articles/active-directory/reports-monitoring/reference-azure-monitor-sign-ins-log-schema.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -167,4 +167,4 @@ This article describes the Azure Active Directory (Azure AD) sign-in log schema
167167
## Next steps
168168

169169
* [Interpret audit logs schema in Azure Monitor](reference-azure-monitor-audit-log-schema.md)
170-
* [Read more about Azure diagnostic logs](../../azure-monitor/platform/platform-logs-overview.md)
170+
* [Read more about Azure platform logs](../../azure-monitor/platform/platform-logs-overview.md)

articles/active-directory/users-groups-roles/directory-admin-roles-secure.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -287,7 +287,7 @@ Use Privileged identity Management with Azure AD administrator roles to manage,
287287

288288
#### Use Azure log integrations to send relevant Azure logs to your SIEM systems
289289

290-
Azure log integration enables you to integrate raw logs from your Azure resources to your organization’s existing Security Information and Event Management (SIEM) systems. [Azure log integration](../../security/fundamentals/azure-log-integration-overview.md) collects Windows events from Windows Event Viewer logs, and Azure resources from Azure Activity Logs, Azure Security Center alerts, and Azure Diagnostic logs.
290+
Azure log integration enables you to integrate raw logs from your Azure resources to your organization’s existing Security Information and Event Management (SIEM) systems. [Azure log integration](../../security/fundamentals/azure-log-integration-overview.md) collects Windows events from Windows Event Viewer logs, and Azure resources from Azure activity Logs, Azure Security Center alerts, and Azure resource logs.
291291

292292

293293
### Additional steps for organizations managing access to other cloud apps via Azure AD

articles/aks/cluster-autoscaler.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -209,7 +209,7 @@ AKS manages the cluster autoscaler on your behalf and runs it in the managed con
209209

210210
To configure logs to be pushed from the cluster autoscaler into Log Analytics, follow these steps.
211211

212-
1. Set up a rule for diagnostic logs to push cluster-autoscaler logs to Log Analytics. [Instructions are detailed here](https://docs.microsoft.com/azure/aks/view-master-logs#enable-diagnostics-logs), ensure you check the box for `cluster-autoscaler` when selecting options for "Logs".
212+
1. Set up a rule for resource logs to push cluster-autoscaler logs to Log Analytics. [Instructions are detailed here](https://docs.microsoft.com/azure/aks/view-master-logs#enable-resource-logs), ensure you check the box for `cluster-autoscaler` when selecting options for "Logs".
213213
1. Click on the "Logs" section on your cluster via the Azure portal.
214214
1. Input the following example query into Log Analytics:
215215

articles/aks/view-master-logs.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,9 +15,9 @@ With Azure Kubernetes Service (AKS), the master components such as the *kube-api
1515

1616
This article requires an existing AKS cluster running in your Azure account. If you do not already have an AKS cluster, create one using the [Azure CLI][cli-quickstart] or [Azure portal][portal-quickstart]. Azure Monitor logs works with both RBAC and non-RBAC enabled AKS clusters.
1717

18-
## Enable diagnostics logs
18+
## Enable resource logs
1919

20-
To help collect and review data from multiple sources, Azure Monitor logs provides a query language and analytics engine that provides insights to your environment. A workspace is used to collate and analyze the data, and can integrate with other Azure services such as Application Insights and Security Center. To use a different platform to analyze the logs, you can instead choose to send diagnostic logs to an Azure storage account or event hub. For more information, see [What is Azure Monitor logs?][log-analytics-overview].
20+
To help collect and review data from multiple sources, Azure Monitor logs provides a query language and analytics engine that provides insights to your environment. A workspace is used to collate and analyze the data, and can integrate with other Azure services such as Application Insights and Security Center. To use a different platform to analyze the logs, you can instead choose to send resource logs to an Azure storage account or event hub. For more information, see [What is Azure Monitor logs?][log-analytics-overview].
2121

2222
Azure Monitor logs are enabled and managed in the Azure portal. To enable log collection for the Kubernetes master components in your AKS cluster, open the Azure portal in a web browser and complete the following steps:
2323

articles/analysis-services/analysis-services-logging.md

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Diagnostic logging for Azure Analysis Services | Microsoft Docs
3-
description: Describes how to setup up Azure resource diagnostic logging to monitoring your Azure Analysis Services server.
3+
description: Describes how to setup up logging to monitoring your Azure Analysis Services server.
44
author: minewiskan
55
ms.service: azure-analysis-services
66
ms.topic: conceptual
@@ -11,9 +11,9 @@ ms.reviewer: minewiskan
1111
---
1212
# Setup diagnostic logging
1313

14-
An important part of any Analysis Services solution is monitoring how your servers are performing. With [Azure resource logs](../azure-monitor/platform/platform-logs-overview.md), you can monitor and send logs to [Azure Storage](https://azure.microsoft.com/services/storage/), stream them to [Azure Event Hubs](https://azure.microsoft.com/services/event-hubs/), and export them to [Azure Monitor logs](../azure-monitor/azure-monitor-log-hub.md).
14+
An important part of any Analysis Services solution is monitoring how your servers are performing. Azure Analysis services is integrated with Azure Monitor. With [Azure Monitor resource logs](../azure-monitor/platform/platform-logs-overview.md), you can monitor and send logs to [Azure Storage](https://azure.microsoft.com/services/storage/), stream them to [Azure Event Hubs](https://azure.microsoft.com/services/event-hubs/), and export them to [Azure Monitor logs](../azure-monitor/azure-monitor-log-hub.md).
1515

16-
![Diagnostic logging to Storage, Event Hubs, or Azure Monitor logs](./media/analysis-services-logging/aas-logging-overview.png)
16+
![Resource logging to Storage, Event Hubs, or Azure Monitor logs](./media/analysis-services-logging/aas-logging-overview.png)
1717

1818
[!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]
1919

@@ -67,9 +67,9 @@ The Metrics category logs the same [Server metrics](analysis-services-monitor.md
6767

6868
### Azure portal
6969

70-
1. In [Azure portal](https://portal.azure.com) > server, click **Diagnostic logs** in the left navigation, and then click **Turn on diagnostics**.
70+
1. In [Azure portal](https://portal.azure.com) > server, click **Diagnostic settings** in the left navigation, and then click **Turn on diagnostics**.
7171

72-
![Turn on diagnostic logging for Azure Cosmos DB in the Azure portal](./media/analysis-services-logging/aas-logging-turn-on-diagnostics.png)
72+
![Turn on resource logging for Azure Cosmos DB in the Azure portal](./media/analysis-services-logging/aas-logging-turn-on-diagnostics.png)
7373

7474
2. In **Diagnostic settings**, specify the following options:
7575

@@ -79,31 +79,31 @@ The Metrics category logs the same [Server metrics](analysis-services-monitor.md
7979
* **Stream to an event hub**. To use this option, you need an existing Event Hub namespace and event hub to connect to. To learn more, see [Create an Event Hubs namespace and an event hub using the Azure portal](../event-hubs/event-hubs-create.md). Then return to this page in the portal to select the Event Hub namespace and policy name.
8080
* **Send to Azure Monitor (Log Analytics workspace)**. To use this option, either use an existing workspace or [create a new workspace](../azure-monitor/learn/quick-create-workspace.md) resource in the portal. For more information on viewing your logs, see [View logs in Log Analytics workspace](#view-logs-in-log-analytics-workspace) in this article.
8181

82-
* **Engine**. Select this option to log xEvents. If you're archiving to a storage account, you can select the retention period for the diagnostic logs. Logs are autodeleted after the retention period expires.
83-
* **Service**. Select this option to log service level events. If you are archiving to a storage account, you can select the retention period for the diagnostic logs. Logs are autodeleted after the retention period expires.
84-
* **Metrics**. Select this option to store verbose data in [Metrics](analysis-services-monitor.md#server-metrics). If you are archiving to a storage account, you can select the retention period for the diagnostic logs. Logs are autodeleted after the retention period expires.
82+
* **Engine**. Select this option to log xEvents. If you're archiving to a storage account, you can select the retention period for the resource logs. Logs are autodeleted after the retention period expires.
83+
* **Service**. Select this option to log service level events. If you are archiving to a storage account, you can select the retention period for the resource logs. Logs are autodeleted after the retention period expires.
84+
* **Metrics**. Select this option to store verbose data in [Metrics](analysis-services-monitor.md#server-metrics). If you are archiving to a storage account, you can select the retention period for the resource logs. Logs are autodeleted after the retention period expires.
8585

8686
3. Click **Save**.
8787

8888
If you receive an error that says "Failed to update diagnostics for \<workspace name>. The subscription \<subscription id> is not registered to use microsoft.insights." follow the [Troubleshoot Azure Diagnostics](https://docs.microsoft.com/azure/log-analytics/log-analytics-azure-storage) instructions to register the account, then retry this procedure.
8989

90-
If you want to change how your diagnostic logs are saved at any point in the future, you can return to this page to modify settings.
90+
If you want to change how your resource logs are saved at any point in the future, you can return to this page to modify settings.
9191

9292
### PowerShell
9393

9494
Here are the basic commands to get you going. If you want step-by-step help on setting up logging to a storage account by using PowerShell, see the tutorial later in this article.
9595

96-
To enable metrics and diagnostics logging by using PowerShell, use the following commands:
96+
To enable metrics and resource logging by using PowerShell, use the following commands:
9797

98-
- To enable storage of diagnostics logs in a storage account, use this command:
98+
- To enable storage of resource logs in a storage account, use this command:
9999

100100
```powershell
101101
Set-AzDiagnosticSetting -ResourceId [your resource id] -StorageAccountId [your storage account id] -Enabled $true
102102
```
103103

104104
The storage account ID is the resource ID for the storage account where you want to send the logs.
105105

106-
- To enable streaming of diagnostics logs to an event hub, use this command:
106+
- To enable streaming of resource logs to an event hub, use this command:
107107

108108
```powershell
109109
Set-AzDiagnosticSetting -ResourceId [your resource id] -ServiceBusRuleId [your service bus rule id] -Enabled $true
@@ -115,7 +115,7 @@ To enable metrics and diagnostics logging by using PowerShell, use the following
115115
{service bus resource ID}/authorizationrules/{key name}
116116
```
117117

118-
- To enable sending diagnostics logs to a Log Analytics workspace, use this command:
118+
- To enable sending resource logs to a Log Analytics workspace, use this command:
119119

120120
```powershell
121121
Set-AzDiagnosticSetting -ResourceId [your resource id] -WorkspaceId [resource id of the log analytics workspace] -Enabled $true
@@ -321,6 +321,6 @@ Set-AzDiagnosticSetting -ResourceId $account.ResourceId`
321321

322322
## Next steps
323323

324-
Learn more about [Azure resource diagnostic logging](../azure-monitor/platform/platform-logs-overview.md).
324+
Learn more about [Azure Monitor resource logging](../azure-monitor/platform/platform-logs-overview.md).
325325

326326
See [Set-AzDiagnosticSetting](https://docs.microsoft.com/powershell/module/az.monitor/set-azdiagnosticsetting) in PowerShell help.

articles/analysis-services/analysis-services-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -227,7 +227,7 @@ Modern data exploration and visualization tools like Power BI, Excel, Reporting
227227

228228
## Monitoring and diagnostics
229229

230-
Azure Analysis Services is integrated with Azure metrics, providing an extensive number of resource-specific metrics to help you monitor the performance and health of your servers. To learn more, see [Monitor server metrics](analysis-services-monitor.md). Record metrics with [Azure resource diagnostic logs](../azure-monitor/platform/platform-logs-overview.md). Monitor and send logs to [Azure Storage](https://azure.microsoft.com/services/storage/), stream them to [Azure Event Hubs](https://azure.microsoft.com/services/event-hubs/), and export them to [Azure Monitor logs](https://azure.microsoft.com/services/log-analytics/), a service of [Azure](https://www.microsoft.com/cloud-platform/operations-management-suite). To learn more, see [Setup diagnostic logging](analysis-services-logging.md).
230+
Azure Analysis Services is integrated with Azure Monitor metrics, providing an extensive number of resource-specific metrics to help you monitor the performance and health of your servers. To learn more, see [Monitor server metrics](analysis-services-monitor.md). Record metrics with [resource platform logs](../azure-monitor/platform/platform-logs-overview.md). Monitor and send logs to [Azure Storage](https://azure.microsoft.com/services/storage/), stream them to [Azure Event Hubs](https://azure.microsoft.com/services/event-hubs/), and export them to [Azure Monitor logs](https://azure.microsoft.com/services/log-analytics/), a service of [Azure](https://www.microsoft.com/cloud-platform/operations-management-suite). To learn more, see [Setup diagnostic logging](analysis-services-logging.md).
231231

232232
Azure Analysis Services also supports using [Dynamic Management Views (DMVs)](https://docs.microsoft.com/analysis-services/instances/use-dynamic-management-views-dmvs-to-monitor-analysis-services). Based on SQL syntax, DMVs interface schema rowsets that return metadata and monitoring information about server instance.
233233

articles/api-management/api-management-advanced-policies.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ This topic provides a reference for the following API Management policies. For i
3434
- [Set request method](#SetRequestMethod) - Allows you to change the HTTP method for a request.
3535
- [Set status code](#SetStatus) - Changes the HTTP status code to the specified value.
3636
- [Set variable](api-management-advanced-policies.md#set-variable) - Persists a value in a named [context](api-management-policy-expressions.md#ContextVariables) variable for later access.
37-
- [Trace](#Trace) - Adds custom traces into the [API Inspector](https://azure.microsoft.com/documentation/articles/api-management-howto-api-inspector/) output, Application Insights telemetries, and Diagnostic Logs.
37+
- [Trace](#Trace) - Adds custom traces into the [API Inspector](https://azure.microsoft.com/documentation/articles/api-management-howto-api-inspector/) output, Application Insights telemetries, and Resource Logs.
3838
- [Wait](#Wait) - Waits for enclosed [Send request](api-management-advanced-policies.md#SendRequest), [Get value from cache](api-management-caching-policies.md#GetFromCacheByKey), or [Control flow](api-management-advanced-policies.md#choose) policies to complete before proceeding.
3939

4040
## <a name="choose"></a> Control flow
@@ -910,11 +910,11 @@ Expressions used in the `set-variable` policy must return one of the following b
910910

911911
## <a name="Trace"></a> Trace
912912

913-
The `trace` policy adds a custom trace into the API Inspector output, Application Insights telemetries, and/or Diagnostic Logs.
913+
The `trace` policy adds a custom trace into the API Inspector output, Application Insights telemetries, and/or Resource Logs.
914914

915915
- The policy adds a custom trace to the [API Inspector](https://azure.microsoft.com/documentation/articles/api-management-howto-api-inspector/) output when tracing is triggered, i.e. `Ocp-Apim-Trace` request header is present and set to true and `Ocp-Apim-Subscription-Key` request header is present and holds a valid key that allows tracing.
916916
- The policy creates a [Trace](https://docs.microsoft.com/azure/azure-monitor/app/data-model-trace-telemetry) telemetry in Application Insights, when [Application Insights integration](https://docs.microsoft.com/azure/api-management/api-management-howto-app-insights) is enabled and the `severity` level specified in the policy is at or higher than the `verbosity` level specified in the diagnostic setting.
917-
- The policy adds a property in the log entry when [Diagnostic Logs](https://docs.microsoft.com/azure/api-management/api-management-howto-use-azure-monitor#diagnostic-logs) is enabled and the severity level specified in the policy is at or higher than the verbosity level specified in the diagnostic setting.
917+
- The policy adds a property in the log entry when [Resource Logs](https://docs.microsoft.com/azure/api-management/api-management-howto-use-azure-monitor#diagnostic-logs) is enabled and the severity level specified in the policy is at or higher than the verbosity level specified in the diagnostic setting.
918918

919919
### Policy statement
920920

0 commit comments

Comments
 (0)