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/unified-connector-custom-device.md
+15-33Lines changed: 15 additions & 33 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,25 +57,7 @@ Each application section contains the following information:
57
57
- The outline of the procedure required to ingest data manually, without using the connector. For the details of this procedure, see [Collect logs from text files with the Azure Monitor Agent and ingest to Microsoft Sentinel](connect-custom-logs-ama.md).
58
58
- Specific instructions for configuring the originating applications or devices themselves, and/or links to the instructions on the providers' web sites. These steps must be taken whether using the connector or not.
59
59
60
-
**The following devices' instructions are provided here:**
Follow these steps to ingest log messages from Apache HTTP Server:
81
63
@@ -93,7 +75,7 @@ Follow these steps to ingest log messages from Apache HTTP Server:
93
75
94
76
[Back to list](#specific-instructions-per-application-type) | [Back to top](#custom-logs-via-ama-data-connector---configure-data-ingestion-to-microsoft-sentinel-from-specific-applications)
95
77
96
-
###Apache Tomcat
78
+
## Apache Tomcat
97
79
98
80
Follow these steps to ingest log messages from Apache Tomcat:
99
81
@@ -110,7 +92,7 @@ Follow these steps to ingest log messages from Apache Tomcat:
110
92
111
93
[Back to list](#specific-instructions-per-application-type) | [Back to top](#custom-logs-via-ama-data-connector---configure-data-ingestion-to-microsoft-sentinel-from-specific-applications)
112
94
113
-
###Cisco Meraki
95
+
## Cisco Meraki
114
96
115
97
Follow these steps to ingest log messages from Cisco Meraki:
116
98
@@ -196,7 +178,7 @@ Follow these steps to ingest log messages from Cisco Meraki:
196
178
197
179
[Back to list](#specific-instructions-per-application-type) | [Back to top](#custom-logs-via-ama-data-connector---configure-data-ingestion-to-microsoft-sentinel-from-specific-applications)
198
180
199
-
### JBoss Enterprise Application Platform
181
+
## JBoss Enterprise Application Platform
200
182
201
183
Follow these steps to ingest log messages from JBoss Enterprise Application Platform:
202
184
@@ -214,7 +196,7 @@ Follow these steps to ingest log messages from JBoss Enterprise Application Plat
214
196
215
197
[Back to list](#specific-instructions-per-application-type) | [Back to top](#custom-logs-via-ama-data-connector---configure-data-ingestion-to-microsoft-sentinel-from-specific-applications)
216
198
217
-
### JuniperIDP
199
+
## JuniperIDP
218
200
219
201
Follow these steps to ingest log messages from JuniperIDP:
220
202
@@ -284,7 +266,7 @@ Follow these steps to ingest log messages from JuniperIDP:
284
266
285
267
[Back to list](#specific-instructions-per-application-type) | [Back to top](#custom-logs-via-ama-data-connector---configure-data-ingestion-to-microsoft-sentinel-from-specific-applications)
286
268
287
-
### MarkLogic Audit
269
+
## MarkLogic Audit
288
270
289
271
Follow these steps to ingest log messages from MarkLogic Audit:
290
272
@@ -310,7 +292,7 @@ Follow these steps to ingest log messages from MarkLogic Audit:
310
292
311
293
[Back to list](#specific-instructions-per-application-type) | [Back to top](#custom-logs-via-ama-data-connector---configure-data-ingestion-to-microsoft-sentinel-from-specific-applications)
312
294
313
-
### MongoDB Audit
295
+
## MongoDB Audit
314
296
315
297
Follow these steps to ingest log messages from MongoDB Audit:
316
298
@@ -334,7 +316,7 @@ Follow these steps to ingest log messages from MongoDB Audit:
334
316
335
317
[Back to list](#specific-instructions-per-application-type) | [Back to top](#custom-logs-via-ama-data-connector---configure-data-ingestion-to-microsoft-sentinel-from-specific-applications)
336
318
337
-
### NGINX HTTP Server
319
+
## NGINX HTTP Server
338
320
339
321
Follow these steps to ingest log messages from NGINX HTTP Server:
340
322
@@ -351,7 +333,7 @@ Follow these steps to ingest log messages from NGINX HTTP Server:
351
333
352
334
[Back to list](#specific-instructions-per-application-type) | [Back to top](#custom-logs-via-ama-data-connector---configure-data-ingestion-to-microsoft-sentinel-from-specific-applications)
353
335
354
-
### Oracle WebLogic Server
336
+
## Oracle WebLogic Server
355
337
356
338
Follow these steps to ingest log messages from Oracle WebLogic Server:
357
339
@@ -369,7 +351,7 @@ Follow these steps to ingest log messages from Oracle WebLogic Server:
369
351
370
352
[Back to list](#specific-instructions-per-application-type) | [Back to top](#custom-logs-via-ama-data-connector---configure-data-ingestion-to-microsoft-sentinel-from-specific-applications)
371
353
372
-
### PostgreSQL Events
354
+
## PostgreSQL Events
373
355
374
356
Follow these steps to ingest log messages from PostgreSQL Events:
375
357
@@ -392,7 +374,7 @@ Follow these steps to ingest log messages from PostgreSQL Events:
392
374
393
375
[Back to list](#specific-instructions-per-application-type) | [Back to top](#custom-logs-via-ama-data-connector---configure-data-ingestion-to-microsoft-sentinel-from-specific-applications)
394
376
395
-
### SecurityBridge Threat Detection for SAP
377
+
## SecurityBridge Threat Detection for SAP
396
378
397
379
Follow these steps to ingest log messages from SecurityBridge Threat Detection for SAP:
398
380
@@ -409,7 +391,7 @@ Follow these steps to ingest log messages from SecurityBridge Threat Detection f
409
391
410
392
[Back to list](#specific-instructions-per-application-type) | [Back to top](#custom-logs-via-ama-data-connector---configure-data-ingestion-to-microsoft-sentinel-from-specific-applications)
411
393
412
-
### SquidProxy
394
+
## SquidProxy
413
395
414
396
Follow these steps to ingest log messages from SquidProxy:
415
397
@@ -427,7 +409,7 @@ Follow these steps to ingest log messages from SquidProxy:
427
409
428
410
[Back to list](#specific-instructions-per-application-type) | [Back to top](#custom-logs-via-ama-data-connector---configure-data-ingestion-to-microsoft-sentinel-from-specific-applications)
429
411
430
-
### Ubiquiti UniFi
412
+
## Ubiquiti UniFi
431
413
432
414
Follow these steps to ingest log messages from Ubiquiti UniFi:
433
415
@@ -495,7 +477,7 @@ Follow these steps to ingest log messages from Ubiquiti UniFi:
495
477
496
478
[Back to list](#specific-instructions-per-application-type) | [Back to top](#custom-logs-via-ama-data-connector---configure-data-ingestion-to-microsoft-sentinel-from-specific-applications)
497
479
498
-
### VMware vCenter
480
+
## VMware vCenter
499
481
500
482
Follow these steps to ingest log messages from VMware vCenter:
501
483
@@ -571,7 +553,7 @@ Follow these steps to ingest log messages from VMware vCenter:
571
553
572
554
[Back to list](#specific-instructions-per-application-type) | [Back to top](#custom-logs-via-ama-data-connector---configure-data-ingestion-to-microsoft-sentinel-from-specific-applications)
573
555
574
-
### Zscaler Private Access (ZPA)
556
+
## Zscaler Private Access (ZPA)
575
557
576
558
Follow these steps to ingest log messages from Zscaler Private Access (ZPA):
0 commit comments