Skip to content

Commit e45e5fa

Browse files
authored
Merge branch 'main' into DOCS-483
2 parents 1e57c41 + 5a37d47 commit e45e5fa

File tree

3 files changed

+9
-5
lines changed

3 files changed

+9
-5
lines changed

.clabot

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -168,7 +168,8 @@
168168
"Andrew-L-Johnson",
169169
"Ayah-Saleh",
170170
"ishaanahuja29",
171-
"raunakmandaokar"
171+
"raunakmandaokar",
172+
"bradtho"
172173
],
173174
"message": "Thank you for your contribution! As this is an open source project, we require contributors to sign our Contributor License Agreement and do not have yours on file. To proceed with your PR, please [sign your name here](https://forms.gle/YgLddrckeJaCdZYA6) and we'll add you to our approved list of contributors.",
174175
"label": "cla-signed",

docs/integrations/containers-orchestration/opentelemetry/docker-opentelemetry.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ Metrics are collected through the [Docker Stats Receiver](https://github.com/ope
4343
To collect the Docker container event logs, the following command needs to be executed on the host machine and needs to be kept running, for monitoring all the Docker container-related events. The following command also needs a JSON file path where these container events can be dumped.
4444

4545
```
46-
docker events docker events -f 'type=container' --format '{{json .}}' > <PATH_TO_JSON> & disown
46+
docker events -f 'type=container' --format '{{json .}}' > <PATH_TO_JSON> & disown
4747
```
4848
Path to this JSON file will be required in the [next step](#step-2-configure-integration), where events are sent to Sumo Logic through a filelog receiver and seen as part of the **Docker - Overview** dashboard. Also, you can add additional parameters to this command to send events for specific containers. [Learn more](https://docs.docker.com/engine/reference/commandline/events/).
4949

docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/armis-api-source.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,8 +16,11 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
1616

1717
<img src={useBaseUrl('img/send-data/armis-icon.png')} alt="armis-icon.png" width="80" />
1818

19-
Armis API is a device security platform that discover devices, tracks behavior, detects threats, and takes action to protect your business.
20-
The Source integration ingests alert and device data from the Armis platform.
19+
Armis API is a device security platform that discover devices, tracks behavior, detects threats, and takes action to protect your business. The Source integration ingests alert and device data from the Armis platform.
20+
21+
:::sumo Best Practice
22+
Armis and Sumo Logic recommend using the Armis SIEM Integration, which pushes logs from Armis to a Sumo Logic HTTP source. There is a known limitation with the Armis API’s time query parameters, which can result in missing logs when using the Cloud-to-Cloud source. To avoid this, we advise using the Armis-side integration instead.
23+
:::
2124

2225
## Data collected
2326

@@ -107,4 +110,4 @@ Sources can be configured using UTF-8 encoded JSON files with the Collector Ma
107110

108111
:::info
109112
Click [here](/docs/c2c/info) for more information about Cloud-to-Cloud sources.
110-
:::
113+
:::

0 commit comments

Comments
 (0)