Skip to content

Commit e067b1e

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into normesta-reg-updates-11
2 parents 862e00b + d2d1f32 commit e067b1e

File tree

8 files changed

+103
-1
lines changed

8 files changed

+103
-1
lines changed
Lines changed: 95 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,95 @@
1+
---
2+
title: How to manage audit logs for Microsoft Azure Data Manager for Energy Preview
3+
description: Learn how to use audit logs on Azure Data Manager for Energy Preview
4+
author: sandeepchads
5+
ms.author: sancha
6+
ms.service: energy-data-services
7+
ms.topic: how-to
8+
ms.date: 04/11/2023
9+
ms.custom: template-how-to
10+
#Customer intent: As a developer, I want to use audit logs to check audit trail for data plane APIs for Azure Data Manager for Energy Preview.
11+
---
12+
13+
14+
# Manage audit logs
15+
Audit logs provide auditing trails for data plane APIs on Azure Data Manager for Energy. With audit logs, you can tell:
16+
* Who performed an action
17+
* What was the action
18+
* When was the action performed
19+
* Status of the action
20+
21+
For example, when you “Add a new member” to the ```users.datalake.admins``` entitlement group using entitlements API, you're able to see this information in audit logs.
22+
23+
[![Screenshot of audit logs for entitlement](media/how-to-manage-audit-logs/how-to-manage-audit-logs-4-entilements.png)](media/how-to-manage-audit-logs/how-to-manage-audit-logs-4-entilements.png#lightbox)
24+
25+
## Enable audit logs
26+
To enable audit logs in diagnostic logging, select your Azure Data Manager for Energy instance in the Azure portal.
27+
* Select the **Activity log** screen, and then select **Diagnostic settings**.
28+
* Select **+ Add diagnostic setting**.
29+
* Enter the Diagnostic settings name.
30+
* Select **Audit Events** as the Category.
31+
32+
[![Screenshot of audit events option in diagnostic settings](media/how-to-manage-audit-logs/how-to-manage-audit-logs-1-audit-event-diagnostic-logs.png)](media/how-to-manage-audit-logs/how-to-manage-audit-logs-1-audit-event-diagnostic-logs.png#lightbox)
33+
34+
* Select appropriate Destination details for accessing the diagnostic logs.
35+
36+
> [!NOTE]
37+
> It might take up to 15 minutes for the first Logs to show in Log Analytics.
38+
For information on how to work with diagnostic logs, see [Azure Resource Log documentation.](../azure-monitor/essentials/platform-logs-overview.md)
39+
40+
## Audit log details
41+
The audit logs for Azure Data Manager for Energy service returns the following fields.
42+
43+
|Field Name| Type| Description|
44+
|----------|----------|----------------|
45+
| TenantID | String | The tenant of your Azure Data Manager for Energy instance.|
46+
| TimeGenerated | UTC format | The time of the audit log. |
47+
| Category | String | The diagnostic settings category to which the logs belong.|
48+
| Location | string | Location of the Azure Data Manager for Energy resource. |
49+
| ServiceName | String | Name of OSDU service running in Azure Data Manager for Energy. For example: Partition, Search, Indexer, Legal, Entitlements, Workflow, Register, Unit, Crs-catalog, File, Schema, and Dataset |
50+
| OperationName | String |Operation ID or operation name associated to data plane APIs, which emits audit logs for example "Add member" |
51+
| Data partition ID | String | Data partition ID on which operation is performed. |
52+
| Action | String | Action refers to the type of operation that is, whether it's create, delete, update etc.|
53+
| ActionID | String | ID associated with operation. |
54+
| PuID | String | ObjectId of the user in Azure AD|
55+
| ResultType | String | Define success or failure of operation |
56+
| Operation Description | String | Provides specific details of the response. These details can include tracing information, such as the symptoms, of the result that are used for further analysis. |
57+
| RequestId | String | This is the unique ID associated to the request, which triggered the operation on data plane. |
58+
| Message | String | Provides message associated with the success or failure of the operation.|
59+
| ResourceID | String | The Azure Data Manager for Energy resource ID of the customer under which the audit log belongs. |
60+
61+
## Sample queries
62+
63+
Basic Application Insights queries you can use to explore your log data.
64+
65+
1. Run the following query to group operations by ServiceName:
66+
67+
```sql
68+
OEPAuditLogs
69+
| summarize count() by ServiceName
70+
```
71+
72+
[![Screenshot of key vault, key, user assigned identity, and CMK on encryption tab](media/how-to-manage-audit-logs/how-to-manage-audit-logs-3-allservices.png)](media/how-to-manage-audit-logs/how-to-manage-audit-logs-3-allservices.png#lightbox)
73+
74+
2. Run the following query to see the 100 most recent logs:
75+
76+
```sql
77+
OEPAuditLogs
78+
| limit 100
79+
```
80+
81+
3. Run the following query to get all the failed results:
82+
83+
```sql
84+
OEPAuditLogs
85+
| where ResultType contains "Failure"
86+
```
87+
88+
89+
## Next steps
90+
91+
Learn about Managed Identity:
92+
> [!div class="nextstepaction"]
93+
> [Managed Identity in Azure Data Manager for Energy Preview](how-to-use-managed-identity.md)
94+
95+

articles/energy-data-services/index.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -111,4 +111,6 @@ landingContent:
111111
- text: Set up use Managed Identity
112112
url: how-to-use-managed-identity.md
113113
- text: Enable resource sharing (CORS)
114-
url: how-to-enable-cors.md
114+
url: how-to-enable-cors.md
115+
- text: Set up audit logs
116+
url: how-to-manage-audit-logs.md
Loading
494 KB
Loading
380 KB
Loading
605 KB
Loading

articles/energy-data-services/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -86,6 +86,8 @@
8686
href: how-to-convert-segy-to-ovds.md
8787
- name: Generate a refresh token
8888
href: how-to-generate-refresh-token.md
89+
- name: Set up audit logs
90+
href: how-to-manage-audit-logs.md
8991
- name: References
9092
items:
9193
- name: REST API

articles/virtual-network/ip-services/public-ip-upgrade-portal.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,9 @@ ms.custom: template-how-to, engagement-fy23
1212

1313
# Upgrade a public IP address using the Azure portal
1414

15+
>[!Important]
16+
>On September 30, 2025, Basic SKU public IPs will be retired. For more information, see the [official announcement](https://azure.microsoft.com/updates/upgrade-to-standard-sku-public-ip-addresses-in-azure-by-30-september-2025-basic-sku-will-be-retired/). If you are currently using Basic SKU public IPs, make sure to upgrade to Standard SKU public IPs prior to the retirement date.
17+
1518
Azure public IP addresses are created with a SKU, either Basic or Standard. The SKU determines their functionality including allocation method, feature support, and resources they can be associated with.
1619

1720
In this article, you'll learn how to upgrade a static Basic SKU public IP address to Standard SKU in the Azure portal.

0 commit comments

Comments
 (0)