Skip to content

Commit badc9ba

Browse files
committed
updating page for AMA agent
1 parent 6233656 commit badc9ba

File tree

1 file changed

+12
-16
lines changed

1 file changed

+12
-16
lines changed

articles/sentinel/sap/collect-sap-hana-audit-logs.md

Lines changed: 12 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22
title: Collect SAP HANA audit logs in Microsoft Sentinel | Microsoft Docs
33
description: This article explains how to collect audit logs from your SAP HANA database.
4-
author: yelevin
5-
ms.author: yelevin
4+
author: batamig
5+
ms.author: bagol
66
ms.topic: how-to
7-
ms.date: 05/24/2023
7+
ms.date: 06/09/2024
88
---
99

1010
# Collect SAP HANA audit logs in Microsoft Sentinel
@@ -14,7 +14,7 @@ This article explains how to collect audit logs from your SAP HANA database.
1414
> [!IMPORTANT]
1515
> Microsoft Sentinel SAP HANA support is currently in PREVIEW. The [Azure Preview Supplemental Terms](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) include additional legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
1616
17-
If you have SAP HANA database audit logs configured with Syslog, you'll also need to configure your Log Analytics agent to collect the Syslog files.
17+
If you have SAP HANA database audit logs configured with Syslog, you'll also need to configure your AMA agent or Log Analytics agent (legacy) to collect the Syslog files.
1818

1919
## Collect SAP HANA audit logs
2020

@@ -25,24 +25,20 @@ If you have SAP HANA database audit logs configured with Syslog, you'll also nee
2525

2626
1. Check your operating system Syslog files for any relevant HANA database events.
2727

28-
1. Install and configure a Log Analytics agent on your machine:
28+
1. Sign into your HANA database operating system as a user with sudo privileges.
2929

30-
1. Sign in to your HANA database operating system as a user with sudo privileges.
30+
1. Install an agent on your machine and confirm that your machine is connected. For more information, see:
3131

32-
1. In the Azure portal, go to your Log Analytics workspace. On the left pane, under **Settings**, select **Agents management** > **Linux servers**.
32+
- [Azure Monitor Agent](/azure/azure-monitor/agents/azure-monitor-agent-manage?tabs=azure-portal)
33+
- [Log Analytics Agent](../../azure-monitor/agents/agent-linux.md) (legacy)
3334

34-
1. Under **Download and onboard agent for Linux**, copy the code that's displayed in the box to your terminal, and then run the script.
35+
1. Configure your agent to collect Syslog data. For more information, see:
3536

36-
The Log Analytics agent is installed on your machine and connected to your workspace. For more information, see [Install Log Analytics agent on Linux computers](../../azure-monitor/agents/agent-linux.md) and [OMS Agent for Linux](https://github.com/microsoft/OMS-Agent-for-Linux) on the Microsoft GitHub repository.
37-
38-
1. Refresh the **Agents Management > Linux servers** tab to confirm that you have **1 Linux computers connected**.
39-
40-
1. On the left pane, under **Settings**, select **Agents configuration**, and then select the **Syslog** tab.
41-
42-
1. Select **Add facility** to add the facilities you want to collect.
37+
- [Azure Monitor Agent](/azure/azure-monitor/agents/data-collection-syslog)
38+
- [Log Analytics Agent](/azure/azure-monitor/agents/data-sources-syslog) (legacy)
4339

4440
> [!TIP]
45-
> Because the facilities where HANA database events are saved can change between different distributions, we recommend that you add all facilities, check them against your Syslog logs, and then remove any that aren't relevant.
41+
> Because the facilities where HANA database events are saved can change between different distributions, we recommend that you add all facilities. Check them against your Syslog logs, and then remove any that aren't relevant.
4642
>
4743
4844
1. In Microsoft Sentinel, check to confirm that HANA database events are now shown in the ingested logs.

0 commit comments

Comments
 (0)