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/sentinel/sap/deployment-solution-configuration.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
@@ -106,17 +106,17 @@ By default, all analytics rules provided in the Microsoft Sentinel solution for
106
106
107
107
To enable or disable the ingestion of a specific log:
108
108
109
-
1. Edit the *systemconfig.ini* file located under */opt/sapcon/SID/* on the connector's VM.
109
+
1. Edit the *systemconfig.json* file located under */opt/sapcon/SID/* on the connector's VM.
110
110
1. Inside the configuration file, locate the relevant log and do one of the following:
111
111
- To enable the log, change the value to `True`.
112
112
- To disable the log, change the value to `False`.
113
113
114
114
For example, to stop ingestion for the `ABAPJobLog`, change its value to `False`:
115
115
116
116
```
117
-
ABAPJobLog = False
117
+
"abapjoblog": "True",
118
118
```
119
-
Review the list of available logs in the [Systemconfig.ini file reference](reference-systemconfig.md#logs-activation-status-section).
119
+
Review the list of available logs in the [Systemconfig.json file reference](reference-systemconfig-json.md).
120
120
121
121
You can also [stop ingesting the user master data tables](sap-solution-deploy-alternate.md#configuring-user-master-data-collection).
122
122
@@ -130,9 +130,9 @@ You can also [stop ingesting the user master data tables](sap-solution-deploy-al
130
130
To stop ingesting SAP logs into the Microsoft Sentinel workspace, and to stop the data stream from the Docker container, run this command:
131
131
132
132
```
133
-
docker stop sapcon-[SID]
133
+
docker stop sapcon-[SID/agent-name]
134
134
```
135
-
135
+
To stop ingesting a specific SID for a multi-SID container you must delete the SID from the connector page UI in Sentinel
136
136
The Docker container stops and doesn't send any more SAP logs to the Microsoft Sentinel workspace. This stops both the ingestion and billing for the SAP system related to the connector.
137
137
138
138
If you need to reenable the Docker container, run this command:
0 commit comments