+
-## Automation installation
+## Automation bridge installation
### Ubuntu
-
-1. Click the **?** icon in the top right.
-1. Click the **UBUNTU** button.
+
+1. Click the **?** icon in the top right.
+1. In the **Automation Bridge Manual** box, click **UBUNTU**.
1. Click **Download** to download the `automation-bridge-X.X.deb` file.
-1. Copy the file to the bridge virtual machine. You can use SCP - see example below:
- ```sh
- scp -r -i /path/to/private_key /path/to/local/folder remote_user@remote_ip:/path/to/remote/folder
- ```
-3. To install the package run from ssh:
+1. Copy the file to the bridge virtual machine.
+1. To install the package run from ssh:
```sh
sudo dpkg -i automation-bridge-X.X.deb
```
### CentOS/RedHat
-1. Click the **?** icon in the top right.
-1. In the **Automation Bridge** box, click **CENTOS/REDHAT**.
+1. Click the **?** icon in the top right.
+1. In the **Automation Bridge Manual** box, click **CENTOS/REDHAT**.
1. Click **Download** to download the `automation-bridge-X.X.rpm` file.
-1. Copy the file to the bridge virtual machine (You can use SCP, see example below).
- ```sh
- scp -r -i /path/to/private_key /path/to/local/folder remote_user@remote_ip:/path/to/remote/folder
- ```
+1. Copy the file to the bridge virtual machine.
1. To install the package run from ssh:
```sh
sudo yum install automation-bridge-X.X.rpm
@@ -127,44 +124,47 @@ An example of a configuration file would be:
{
"SOAR_URL":"API_ENDPOINT_FROM_FIREWALL_DOC_FOR_YOUR_REGION",
"SOAR_TOKEN":"TOKEN_FROM_ADMINISTRATION_-->_SECURITY_-->_INSTALLATION TOKEN",
- "SIEM_URL":"https://YOUR_CSE_URL/sec",
+ "SIEM_URL":"The HTTPS Source Endpoint URL From a Hosted Sumo Logic Collector",
"ALIAS":"YOUR_ALIAS_NO_SPACES_LESS_THAN_20_CHARACTERS"
}
```
+To create a Hosted Sumo Logic Collector, see [Hosted Collectors](/docs/send-data/hosted-collectors/). To add an HTTPS Source to a Hosted Collector, see [HTTP Logs and Metrics Source](/docs/send-data/hosted-collectors/http-source/logs-metrics/).
+
+By adding this endpoint to `SIEM_URL`, this will enable the automation-bridge logs to be forwarded to Sumo Logic Log Analytics.
### Bridge ALIAS
-With bridge ALIAS, it is possible to distinguish which integration resources will be executed with this automation bridge. When a new integration resource is created or edited, it is possible to select the default ALIAS or to create a new one. So every automatic action configured to use this resource will be performed with the Bridge that has the same ALIAS.
+With bridge ALIAS, it is possible to distinguish which integration resources will be executed with this automation bridge. When a new integration resource is created or edited it is possible to select the default ALIAS or to create a new one. So every automatic action configured to use this resource will be performed with the Bridge that has the same ALIAS.
-
+
-
+
### Automation bridge update
-For Ubuntu and CentOS/RedHat, the update process works as the installation process. Follow the same steps described in [Automation bridge installation](#automation-installation) above.
+For Ubuntu and CentOS/RedHat, the update process works as the installation process. Follow the same steps described in [Automation bridge installation](#automation-bridge-installation) above.
:::note
If you are not using the SIEM:
1. Set `SIEM_URL` to `NONE`.
1. Restart the service with:
- ```sh
+ ```
systemctl restart automation-bridge
```
1. If you need to allow automation-bridge communication through a proxy, edit the file `/etc/opt/automation-bridge/automation-bridge.conf` and set the correct value. Below is an example:
- ```sh
- HTTP_PROXY="http://proxy.example.com:8080"
- HTTPS_PROXY="http://proxy.example.com:8080"
+ ```
+ HTTP_PROXY="http://proxy.example.com:8080\"
+ HTTPS_PROXY="http://proxy.example.com:8080\"
```
1. Restart the service with:
- ```sh
+ ```
systemctl restart automation-bridge
```
:::
### Configuring the automation bridge for high availability
-You may elect to deploy and register multiple bridges to your Cloud SOAR tenant for high availability. To cluster automation bridges together logically within Cloud SOAR and ensure high availability, you must set the same ALIAS for each bridge within the cluster in each respective `user-configuration.conf` file upon installation.
+You may elect to deploy and register multiple bridges to your tenant for high availability. To cluster automation bridges together logically within the Automation Service and ensure high availability, you must set the same ALIAS for each bridge within the cluster in each respective `user-configuration.conf` file upon installation.
When multiple bridges are registered with the same ALIAS, they will appear as active. If one or more bridges within the cluster go offline, playbooks will execute via the active nodes utilizing the same ALIAS. So long as there is parity between the nodes and there is at least one active node registered, there will be no disruption in playbook execution.
@@ -177,11 +177,11 @@ To check if the bridge is running correctly, run the following command:
ps faux |grep automation-bridge
```
-This is an example of running `automation-bridge`:
+This is an example of running `automation-bridge`:
+
+On the **Bridge** tab in the [Automation Service UI](/docs/platform-services/automation-service/about-automation-service/#automation-service-ui), a list of live bridge agents will be displayed along with their status.
-On the SOAR instance, a list of live bridge agents will be displayed along with their status:
-1. Click the gear icon
### Configuring the automation bridge for CyberArk
@@ -195,13 +195,13 @@ If you are using CyberArk, you must add the following certificates provided by C
#### Enable Podman socket
1. Run the following commands:
- ```bash
- systemctl enable podman.socket && systemctl start podman.socket
- ```
+ ```bash
+ systemctl enable podman.socket && systemctl start podman.socket
+ ```
1. Create a symbolic link:
- ```bash
- ln -s /run/podman/podman.sock /var/run/docker.sock
- ```
+ ```bash
+ ln -s /run/podman/podman.sock /var/run/docker.sock
+ ```
#### Change automation bridge configuration
@@ -219,7 +219,7 @@ ExecStop=/bin/kill -s TERM $MAINPID
Restart=on-failure
TimeoutStartSec=10
RestartSec=10
-
+##
NoNewPrivileges=yes
PrivateTmp=yes
PrivateDevices=yes
@@ -232,25 +232,25 @@ WantedBy=multi-user.target
This is the current solution and it needs to run service as `root`.
:::
-## Cloud SOAR automation bridge for Docker
+## Automation bridge for Docker
-This repository provides Docker images to run the Sumo Logic Cloud SOAR automation bridge. The images contain an automation bridge able to connect to the Sumo Logic SOAR environment.
+This repository provides Docker images to run the Sumo Logic automation bridge. The images contain an automation bridge able to connect to the Automation Service environment.
### Use the Docker automation bridge image
There are images tagged `latest` and for specific versions to run the automation bridge.
-When run, the automation bridge listens on the Docker Unix socket to be able to execute the Cloud SOAR integration or run a standalone daemon.
+When run, the automation bridge listens on the Docker Unix socket to be able to execute the integration or to run a standalone daemon.
-The Cloud SOAR automation bridge needs to be able to communicate with the Docker API to work.
+The automation bridge needs to be able to communicate with the Docker API to work.
### Prerequisites and configuration
-|Environment Variable |Description |Default |
-|:--|:--|:--|
-|`API_URL_HERE` |To determine which is the correct SOAR_URL, see [Sumo Logic Endpoints by Deployment and Firewall Security](/docs/api/getting-started/#sumo-logic-endpoints-by-deployment-and-firewall-security) and get the URL under the API Endpoint column. For example: `https://api.eu.sumologic.com/api/` | |
-|`SOAR_TOKEN_HERE`|Log in to Sumo Logic and create a new [installation token](/docs/manage/security/installation-tokens/) with the name prefix `csoar-bridge-token`. | |
-|`SIEM_URL_HERE` | The HTTP Sumo Logic collector to send the bridge logs. | NONE |
+|Environment Variable |Description |Default |
+|:------------------------------------|:---------------|:----------|
+|`API_URL_HERE` | To determine which is the correct SOAR_URL, see [Sumo Logic Endpoints by Deployment and Firewall Security](/docs/api/getting-started/#sumo-logic-endpoints-by-deployment-and-firewall-security) and get the URL under the API Endpoint column. For example: `https://api.eu.sumologic.com/api/` | |
+|`SOAR_TOKEN_HERE` | Log in to Sumo Logic and create a new [installation token](/docs/manage/security/installation-tokens/) with the name prefix `csoar-bridge-token`. | |
+|`SIEM_URL_HERE` | The HTTPS Source endpoint URL from a hosted Sumo Logic Collector. | NONE |
|`BRIDGE_ALIAS_HERE` | Provide the alias name. With bridge ALIAS, it is possible to distinguish which integration resources will be executed with this automation bridge. When a new integration resource is created or edited, it is possible to select the default ALIAS or to create a new one. So every automatic action configured to use this resource will be performed with the bridge that has the same ALIAS. | NONE |
### Methodologies
@@ -275,15 +275,15 @@ public.ecr.aws/u5z5f8z6/sumologic/csoar-automation-bridge:latest
In the DooD approach, you use the Docker daemon from the host system to interact with containers. Containers themselves do not have their own Docker runtime; they communicate with the host's Docker. This offers some distinct advantages, including simplicity in managing the containers and resource efficiency, as containers do not need to run their own Docker daemon.
-This way, the main container will have access to the Docker socket and can start containers. The only difference is that instead of starting “child” containers, it will start “sibling” containers.
+This way, the main container will have access to the Docker socket and will, therefore, be able to start containers. The only difference is that instead of starting “child” containers, it will start “sibling” containers.

-It's useful to share pulled images with all bridges running on the host machine.
+It's useful to share the pulled image with all bridges running on the host machine.
#### With privileged option
- ```bash
+```bash
docker run -d \
--privileged \
-e SOAR_URL=API_URL_HERE \
@@ -293,7 +293,7 @@ docker run -d \
-e DOCKER_TLS_CERTDIR=/certs \
-v docker-certs-ca:/certs/ca -v docker-certs-client:/certs/client \
public.ecr.aws/u5z5f8z6/sumologic/csoar-automation-bridge:latest
- ```
+```
Privileged containers are special containers with elevated privileges and direct access to the host system. Unlike their non-privileged counterparts, which are isolated and restricted in their capabilities, privileged containers can perform tasks requiring higher-level access. They achieve this by interacting with the host kernel and accessing sensitive resources, including hardware devices and network interfaces.
diff --git a/docs/contributing/style-guide.md b/docs/contributing/style-guide.md
index 2b18bea570..8040368600 100644
--- a/docs/contributing/style-guide.md
+++ b/docs/contributing/style-guide.md
@@ -1410,14 +1410,14 @@ See the following tabbed code examples:
@@ -19,17 +19,32 @@ The [RabbitMQ](https://www.rabbitmq.com/getstarted.html) app is a unified log ap
Following are the [Fields](/docs/manage/fields/) which will be created as part of RabbitMQ App install if not already present.
-* `messaging.cluster.name`. User configured. Specify the user-friendly cluster name which RabbitMQ belongs to.
-* `sumo.datasource`. Has fixed value of **rabbitmq**.
+* **`sumo.datasource`**. Fixed value of **rabbitmq**.
+* **`messaging.system`**. Fixed value of **rabbitmq**.
+* **`deployment.environment`**. This is a user-configured field set at the time of collector installation. It identifies the environment where the rabbitmq env resides, such as `dev`, `prod`, or `qa`.
+* **`messaging.cluster.name`**. User configured. Enter a name to uniquely identify your RabbitMQ cluster. This cluster name will be shown in the Sumo Logic dashboards.
+* **`messaging.node.name`**. Includes the value of the hostname of the machine which is being monitored.
## Prerequisites
+### For metrics collection
+
+:::note
+The RabbitMQ receiver supports RabbitMQ versions `3.8` and `3.9`.
+:::
+
+Enable the RabbitMQ management plugin by following the instructions in the [RabbitMQ documentation](https://www.rabbitmq.com/management.html#getting-started). Also, make sure you at least have the [monitoring](https://www.rabbitmq.com/management.html#permissions) level permissions to monitor the metrics.
+
+
+### For logs collection
+
This section provides instructions for configuring log collection for RabbitMQ running on a non-Kubernetes environment for the Sumo Logic App for RabbitMQ. By default, RabbitMQ logs are stored in a log file.
Follow the instructions to set up log collection:
-1. **Configure logging in RabbitMQ**. RabbitMQ supports logging via the following methods: local text log files, syslog and stdout. RabbitMQ logs have six levels of verbosity: debug, info, warning, error, critical, none. For details please visit this [page](https://www.rabbitmq.com/logging.html#log-levels). For the dashboards to work properly, log level needs to be set to **debug**. Default log level is **info**. All logging settings are located in [RabbitMQ.conf](https://www.rabbitmq.com/logging.html).
-2. **Configure RabbitMQ to write log lines to a local file**. By default, RabbitMQ logs are stored in `/var/log/rabbitmq/rabbit@
@@ -164,6 +192,8 @@ Here's a sample log message you'd find in Non-Kubernetes environments.
## Sample queries
+### Logs
+
This sample Query is from the **RabbitMQ - Logs dashboard** > **Events** by Severity panel.
```sql title="Query String"
@@ -173,10 +203,26 @@ This sample Query is from the **RabbitMQ - Logs dashboard** > **Events** by Seve
| parse "* * [*]" as date,time,severity | count by severity
```
+### Metrics
+
+This sample query is from the **Average Number of Consumers** panel in **RabbitMQ - Metrics** dashboard.
+
+```sql sumo.datasource=rabbitmq metric=rabbitmq.consumer.count deployment.environment=* messaging.cluster.name=* messaging.node.name=* rabbitmq.queue.name=* rabbitmq.vhost.name=*
+| avg by messaging.cluster.name
+| sum
+```
+
+
## Viewing RabbitMQ Dashboards
-### Overview
+### Logs
+
+The **RabbitMQ - Logs** dashboard gives you an at-a-glance view of error messages, error by severity, top and last 10 errors, broker, and Event Start/Add log messages.
+
+
+
+### Metrics
-The **RabbitMQ - Overview** dashboard gives you an at-a-glance view of Error messages, error by severity, top and last 10 errors, Broker and Event Start/Add log messages.
+The **RabbitMQ - Metrics** dashboard gives you an at-a-glance view of your RabbitMQ deployment across brokers, queue, exchange, consumer, and messages.
-
+
diff --git a/docs/integrations/containers-orchestration/rabbitmq.md b/docs/integrations/containers-orchestration/rabbitmq.md
index 80cfa7ba9e..a35468371d 100644
--- a/docs/integrations/containers-orchestration/rabbitmq.md
+++ b/docs/integrations/containers-orchestration/rabbitmq.md
@@ -463,7 +463,7 @@ This section demonstrates how to install the RabbitMQ App.
Version selection is not available for all apps.
:::
3. To install the app, complete the following fields.
- 1. **App Name.** You can retain the existing name, or enter a name of your choice for the app.
+ 1. **App Name.** You can retain the existing name, or enter a name of your choice for the app.
2. **Data Source.** Choose **Enter a Custom Data Filter**, and enter a custom RabbitMQ cluster filter. Examples:
1. For all RabbitMQ clusters: `messaging_cluster=*`
2. For a specific cluster: `messaging_cluster=rabbitmq.dev.01`
diff --git a/docs/integrations/databases/couchbase.md b/docs/integrations/databases/couchbase.md
index 9db4720cd3..fe4a125cb5 100644
--- a/docs/integrations/databases/couchbase.md
+++ b/docs/integrations/databases/couchbase.md
@@ -200,8 +200,8 @@ This section explains the steps to collect Couchbase logs from a Kubernetes envi
5. Sumo Logic Kubernetes collection will automatically start collecting logs from the pods having the annotations defined above.
6. Verify logs in Sumo Logic.
3. **Add a FER to normalize the fields in Kubernetes environments**. This step is not needed if using application components solution terraform script. Labels created in Kubernetes environments automatically are prefixed with pod_labels. To normalize these for our app to work, we need to create a Field Extraction Rule if not already created for Proxy Application Components. To do so:
- 1. Go to Manage Data > Logs > Field Extraction Rules.
- 2. Click the + Add button on the top right of the table.
+ 1. In the main Sumo Logic menu, select **Manage Data > Logs > Field Extraction Rules**.
+ 2. Click the **+ Add Rule** button on the top right of the table.
3. The **Add Field Extraction Rule** form will appear:
4. Enter the following options:
* **Rule Name**. Enter the name as **App Observability - Proxy**.
@@ -401,7 +401,7 @@ There are limits to how many alerts can be enabled - see the [Alerts FAQ](/docs/
1. For alerts applicable only to a specific cluster, your custom filter would be `'db_cluster=couchbase-standalone.01'`.
2. For alerts applicable to all cluster that start with couchbase-standalone, your custom filter would be,`db_cluster=couchbase-standalone*`.
3. For alerts applicable to a specific cluster within a production environment, your custom filter would be `db_cluster=couchbase-1` and `environment=standalone` (This assumes you have set the optional environment tag while configuring collection).
-3. Go to Manage Data > Alerts > Monitors.
+3. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**.
4. Click **Add**:
5. Click **Import** and then copy-paste the above JSON to import monitors.
6. The monitors are disabled by default. Once you have installed the alerts using this method, navigate to the Couchbase folder under **Monitors** to configure them. See [Monitor Settings](/docs/alerts/monitors/settings) to learn how to enable monitors to send notifications to teams or connections. See the instructions detailed in [Create a Monitor](/docs/alerts/monitors/create-monitor).
@@ -485,7 +485,7 @@ Locate and install the app you need from the **App Catalog**. If you want to see
Version selection is not available for all apps.
:::
3. To install the app, complete the following fields.
- 1. **App Name.** You can retain the existing name, or enter a name of your choice for the app.
+ 1. **App Name.** You can retain the existing name, or enter a name of your choice for the app.
2. **Data Source.**
* Choose **Enter a Custom Data Filter**, and enter a custom Couchbase cluster filter. Examples:
1. For all Couchbase clusters `db_cluster=*`
diff --git a/docs/integrations/databases/mariadb.md b/docs/integrations/databases/mariadb.md
index 48c06d4cb7..efad874a5f 100644
--- a/docs/integrations/databases/mariadb.md
+++ b/docs/integrations/databases/mariadb.md
@@ -448,7 +448,7 @@ Sumo Logic has provided out-of-the-box alerts available through [Sumo Logic moni
* For alerts applicable only to a specific cluster, your custom filter would be `db_cluster=mariadb-prod.01`.
* For alerts applicable to all clusters that start with Kafka-prod, your custom filter would be `db_cluster=mariadb-prod*`.
* For alerts applicable to a specific cluster within a production environment, your custom filter would be `db_cluster=mariadb-1` and `environment=prod`. This assumes you have set the optional environment tag while configuring collection.
-3. Go to Manage Data > Alerts > Monitors.
+3. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**.
4. Click **Add**.
5. Click Import and then copy-paste the above JSON to import monitors.
6. The monitors are disabled by default. Once you have installed the alerts using this method, navigate to the MariaDB folder under **Monitors** to configure them. See [this](/docs/alerts/monitors) document to enable monitors to send notifications to teams or connections. See the instructions detailed in [Add a Monitor](/docs/alerts/monitors/create-monitor).
@@ -526,7 +526,7 @@ Locate and install the app you need from the **App Catalog**. If you want to see
Version selection is not available for all apps.
:::
3. To install the app, complete the following fields.
- 1. **App Name.** You can retain the existing name, or enter a name of your choice for the app.
+ 1. **App Name.** You can retain the existing name, or enter a name of your choice for the app.
2. **Data Source.**
* Choose **Enter a Custom Data Filter**, and enter a custom MariaDB cluster filter. Examples;
1. For all MariaDB clusters, `db_cluster=*`.
diff --git a/docs/integrations/databases/memcached.md b/docs/integrations/databases/memcached.md
index 9b51f5c9f9..576f5f3218 100644
--- a/docs/integrations/databases/memcached.md
+++ b/docs/integrations/databases/memcached.md
@@ -218,7 +218,7 @@ This section explains the steps to collect Memcached logs from a Kubernetes envi
```
4. Sumo Logic Kubernetes collection will automatically start collecting logs from the pods having the annotations defined above.
3. **Add a FER to normalize the fields in Kubernetes environments**. This step is not needed if one is using application components solution terraform script. Labels created in Kubernetes environments automatically are prefixed with pod_labels. To normalize these for our app to work, we need to create a Field Extraction Rule if not already created for Proxy Application Components. To do so:
- 1. Go to **Manage Data > Logs > Field Extraction Rules**.
+ 1. In the main Sumo Logic menu, select **Manage Data > Logs > Field Extraction Rules**.
2. Click the + Add button on the top right of the table.
3. The **Add Field Extraction Rule** form will appear:
4. Enter the following options:
@@ -372,7 +372,7 @@ There are limits to how many alerts can be enabled. For more information, see [M
* For alerts applicable only to a specific cluster, your custom filter would be: `db_cluster=dev-memcached-01`
* For alerts applicable to all clusters that start with `memcached-prod`, your custom filter would be: `db_cluster=memcachedt-prod*`
* For alerts applicable to specific clusters within a production environment, your custom filter would be: `db_cluster=dev-memcached-01` AND `environment=prod`. This assumes you have set the optional environment tag while configuring collection.
-3. Go to **Manage Data > Alerts > Monitors**.
+3. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**.
4. Click **Add**.
4. Click **Import**.
6. On the **Import Content popup**, enter **Memcached** in the Name field, paste the JSON into the popup, and click **Import**.
diff --git a/docs/integrations/databases/mongodb.md b/docs/integrations/databases/mongodb.md
index ca047d0541..d742891716 100644
--- a/docs/integrations/databases/mongodb.md
+++ b/docs/integrations/databases/mongodb.md
@@ -235,7 +235,7 @@ Pivoting to Tracing data from Entity Inspector is possible only for “MongoDB a
```
5. Sumo Logic Kubernetes collection will automatically start collecting logs from the pods having the annotations defined above.
3. **Add an FER to normalize the fields in Kubernetes environments**. This step is not needed if one is using application components solution terraform script. Labels created in Kubernetes environments automatically are prefixed with `pod_labels`. To normalize these for our app to work, we need to create a Field Extraction Rule if not already created for Database Application Components. To do so:
- 1. Go to **Manage Data > Logs > Field Extraction Rules**.
+ 1. In the main Sumo Logic menu, select **Manage Data > Logs > Field Extraction Rules**.
2. Click the + Add button on the top right of the table.
3. The **Add Field Extraction Rule** form will appear:
4. Enter the following options:
@@ -427,7 +427,7 @@ There are limits to how many alerts can be enabled. For more information, see [M
1. Download the [JSON file](https://github.com/SumoLogic/terraform-sumologic-sumo-logic-monitor/blob/main/monitor_packages/MongoDB/MongoDB.json) that describes the monitors.
2. Replace `$$mongodb_data_source` with a custom source filter. To configure alerts for a specific database cluster, use a filter like `db_system=mongodb` or `db_cluster=dev-mongodb`. To configure the alerts for all of your clusters, set `$$mongodb_data_source` to blank (`""`).
-3. Go to **Manage Data > Alerts > Monitors**.
+3. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**.
4. Click **Add**.
5. Click **Import**.
6. On the **Import Content popup**, enter `MongoDB` in the Name field, paste in the JSON into the the popup, and click **Import**.
diff --git a/docs/integrations/databases/mysql.md b/docs/integrations/databases/mysql.md
index cdd76ee6c1..7b6cecf94d 100644
--- a/docs/integrations/databases/mysql.md
+++ b/docs/integrations/databases/mysql.md
@@ -346,7 +346,7 @@ Sumo Logic Kubernetes collection will automatically start collecting logs from t
2. **Add an FER to normalize the fields in Kubernetes environments**. This step is not needed if using application components solution terraform script. Labels created in Kubernetes environments are automatically prefixed with pod_labels. To normalize these for our app to work, we'll create a [Field Extraction Rule](/docs/manage/field-extractions/create-field-extraction-rule), Database Application Components, assuming it does not already exist:
- 1. Go to **Manage Data > Logs > Field Extraction Rules**.
+ 1. In the main Sumo Logic menu, select **Manage Data > Logs > Field Extraction Rules**.
2. Click the **+ Add**.
3. The **Add Field Extraction** pane appears.
4. **Rule Name.** Enter "App Observability - Database".
@@ -574,7 +574,7 @@ There are limits to how many alerts can be enabled. For more information, see [M
1. Download the [JSON file](https://github.com/SumoLogic/terraform-sumologic-sumo-logic-monitor/blob/main/monitor_packages/mysql/mysql.json) that describes the monitors.
2. Replace `$$mysql_data_source` with a custom source filter. To configure alerts for a specific database cluster, use a filter like `db_system=mysql` or `db_cluster=dev-mysql`. To configure the alerts for all of your clusters, set `$$mysql_data_source` to blank (`""`).
-3. Go to **Manage Data > Alerts > Monitors**.
+3. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**.
4. Click **Add**.
5. Click **Import.**
6. On the **Import Content popup**, enter "MySQL" in the Name field, paste in the JSON into the the popup, and click **Import**.
diff --git a/docs/integrations/databases/opentelemetry/cassandra-opentelemetry.md b/docs/integrations/databases/opentelemetry/cassandra-opentelemetry.md
index bad7a0d63e..3fcb226a94 100644
--- a/docs/integrations/databases/opentelemetry/cassandra-opentelemetry.md
+++ b/docs/integrations/databases/opentelemetry/cassandra-opentelemetry.md
@@ -11,9 +11,11 @@ import TabItem from '@theme/TabItem';
@@ -21,13 +23,27 @@ The app supports Logs from the open-source version of Cassandra. The App is test
Following are the [Fields](/docs/manage/fields/) which will be created as part of Cassandra App install if not already present:
+- `deployment.environment`. User configured. Through this Cassandra cluster is identified by the environment where it resides. For example: dev, prod, or qa.
- `db.cluster.name`. User configured. Enter a name to identify this Cassandra cluster. This cluster name will be shown in the Sumo Logic dashboards.
- `db.system`. Has fixed value of **cassandra**.
-- `deployment.environment`. User configured. Through this Cassandra cluster is identified by the environment where it resides. For example: dev, prod or qa.
+- `db.node.name`. Holds the value of the Fully Qualified Domain Name (FQDN) of the machine from which the OpenTelemetry collector is collecting logs and metrics.
- `sumo.datasource`. Has fixed value of **cassandra**.
## Prerequisites
+#### For metric collection
+
+JMX receiver collects Cassandra metrics from Cassandra server as part of the OpenTelemetry Collector (OTC).
+
+ 1. Follow the instructions in [JMX - OpenTelemetry's prerequisites section](/docs/integrations/app-development/opentelemetry/jmx-opentelemetry/#prerequisites) to download the [JMX Metric Gatherer](https://github.com/open-telemetry/opentelemetry-java-contrib/blob/main/jmx-metrics/README.md). This gatherer is used by the [JMX Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/jmxreceiver#details).
+
+ 2. Set the JMX port as part of `JAVA_OPTS` for Tomcat startup. Usually, it is set in the `/etc/systemd/system/cassandra.service` or `C:\Program Files\apache-tomcat\bin\tomcat.bat` file.
+
+ ```json
+ JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=11099 -Dcom.sun.management.jmxremote.authenticate=true -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.password.file=${CASSANDRA_CONF_DIR}/jmx.password -Dcom.sun.management.jmxremote.access.file=${CASSANDRA_CONF_DIR}/jmx.access"
+ ```
+
+#### For log collection
Cassandra has three main logs: system.log, debug.log, and gc.log which hold general logging messages, debugging logging messages, and java garbage collection logs respectively.
These logs by default live in `${CASSANDRA_HOME}/logs`, but most Linux distributions relocate logs to `/var/log/cassandra`. Operators can tune this location as well as what levels are logged using the provided logback.xml file. For more details on Cassandra logs, see[ this](https://cassandra.apache.org/doc/latest/troubleshooting/reading_logs.html) link.
@@ -56,6 +72,7 @@ In this step, you will configure the yaml required for Cassandra Collection. Pat
Below are the inputs required:
- The path to system.log is required here. This file is typically located in `/var/log/cassandra`. If you're using a customized path, check the respective conf file for this information.
+- For metrics, you're required to provide the JMX endpoint (default is `localhost:7199`) along with the `collection_interval` (default is 1 minute).
You can add any custom fields which you want to be tagged with the data ingested in Sumo. Click on the **Download YAML File** button to get the yaml file.
@@ -122,7 +139,44 @@ import LogsOutro from '../../../reuse/apps/opentelemetry/send-logs-outro.md';
INFO [ScheduledTasks:1] 2023-01-08 09:18:47,347 StatusLogger.java:101 - system.schema_aggregates
```
-## Sample queries
+## Sample metrics message
+
+```json
+{
+ "queryId": "A",
+ "_source": "cassandra-otel",
+ "_metricId": "dasIFS6RvCVxEcsljWGpnQ",
+ "_sourceName": "Http Input",
+ "host.id": "i-071ade75d03650657",
+ "host.group": "cassandraHostGrp",
+ "telemetry.sdk.version": "1.38.0",
+ "os.type": "linux",
+ "sumo.datasource": "cassandra",
+ "db.system": "cassandra",
+ "db.node.name": "ip-54-163-607-30.ec2.internal",
+ "_sourceCategory": "Labs/cassandra-otel",
+ "deployment.environment": "dev",
+ "_contentType": "Carbon2",
+ "host.name": "ip-54-163-607-30.ec2.internal",
+ "metric": "cassandra.client.request.write.latency.50p",
+ "_collectorId": "000000000FB3B451",
+ "_sourceId": "000000005A60F624",
+ "unit": "us",
+ "db.cluster.name": "cassandra_cluster",
+ "telemetry.sdk.language": "java",
+ "telemetry.sdk.name": "opentelemetry",
+ "service.name": "unknown_service:java",
+ "_collector": "Labs - cassandra-otel",
+ "max": 229,
+ "min": 0,
+ "avg": 131.25,
+ "sum": 525,
+ "latest": 67,
+ "count": 4
+}
+```
+
+## Sample log queries
Following is the query from Cassandra App's overview Dashboard's Nodes Up Panel:
@@ -136,7 +190,14 @@ Following is the query from Cassandra App's overview Dashboard's Nodes Up Panel:
| sort by _timeslice asc
```
-## Viewing Cassandra Dashboards
+## Sample metrics query
+Following is the query from Cassandra App's overview Dashboard's Number of Requests Panel:
+
+```sql
+sumo.datasource=cassandra deployment.environment=* db.cluster.name=* db.node.name=* metric=cassandra.client.request.count | sum
+```
+
+## Viewing Cassandra dashboards
### Overview
@@ -148,7 +209,7 @@ Use this dashboard to:
- Gain insights into Memory - Init, used, Max and committed
- Gain insights into the error and warning logs by thread and Node activity
-
+
### Cache Stats
@@ -159,7 +220,7 @@ Use this dashboard to:
- Monitor Cache performance.
- Identify Cache usage statistics.
-
+
### Errors and Warnings
@@ -170,7 +231,7 @@ Use this dashboard to:
- Review errors and warnings generated by the server.
- Review the Threads errors and warning events.
-
+
### Gossip
@@ -181,7 +242,7 @@ Use this dashboard to:
- Determine nodes with errors resulting in failures.
- Review the node activity and pending tasks.
-
+
### Memtable
@@ -191,7 +252,7 @@ Use this dashboard to:
- Review flush activity and memtable status.
-
+
### Resource Usage
@@ -201,4 +262,20 @@ Use this dashboard to:
- Identify resource utilization. This can help you to determine whether resources are over-allocated or under-allocated.
-
+
+
+### Compaction
+
+The **Cassandra - Compactions** dashboard provides insight into the completed and pending compaction tasks.
+
+
+### Requests
+
+The **Cassandra - Requests** dashboard provides insight into the number of request served, number of error request, and their distribution by status and operation. Also you can monitor the read and write latency of the cluster instance using this dashboard.
+
+
+### Storage
+
+The **Cassandra - Storage** dashboard provides insight into the current value of total hints of your Cassandra cluster along with storage managed by the cluster.
+
+
\ No newline at end of file
diff --git a/docs/integrations/databases/redis.md b/docs/integrations/databases/redis.md
index 3fa28f8c3d..997c42bc67 100644
--- a/docs/integrations/databases/redis.md
+++ b/docs/integrations/databases/redis.md
@@ -454,9 +454,9 @@ There are limits for how many alerts can be enabled - please see the [Alerts FAQ
* For alerts applicable only to a specific cluster, your custom filter would be: `db_cluster=redis-.prod.01`.
* For alerts applicable to all clusters that start with `redis-prod`, your custom filter would be: `db_cluster=redis-prod*`.
* For alerts applicable to a specific cluster within a production environment, your custom filter would be: `db_cluster=redis-1 and environment=prod`. This assumes you have set the optional environment tag while configuring collection.
-2. Go to Manage Data > Alerts > Monitors.
+2. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**.
3. Click **Add**.
-4. Click Import to import monitors from the JSON above.
+4. Click **Import** to import monitors from the JSON above.
:::note
Monitors are disabled by default. Once you have installed the alerts via this method, navigate to the Redis folder under **Monitors** to configure them. See [Monitor Settings](/docs/alerts/monitors/settings/#edit-disable-more-actions) to enable monitors. To send notifications to teams or connections, see the instructions detailed in Step 4 of [Create a Monitor](/docs/alerts/monitors/create-monitor).
@@ -539,8 +539,8 @@ This section demonstrates how to install the Redis ULM app.
Version selection is not available for all apps.
:::
3. To install the app, complete the following fields.
- 1. **App Name.** You can retain the existing name, or enter a name of your choice for the app.
- 2. **Data Source.**
Choose **Enter a Custom Data Filter** and enter a custom Redis cluster filter. Examples:
+ 1. **App Name.** You can retain the existing name, or enter a name of your choice for the app.
+ 2. **Data Source.** Choose **Enter a Custom Data Filter** and enter a custom Redis cluster filter. Examples:
* For all Redis clusters: `db_cluster=*`
* For a specific cluster: `db_cluster=redis.dev.01`
* Clusters within a specific environment: `db_cluster=redis-1 and environment=prod`. (This assumes you have set the optional environment tag while configuring collection).
diff --git a/docs/integrations/hosts-operating-systems/host-process-metrics.md b/docs/integrations/hosts-operating-systems/host-process-metrics.md
index c50b85687a..ec7e40245c 100644
--- a/docs/integrations/hosts-operating-systems/host-process-metrics.md
+++ b/docs/integrations/hosts-operating-systems/host-process-metrics.md
@@ -190,9 +190,9 @@ There are limits to how many alerts can be enabled - please see the [Alerts FAQ]
* For alerts applicable only to a specific cluster of hosts, your custom filter could be: `'_sourceCategory=yourclustername/metrics'`.
* For alerts applicable to all hosts that start with ec2hosts-prod, your custom filter could be: `'_sourceCategory=ec2hosts-prod*/metrics'`.
* For alerts applicable to a specific cluster within a production environment, your custom filter could be: `'_sourceCategory=prod/yourclustername/metrics'`
-2. Go to Manage Data > Alerts > Monitors.
-3. Click Add.
-4. Click Import to import monitors from the JSON above.
+2. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**.
+3. Click **Add**.
+4. Click **Import** to import monitors from the JSON above.
The monitors are disabled by default. Once you have installed the alerts using this method, navigate to the Host and Process Metrics folder under Monitors to configure them. See [this](/docs/alerts/monitors/settings) document to enable monitors, to configure each monitor, to send notifications to teams or connections, see the instructions detailed in [Create a Monitor](/docs/alerts/monitors/create-monitor).
diff --git a/docs/integrations/microsoft-azure/sql-server.md b/docs/integrations/microsoft-azure/sql-server.md
index 0c14a56f00..da6f134e8c 100644
--- a/docs/integrations/microsoft-azure/sql-server.md
+++ b/docs/integrations/microsoft-azure/sql-server.md
@@ -227,8 +227,8 @@ kubectl describe pod List of vendors and products A-L that Sumo Logic integrates with.
+List of vendors and products M-Z that Sumo Logic integrates with.
+
| [LogPoint](https://www.logpoint.com/en/) | Automation integration: [LogPoint](/docs/platform-services/automation-service/app-central/integrations/logpoint/) |
|
| [LogRhythm](https://logrhythm.com/) | Automation integration: [LogRhythm](/docs/platform-services/automation-service/app-central/integrations/logrhythm/) |
|
| [Lucidum](https://lucidum.io/) | Partner integration: [Lucidum](https://github.com/SumoLogic/sumologic-public-partner-apps/tree/master/Lucidum) |
-
-## M
-
-| Logo | Vendors and Products | Integrations |
-| :-- | :-- | :-- |
-|
| [Mailgun](https://www.mailgun.com/) | Webhook: [Mailgun](/docs/integrations/webhooks/mailgun/) |
-|
| [Malwarebytes](https://www.malwarebytes.com/) | Automation integration: [Malwarebytes Nebula](/docs/platform-services/automation-service/app-central/integrations/malwarebytes-nebula/)
| [ManageEngine](https://www.manageengine.com/) | Automation integration: [ManageEngine Desktop Central](/docs/platform-services/automation-service/app-central/integrations/manage-engine-desktop-central/)
| [MariaDB](https://mariadb.org/) | Apps:
| [Material Security](https://material.security/) | Automation integration: [Material Security](/docs/platform-services/automation-service/app-central/integrations/material-security/) |
-|
| [Mattermost](https://mattermost.com/) | Automation integration: [Mattermost](/docs/platform-services/automation-service/app-central/integrations/mattermost/) |
-|
| [MaxMind](https://www.maxmind.com/en/home) | Automation integration: [MaxMind V2](/docs/platform-services/automation-service/app-central/integrations/maxmind-v2/) |
-|
| [McAfee](https://www.mcafee.com/) | Automation integrations:
| [Memcached](https://memcached.org/) | Apps:
| [Microsoft](https://www.microsoft.com/) | Apps:
| [Mimecast](https://www.mimecast.com/) | App: [Mimecast](/docs/integrations/saas-cloud/mimecast/)
| [Miro](https://miro.com/) | App: [Miro](/docs/integrations/saas-cloud/miro/)
| [MISP](https://www.misp-project.org/) | Automation integration: [MISP](/docs/platform-services/automation-service/app-central/integrations/misp/)
| [MITRE ATT&CK](https://attack.mitre.org/) | Automation integration: [Mitre Matrix](/docs/platform-services/automation-service/app-central/integrations/mitre-matrix/) |
-|
| [MongoDB](https://www.mongodb.com/) | Apps:
| [MongoDB Atlas](https://www.mongodb.com/atlas) | App: [MongoDB Atlas](/docs/integrations/databases/mongodb-atlas/) |
-|
| [mParticle](https://www.mparticle.com/) | Webhook: [mParticle](/docs/integrations/webhooks/mparticle/) |
-|
| [MxToolbox](https://mxtoolbox.com/) | Automation integration: [MxToolbox](/docs/platform-services/automation-service/app-central/integrations/mxtoolbox/) |
-|
| [MySQL](https://www.mysql.com/) | Apps:
| [Netlify](https://www.netlify.com/) | Webhook: [Netlify](/docs/integrations/webhooks/netlify/) |
-|
| [NETSCOUT](https://www.netscout.com/) | Automation integration: [Arbor (NETSCOUT)](/docs/platform-services/automation-service/app-central/integrations/arbor/) |
-|
| [Netskope](https://www.netskope.com/) | Apps:
| [Neustar](https://www.home.neustar/) | Automation integration: [Neustar IP GeoPoint](/docs/platform-services/automation-service/app-central/integrations/neustar-ip-geopoint/) |
-|
| [New Relic](https://newrelic.com/) | Webhook: [Webhook Connection for New Relic](/docs/alerts/webhook-connections/new-relic/) |
-|
| [Nmap](https://nmap.org/) | Automation integration: [Nmap](/docs/platform-services/automation-service/app-central/integrations/nmap/) |
-|
| [Nobl9](https://www.nobl9.com/) | Webhook: [Nobl9](/docs/integrations/webhooks/nobl9/) |
-|
| [Nozomi Networks](https://www.nozominetworks.com/) | Automation integration: [Nozomi Networks](/docs/platform-services/automation-service/app-central/integrations/nozomi-networks/) |
-|
| [Nucleon](https://nucleoncyber.com/) | Automation integration: [Nucleon Cyber](/docs/platform-services/automation-service/app-central/integrations/nucleon-cyber/)
| [NXLog](https://nxlog.co/) | Partner integration: [NXLog](https://nxlog.co/technology-ecosystem) |
-
-## O
-
-| Logo | Vendors and Products | Integrations |
-| :-- | :-- | :-- |
-|
| [Observable Networks](https://www.cisco.com/c/en/us/services/acquisitions/observable-networks.html) | App: [Observable Networks](/docs/integrations/security-threat-detection/observable-networks/) |
-|
| [OISF](https://oisf.net/) | Cloud SIEM integration: [OISF](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/9c138edd-dc14-43a6-b751-52e41a8bd105.md) |
-|
| [Okta](https://www.okta.com/) | App: [Okta](/docs/integrations/saml/okta/)
| [OneLogin](https://www.onelogin.com/) | App: [OneLogin](/docs/integrations/saml/onelogin/)
| [1Password](https://1password.com/) | App: [1Password](/docs/integrations/1password/)
| [OneTrust](https://www.onetrust.com/) | Automation integration: [OneTrust](/docs/platform-services/automation-service/app-central/integrations/onetrust/) |
-|
| [OpenAI](https://openai.com/) | Automation integration: [OpenAI ChatGPT](/docs/platform-services/automation-service/app-central/integrations/openai-chatgpt/) |
-|
| [OpenLDAP](https://www.openldap.org/) | Automation integration: [OpenLDAP](/docs/platform-services/automation-service/app-central/integrations/openldap/) |
-|
| [OpenSSH](https://www.openssh.com/) | Cloud SIEM integration: [OpenSSH](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/d0bf0b9f-162e-4d1e-9b89-38e8d526a434.md) |
-|
| [OpenText](https://www.opentext.com/) | Automation integrations:
| [OpenVPN](https://openvpn.net/) | Cloud SIEM integration: [OpenVPN](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/8e5a85b3-a95e-47d9-adcf-bb543e6580c0.md) |
-|
| [Opsgenie](https://www.atlassian.com/software/opsgenie) | App: [Opsgenie](/docs/integrations/saas-cloud/opsgenie/)
| [OpsRamp](https://www.opsramp.com/) | Partner integration: [OpsRamp](https://docs.opsramp.com/integrations/a2r/3rd-party/sumologic/) |
-|
| [Opswat](https://www.opswat.com/) | Automation integration: [Opswat Metadefender](/docs/platform-services/automation-service/app-central/integrations/opswat-metadefender/) |
-|
| [Oracle Database](https://www.oracle.com/database/) | Apps:
| [Orca Security](https://orca.security/) | Cloud SIEM integration: [Orca Security](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/ab5b4909-20f7-4cf7-b8de-24f4a5b2ba57.md) |
-|
| [osquery](https://osquery.io/) | Cloud SIEM integration: [Osquery](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/eca511e4-0daa-41f7-919e-ec4d0ac1558f.md)
| [Ossec](https://www.ossec.net/) | Cloud SIEM integration: [Ossec](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/1eceb40f-85d7-45ea-b341-864a38ea0775.md) |
-
-## P
-
-| Logo | Vendors and Products | Integrations |
-| :-- | :-- | :-- |
-|
| [PagerDuty](https://www.pagerduty.com/) | Apps:
| [Palo Alto Networks](https://www.paloaltonetworks.com/) | Apps:
| [PaperTrail](https://www.papertrail.com/) | Webhook: [PaperTrail](/docs/integrations/webhooks/papertrail/) |
-|
| [Phantombuster](https://phantombuster.com/) | Automation integration: [Phantombuster](/docs/platform-services/automation-service/app-central/integrations/phantombuster/) |
-|
| [PhishTank](https://phishtank.org/) | Automation integration: [PhishTank](/docs/platform-services/automation-service/app-central/integrations/phishtank/) |
-|
| [PostgreSQL](https://www.postgresql.org/) | Apps:
| [Postman](https://www.postman.com/) | Webhook: [Postman](/docs/integrations/webhooks/postman/) |
-|
| [Pritunl](https://pritunl.com/) | Cloud SIEM integration: [Pritunl](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/598b6820-feff-4169-89da-77211493a91d.md) |
-|
| [Prometheus](https://prometheus.io/) | Collector: [Collect Prometheus Metrics](/docs/send-data/collect-from-other-data-sources/collect-prometheus-metrics/) |
-|
| [Proofpoint](https://www.proofpoint.com/us) | Apps:
| [ProtectOnce](https://protectonce.com/) | Automation integration: [ProtectOnce](/docs/platform-services/automation-service/app-central/integrations/protectonce/) |
-|
| [Pulsedive](https://pulsedive.com/) | Automation integration: [Pulsedive](/docs/platform-services/automation-service/app-central/integrations/pulsedive/) |
-|
| [Puppet](https://www.puppet.com/) | Apps:
| [Pusher](https://pusher.com/) | Webhook: [Pusher](/docs/integrations/webhooks/pusher/) |
-
-## Q
-
-| Logo | Vendors and Products | Integrations |
-| :-- | :-- | :-- |
-|
| [RabbitMQ](https://www.rabbitmq.com/) | Apps:
| [Rapid7](https://www.rapid7.com/) | App: [Rapid7](/docs/integrations/saas-cloud/rapid7/)
| [RapidAPI](https://rapidapi.com/) | Automation integration: [RapidAPI](/docs/platform-services/automation-service/app-central/integrations/rapidapi/) |
-|
| [Recorded Future](https://www.recordedfuture.com/) | Automation integration: [Recorded Future](/docs/platform-services/automation-service/app-central/integrations/recorded-future/) |
-|
| [Red Hat OpenShift](https://www.redhat.com/en/technologies/cloud-computing/openshift) | Partner integration: [Red Hat OpenShift](https://docs.openshift.com/acs/3.74/integration/integrate-with-sumologic.html)
| [Redis](https://redis.io/) | Apps:
| [RiskIQ](https://community.riskiq.com/) | Automation integration: [Passive Total](/docs/platform-services/automation-service/app-central/integrations/passive-total/) |
-|
| [Rollbar](https://rollbar.com/) | Webhook: [Rollbar](/docs/integrations/webhooks/rollbar/) |
-|
| [RSA](https://www.rsa.com/) | Automation integrations:
| [rsyslog](https://www.rsyslog.com/) | Collector: [rsyslog](/docs/send-data/hosted-collectors/cloud-syslog-source/rsyslog/) |
-|
| [Ruby on Rails](https://rubyonrails.org/) | Collector: [Collect Ruby on Rails Logs](/docs/send-data/collect-from-other-data-sources/collect-ruby-on-rails-logs/) |
-
-
-## S
-
-| Logo | Vendors and Products | Integrations |
-| :-- | :-- | :-- |
-|
| [Sauce Labs](https://saucelabs.com/) | Partner integration: [Sauce Labs](https://docs.saucelabs.com/basics/integrations/sumo/) |
-|
| [Screenshot Machine](https://www.screenshotmachine.com/) | Automation integration: [Screenshot Machine](/docs/platform-services/automation-service/app-central/integrations/screenshot-machine/) |
-|
| [SecureAuth](https://www.secureauth.com/) | Cloud SIEM integration: [SecureAuth](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/72744d1c-ddff-4ead-b76e-60430704f945.md) |
-|
| [Security Scorecard](https://securityscorecard.com/) | Automation integration: [Security Scorecard](/docs/platform-services/automation-service/app-central/integrations/security-scorecard/) |
-|
| [SecurityTrails](https://securitytrails.com/) | Automation integration: [SecurityTrails](/docs/platform-services/automation-service/app-central/integrations/securitytrails/) |
-|
| [Securonix](https://www.securonix.com/) | Automation integrations:
| [SendGrid](https://sendgrid.com/) | Webhook: [SendGrid](/docs/integrations/webhooks/sendgrid/) |
-|
| [Sensu](https://sensu.io/) | Partner integration: [Send data to Sumo Logic with Sensu](https://docs.sensu.io/sensu-go/latest/observability-pipeline/observe-process/send-data-sumo-logic/) |
-|
| [SIGNL4](https://www.signl4.com/) | Webhooks:
| [Sentry](https://sentry.io/welcome/) | Webhook: [Sentry](/docs/integrations/webhooks/sentry/) |
-|
| [ServiceNow](https://www.servicenow.com/) | Automation integration: [ServiceNow V2](/docs/platform-services/automation-service/app-central/integrations/servicenow-v2/)
| [Shodan](https://www.shodan.io/) | Automation integration: [Shodan](/docs/platform-services/automation-service/app-central/integrations/shodan/) |
-|
| [Silent Push](https://www.silentpush.com/) | Automation integration: [Silent Push](/docs/platform-services/automation-service/app-central/integrations/silent-push) |
-|
| [Slack](https://slack.com/) | App: [Slack](/docs/integrations/saas-cloud/slack/)
| [Snare](https://www.snaresolutions.com/) | Cloud SIEM integration: [Intersect Alliance](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/005c835d-f067-4147-9da9-fe4d2691247e.md) |
-|
| [Snowflake](https://www.snowflake.com/en/) | Cloud SIEM integration: [Snowflake](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/5541f59d-e27d-48e6-a35c-34fb75e9cf13.md) |
-|
| [Snyk](https://snyk.io/) | Automation integration: [Snyk](/docs/platform-services/automation-service/app-central/integrations/snyk/) |
-|
| [SOCRadar](https://socradar.io/) | Automation integration: [SOCRadar](/docs/platform-services/automation-service/app-central/integrations/socradar/) |
-|
| [SonicWall](https://www.sonicwall.com/) | Automation integration: [SonicWall](/docs/platform-services/automation-service/app-central/integrations/sonicwall/) |
-|
| [Sophos](https://www.sophos.com/en-us) | Automation integrations:
| [SpiderFoot HX](https://login.hx.spiderfoot.net/) | Automation integration: [SpiderFoot HX](/docs/platform-services/automation-service/app-central/integrations/spiderfoot-hx/) |
-|
| [Spinnaker](https://spinnaker.io/) | Partner integration: [Spinnaker](https://docs.armory.io/continuous-deployment/armory-admin/observe/integrations-sumologic/) |
-|
| [Split](https://www.split.io/) | Webhook: [Split](/docs/integrations/webhooks/split/) |
-|
| [Splunk](https://www.splunk.com/) | Automation integration: [Splunk](/docs/platform-services/automation-service/app-central/integrations/splunk/)
| [Squadcast](https://www.squadcast.com/) | Webhook: [Squadcast](/docs/integrations/webhooks/squadcast/) |
-|
| [Squid Cache](http://www.squid-cache.org/) | Apps:
| [StackRox](https://www.stackrox.io/) | Collector: [StackRox](https://cdn.stackrox.io/integrations/sumologic-stackrox-app.pdf)
| [StatsD](https://www.datadoghq.com/blog/statsd/) | Collector: [Collect StatsD Metrics](/docs/send-data/collect-from-other-data-sources/collect-statsd-metrics/) |
-|
| [Stellar Cyber](https://stellarcyber.ai/) | [Stellar Cyber Starlight](/docs/platform-services/automation-service/app-central/integrations/stellar-cyber-starlight/) |
-|
| [Strimzi](https://strimzi.io/) | App: [Strimzi Kafka](/docs/integrations/containers-orchestration/strimzi-kafka/) |
-|
| [Stripe](https://stripe.com/) | Webhook: [Stripe](/docs/integrations/webhooks/stripe/) |
-|
| [Sucuri](https://sucuri.net/) | Cloud SIEM integration: [Sucuri](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/cdfd2ba0-77eb-4e11-b071-6f4d01fda607.md) |
-|
| [Sumo Logic](https://www.sumologic.com/) | Apps:
| [Superwise](https://superwise.ai/) | Webhook: [Superwise](/docs/integrations/webhooks/superwise/) |
-|
| [Sysdig](https://sysdig.com/) | Cloud SIEM integration: [Sysdig](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/c4de0854-e718-45e1-a4c8-63623755aa43.md) |
-|
| [syslog-ng](https://www.syslog-ng.com/) | Automation integration: [Syslog-NG](/docs/platform-services/automation-service/app-central/integrations/syslog-ng/)
| [Tanium](https://www.tanium.com/) | Cloud SIEM integration: [Tanium](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/c7a342e6-5621-401a-ac5c-80ea3f2db23c.md)
| [Telegraf](https://www.influxdata.com/time-series-platform/telegraf/) | Collector: [Telegraf](/docs/send-data/collect-from-other-data-sources/collect-metrics-telegraf/) |
-|
| [Telegram](https://telegram.org/) | Automation integration: [Telegram V2](/docs/platform-services/automation-service/app-central/integrations/telegram-v2/) |
-|
| [Tenable](https://www.tenable.com/) | App: [Tenable](/docs/integrations/saas-cloud/tenable/)
| [Tessian](https://www.tessian.com/) | Partner integration: [Tessian for Sumo Logic](https://github.com/SumoLogic/sumologic-public-partner-apps/tree/master/Tessian#tessian-for-sumo-logic) |
-|
| [TheHive](https://thehive-project.org/) | Automation integration: [TheHive](/docs/platform-services/automation-service/app-central/integrations/thehive/) |
-|
| [Thinkst Canary](https://canary.tools/) | [Thinkst Canary](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/0152e233-fce6-4cbf-9edc-721d7bef94f8.md) |
-|
| [ThreatConnect](https://threatconnect.com/) | Automation integration: [ThreatConnect](/docs/platform-services/automation-service/app-central/integrations/threatconnect/) |
-|
| [Threat Crowd](https://otx.alienvault.com/) | Automation integration: [Threat Crowd](/docs/platform-services/automation-service/app-central/integrations/threat-crowd/) |
-|
| [Threater](https://www.threater.com/) | Cloud SIEM integration: [Bandura](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/ec354a4c-a761-4e18-8ceb-194d6e8692e2.md) |
-|
| [ThreatMiner](https://www.threatminer.org/) | Automation integration: [ThreatMiner](/docs/platform-services/automation-service/app-central/integrations/threatminer/) |
-|
| [ThreatQ](https://www.threatq.com/) | Automation integration: [ThreatQ](/docs/platform-services/automation-service/app-central/integrations/threatq/) |
-|
| [Trellix](https://www.trellix.com/en-us/index.html) | Automation integrations:
| [Tufin](https://www.tufin.com/) | Automation integrations:
| [Uptime](https://uptime.com/) | Webhook: [Uptime](/docs/integrations/webhooks/uptime/) |
-|
| [URLScan.io](https://urlscan.io/) | Automation integration: [URLScan.io](/docs/platform-services/automation-service/app-central/integrations/urlscan.io/) |
-
-## V
-
-| Logo | Vendors and Products | Integrations |
-| :-- | :-- | :-- |
-|
| [Varnish](https://www.varnish-software.com/) | Apps:
| [Varonis](https://www.varonis.com/) | Cloud SIEM integration: [Varonis](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/20270f89-127e-4055-96ec-56045e67e163.md) |
-|
| [Vectra](https://www.vectra.ai/) | Automation integration: [Vectra](/docs/platform-services/automation-service/app-central/integrations/vectra/)
| [VirusTotal](https://www.virustotal.com/) | Automation integration: [VirusTotal](/docs/platform-services/automation-service/app-central/integrations/virustotal/) |
-|
| [VMRay](https://www.vmray.com/) | Automation integration: [VMRay](/docs/platform-services/automation-service/app-central/integrations/vmray/) |
-|
| [VMware](https://www.vmware.com/) | Apps:
| [Votiro](https://votiro.com/) | Partner integration: [Votiro](https://github.com/SumoLogic/sumologic-public-partner-apps/tree/master/Votiro#votiro) |
-
-## W
-
-| Logo | Vendors and Products | Integrations |
-| :-- | :-- | :-- |
-|
| [Watchguard](https://www.watchguard.com/) | Automation integration: [Panda EDR](/docs/platform-services/automation-service/app-central/integrations/panda-edr/) |
-|
| [WhoisXML](https://main.whoisxmlapi.com/) | Automation integration: [WhoisXML](/docs/platform-services/automation-service/app-central/integrations/whoisxml/) |
-|
| [Windows](https://www.microsoft.com/en-us/windows) | Apps:
| [WithSecure](https://www.withsecure.com/en/home) | Automation integrations:
| [Wittra](https://www.wittra.io/) | Automation integration: [Wittra](/docs/platform-services/automation-service/app-central/integrations/wittra/) |
-|
| [Wiz](https://www.wiz.io/) | Cloud SIEM integration: [Wiz](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/2cde0cac-102b-4756-9a56-81437fea1400.md) |
-|
| [Workday](https://www.workday.com/) | App: [Workday](/docs/integrations/saas-cloud/workday/)
| [Zebrium](https://www.zebrium.com/) | Webhook: [Zebrium RCaaS](/docs/integrations/webhooks/zebrium-rcaas/) |
-|
| [Zendesk](https://www.zendesk.com/) | Automation integration: [Zendesk](/docs/platform-services/automation-service/app-central/integrations/zendesk/) |
-|
| [Zenduty](https://www.zenduty.com/) | Webhook: [Zenduty](/docs/integrations/webhooks/zenduty/) |
-|
| [ZeroFox](https://www.zerofox.com/) | Automation integration: [ZeroFOX](/docs/platform-services/automation-service/app-central/integrations/zerofox/)
| [Zoom](https://zoom.us/) | App: [Zoom](/docs/integrations/saas-cloud/zoom/)
| [Zscaler](https://www.zscaler.com/) | Apps:
| [Mailgun](https://www.mailgun.com/) | Webhook: [Mailgun](/docs/integrations/webhooks/mailgun/) |
+|
| [Malwarebytes](https://www.malwarebytes.com/) | Automation integration: [Malwarebytes Nebula](/docs/platform-services/automation-service/app-central/integrations/malwarebytes-nebula/)
| [ManageEngine](https://www.manageengine.com/) | Automation integration: [ManageEngine Desktop Central](/docs/platform-services/automation-service/app-central/integrations/manage-engine-desktop-central/)
| [MariaDB](https://mariadb.org/) | Apps:
| [Material Security](https://material.security/) | Automation integration: [Material Security](/docs/platform-services/automation-service/app-central/integrations/material-security/) |
+|
| [Mattermost](https://mattermost.com/) | Automation integration: [Mattermost](/docs/platform-services/automation-service/app-central/integrations/mattermost/) |
+|
| [MaxMind](https://www.maxmind.com/en/home) | Automation integration: [MaxMind V2](/docs/platform-services/automation-service/app-central/integrations/maxmind-v2/) |
+|
| [McAfee](https://www.mcafee.com/) | Automation integrations:
| [Memcached](https://memcached.org/) | Apps:
| [Microsoft](https://www.microsoft.com/) | Apps:
| [Mimecast](https://www.mimecast.com/) | App: [Mimecast](/docs/integrations/saas-cloud/mimecast/)
| [Miro](https://miro.com/) | App: [Miro](/docs/integrations/saas-cloud/miro/)
| [MISP](https://www.misp-project.org/) | Automation integration: [MISP](/docs/platform-services/automation-service/app-central/integrations/misp/)
| [MITRE ATT&CK](https://attack.mitre.org/) | Automation integration: [Mitre Matrix](/docs/platform-services/automation-service/app-central/integrations/mitre-matrix/) |
+|
| [MongoDB](https://www.mongodb.com/) | Apps:
| [MongoDB Atlas](https://www.mongodb.com/atlas) | App: [MongoDB Atlas](/docs/integrations/databases/mongodb-atlas/) |
+|
| [mParticle](https://www.mparticle.com/) | Webhook: [mParticle](/docs/integrations/webhooks/mparticle/) |
+|
| [MxToolbox](https://mxtoolbox.com/) | Automation integration: [MxToolbox](/docs/platform-services/automation-service/app-central/integrations/mxtoolbox/) |
+|
| [MySQL](https://www.mysql.com/) | Apps:
| [Netlify](https://www.netlify.com/) | Webhook: [Netlify](/docs/integrations/webhooks/netlify/) |
+|
| [NETSCOUT](https://www.netscout.com/) | Automation integration: [Arbor (NETSCOUT)](/docs/platform-services/automation-service/app-central/integrations/arbor/) |
+|
| [Netskope](https://www.netskope.com/) | Apps:
| [Neustar](https://www.home.neustar/) | Automation integration: [Neustar IP GeoPoint](/docs/platform-services/automation-service/app-central/integrations/neustar-ip-geopoint/) |
+|
| [New Relic](https://newrelic.com/) | Webhook: [Webhook Connection for New Relic](/docs/alerts/webhook-connections/new-relic/) |
+|
| [Nmap](https://nmap.org/) | Automation integration: [Nmap](/docs/platform-services/automation-service/app-central/integrations/nmap/) |
+|
| [Nobl9](https://www.nobl9.com/) | Webhook: [Nobl9](/docs/integrations/webhooks/nobl9/) |
+|
| [Nozomi Networks](https://www.nozominetworks.com/) | Automation integration: [Nozomi Networks](/docs/platform-services/automation-service/app-central/integrations/nozomi-networks/) |
+|
| [Nucleon](https://nucleoncyber.com/) | Automation integration: [Nucleon Cyber](/docs/platform-services/automation-service/app-central/integrations/nucleon-cyber/)
| [NXLog](https://nxlog.co/) | Partner integration: [NXLog](https://nxlog.co/technology-ecosystem) |
+
+## O
+
+| Logo | Vendors and Products | Integrations |
+| :-- | :-- | :-- |
+|
| [Observable Networks](https://www.cisco.com/c/en/us/services/acquisitions/observable-networks.html) | App: [Observable Networks](/docs/integrations/security-threat-detection/observable-networks/) |
+|
| [OISF](https://oisf.net/) | Cloud SIEM integration: [OISF](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/9c138edd-dc14-43a6-b751-52e41a8bd105.md) |
+|
| [Okta](https://www.okta.com/) | App: [Okta](/docs/integrations/saml/okta/)
| [OneLogin](https://www.onelogin.com/) | App: [OneLogin](/docs/integrations/saml/onelogin/)
| [1Password](https://1password.com/) | App: [1Password](/docs/integrations/1password/)
| [OneTrust](https://www.onetrust.com/) | Automation integration: [OneTrust](/docs/platform-services/automation-service/app-central/integrations/onetrust/) |
+|
| [OpenAI](https://openai.com/) | Automation integration: [OpenAI ChatGPT](/docs/platform-services/automation-service/app-central/integrations/openai-chatgpt/) |
+|
| [OpenLDAP](https://www.openldap.org/) | Automation integration: [OpenLDAP](/docs/platform-services/automation-service/app-central/integrations/openldap/) |
+|
| [OpenSSH](https://www.openssh.com/) | Cloud SIEM integration: [OpenSSH](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/d0bf0b9f-162e-4d1e-9b89-38e8d526a434.md) |
+|
| [OpenText](https://www.opentext.com/) | Automation integrations:
| [OpenVPN](https://openvpn.net/) | Cloud SIEM integration: [OpenVPN](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/8e5a85b3-a95e-47d9-adcf-bb543e6580c0.md) |
+|
| [Opsgenie](https://www.atlassian.com/software/opsgenie) | App: [Opsgenie](/docs/integrations/saas-cloud/opsgenie/)
| [OpsRamp](https://www.opsramp.com/) | Partner integration: [OpsRamp](https://docs.opsramp.com/integrations/a2r/3rd-party/sumologic/) |
+|
| [Opswat](https://www.opswat.com/) | Automation integration: [Opswat Metadefender](/docs/platform-services/automation-service/app-central/integrations/opswat-metadefender/) |
+|
| [Oracle Database](https://www.oracle.com/database/) | Apps:
| [Orca Security](https://orca.security/) | Cloud SIEM integration: [Orca Security](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/ab5b4909-20f7-4cf7-b8de-24f4a5b2ba57.md) |
+|
| [osquery](https://osquery.io/) | Cloud SIEM integration: [Osquery](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/eca511e4-0daa-41f7-919e-ec4d0ac1558f.md)
| [Ossec](https://www.ossec.net/) | Cloud SIEM integration: [Ossec](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/1eceb40f-85d7-45ea-b341-864a38ea0775.md) |
+
+## P
+
+| Logo | Vendors and Products | Integrations |
+| :-- | :-- | :-- |
+|
| [PagerDuty](https://www.pagerduty.com/) | Apps:
| [Palo Alto Networks](https://www.paloaltonetworks.com/) | Apps:
| [PaperTrail](https://www.papertrail.com/) | Webhook: [PaperTrail](/docs/integrations/webhooks/papertrail/) |
+|
| [Phantombuster](https://phantombuster.com/) | Automation integration: [Phantombuster](/docs/platform-services/automation-service/app-central/integrations/phantombuster/) |
+|
| [PhishTank](https://phishtank.org/) | Automation integration: [PhishTank](/docs/platform-services/automation-service/app-central/integrations/phishtank/) |
+|
| [PostgreSQL](https://www.postgresql.org/) | Apps:
| [Postman](https://www.postman.com/) | Webhook: [Postman](/docs/integrations/webhooks/postman/) |
+|
| [Pritunl](https://pritunl.com/) | Cloud SIEM integration: [Pritunl](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/598b6820-feff-4169-89da-77211493a91d.md) |
+|
| [Prometheus](https://prometheus.io/) | Collector: [Collect Prometheus Metrics](/docs/send-data/collect-from-other-data-sources/collect-prometheus-metrics/) |
+|
| [Proofpoint](https://www.proofpoint.com/us) | Apps:
| [ProtectOnce](https://protectonce.com/) | Automation integration: [ProtectOnce](/docs/platform-services/automation-service/app-central/integrations/protectonce/) |
+|
| [Pulsedive](https://pulsedive.com/) | Automation integration: [Pulsedive](/docs/platform-services/automation-service/app-central/integrations/pulsedive/) |
+|
| [Puppet](https://www.puppet.com/) | Apps:
| [Pusher](https://pusher.com/) | Webhook: [Pusher](/docs/integrations/webhooks/pusher/) |
+
+## Q
+
+| Logo | Vendors and Products | Integrations |
+| :-- | :-- | :-- |
+|
| [RabbitMQ](https://www.rabbitmq.com/) | Apps:
| [Rapid7](https://www.rapid7.com/) | App: [Rapid7](/docs/integrations/saas-cloud/rapid7/)
| [RapidAPI](https://rapidapi.com/) | Automation integration: [RapidAPI](/docs/platform-services/automation-service/app-central/integrations/rapidapi/) |
+|
| [Recorded Future](https://www.recordedfuture.com/) | Automation integration: [Recorded Future](/docs/platform-services/automation-service/app-central/integrations/recorded-future/) |
+|
| [Red Hat OpenShift](https://www.redhat.com/en/technologies/cloud-computing/openshift) | Partner integration: [Red Hat OpenShift](https://docs.openshift.com/acs/3.74/integration/integrate-with-sumologic.html)
| [Redis](https://redis.io/) | Apps:
| [RiskIQ](https://community.riskiq.com/) | Automation integration: [Passive Total](/docs/platform-services/automation-service/app-central/integrations/passive-total/) |
+|
| [Rollbar](https://rollbar.com/) | Webhook: [Rollbar](/docs/integrations/webhooks/rollbar/) |
+|
| [RSA](https://www.rsa.com/) | Automation integrations:
| [rsyslog](https://www.rsyslog.com/) | Collector: [rsyslog](/docs/send-data/hosted-collectors/cloud-syslog-source/rsyslog/) |
+|
| [Ruby on Rails](https://rubyonrails.org/) | Collector: [Collect Ruby on Rails Logs](/docs/send-data/collect-from-other-data-sources/collect-ruby-on-rails-logs/) |
+
+
+## S
+
+| Logo | Vendors and Products | Integrations |
+| :-- | :-- | :-- |
+|
| [Sauce Labs](https://saucelabs.com/) | Partner integration: [Sauce Labs](https://docs.saucelabs.com/basics/integrations/sumo/) |
+|
| [Screenshot Machine](https://www.screenshotmachine.com/) | Automation integration: [Screenshot Machine](/docs/platform-services/automation-service/app-central/integrations/screenshot-machine/) |
+|
| [SecureAuth](https://www.secureauth.com/) | Cloud SIEM integration: [SecureAuth](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/72744d1c-ddff-4ead-b76e-60430704f945.md) |
+|
| [Security Scorecard](https://securityscorecard.com/) | Automation integration: [Security Scorecard](/docs/platform-services/automation-service/app-central/integrations/security-scorecard/) |
+|
| [SecurityTrails](https://securitytrails.com/) | Automation integration: [SecurityTrails](/docs/platform-services/automation-service/app-central/integrations/securitytrails/) |
+|
| [Securonix](https://www.securonix.com/) | Automation integrations:
| [SendGrid](https://sendgrid.com/) | Webhook: [SendGrid](/docs/integrations/webhooks/sendgrid/) |
+|
| [Sensu](https://sensu.io/) | Partner integration: [Send data to Sumo Logic with Sensu](https://docs.sensu.io/sensu-go/latest/observability-pipeline/observe-process/send-data-sumo-logic/) |
+|
| [SIGNL4](https://www.signl4.com/) | Webhooks:
| [Sentry](https://sentry.io/welcome/) | Webhook: [Sentry](/docs/integrations/webhooks/sentry/) |
+|
| [ServiceNow](https://www.servicenow.com/) | Automation integration: [ServiceNow V2](/docs/platform-services/automation-service/app-central/integrations/servicenow-v2/)
| [Shodan](https://www.shodan.io/) | Automation integration: [Shodan](/docs/platform-services/automation-service/app-central/integrations/shodan/) |
+|
| [Silent Push](https://www.silentpush.com/) | Automation integration: [Silent Push](/docs/platform-services/automation-service/app-central/integrations/silent-push) |
+|
| [Slack](https://slack.com/) | App: [Slack](/docs/integrations/saas-cloud/slack/)
| [Snare](https://www.snaresolutions.com/) | Cloud SIEM integration: [Intersect Alliance](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/005c835d-f067-4147-9da9-fe4d2691247e.md) |
+|
| [Snowflake](https://www.snowflake.com/en/) | Cloud SIEM integration: [Snowflake](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/5541f59d-e27d-48e6-a35c-34fb75e9cf13.md) |
+|
| [Snyk](https://snyk.io/) | Automation integration: [Snyk](/docs/platform-services/automation-service/app-central/integrations/snyk/) |
+|
| [SOCRadar](https://socradar.io/) | Automation integration: [SOCRadar](/docs/platform-services/automation-service/app-central/integrations/socradar/) |
+|
| [SonicWall](https://www.sonicwall.com/) | Automation integration: [SonicWall](/docs/platform-services/automation-service/app-central/integrations/sonicwall/) |
+|
| [Sophos](https://www.sophos.com/en-us) | Automation integrations:
| [SpiderFoot HX](https://login.hx.spiderfoot.net/) | Automation integration: [SpiderFoot HX](/docs/platform-services/automation-service/app-central/integrations/spiderfoot-hx/) |
+|
| [Spinnaker](https://spinnaker.io/) | Partner integration: [Spinnaker](https://docs.armory.io/continuous-deployment/armory-admin/observe/integrations-sumologic/) |
+|
| [Split](https://www.split.io/) | Webhook: [Split](/docs/integrations/webhooks/split/) |
+|
| [Splunk](https://www.splunk.com/) | Automation integration: [Splunk](/docs/platform-services/automation-service/app-central/integrations/splunk/)
| [Squadcast](https://www.squadcast.com/) | Webhook: [Squadcast](/docs/integrations/webhooks/squadcast/) |
+|
| [Squid Cache](http://www.squid-cache.org/) | Apps:
| [StackRox](https://www.stackrox.io/) | Collector: [StackRox](https://cdn.stackrox.io/integrations/sumologic-stackrox-app.pdf)
| [StatsD](https://www.datadoghq.com/blog/statsd/) | Collector: [Collect StatsD Metrics](/docs/send-data/collect-from-other-data-sources/collect-statsd-metrics/) |
+|
| [Stellar Cyber](https://stellarcyber.ai/) | Automation integration: [Stellar Cyber Starlight](/docs/platform-services/automation-service/app-central/integrations/stellar-cyber-starlight/) |
+|
| [Strimzi](https://strimzi.io/) | App: [Strimzi Kafka](/docs/integrations/containers-orchestration/strimzi-kafka/) |
+|
| [Stripe](https://stripe.com/) | Webhook: [Stripe](/docs/integrations/webhooks/stripe/) |
+|
| [Sucuri](https://sucuri.net/) | Cloud SIEM integration: [Sucuri](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/cdfd2ba0-77eb-4e11-b071-6f4d01fda607.md) |
+|
| [Sumo Logic](https://www.sumologic.com/) | Apps:
| [Superwise](https://superwise.ai/) | Webhook: [Superwise](/docs/integrations/webhooks/superwise/) |
+|
| [Sysdig](https://sysdig.com/) | Cloud SIEM integration: [Sysdig](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/c4de0854-e718-45e1-a4c8-63623755aa43.md) |
+|
| [syslog-ng](https://www.syslog-ng.com/) | Automation integration: [Syslog-NG](/docs/platform-services/automation-service/app-central/integrations/syslog-ng/)
| [Tanium](https://www.tanium.com/) | Cloud SIEM integration: [Tanium](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/c7a342e6-5621-401a-ac5c-80ea3f2db23c.md)
| [Telegraf](https://www.influxdata.com/time-series-platform/telegraf/) | Collector: [Telegraf](/docs/send-data/collect-from-other-data-sources/collect-metrics-telegraf/) |
+|
| [Telegram](https://telegram.org/) | Automation integration: [Telegram V2](/docs/platform-services/automation-service/app-central/integrations/telegram-v2/) |
+|
| [Tenable](https://www.tenable.com/) | App: [Tenable](/docs/integrations/saas-cloud/tenable/)
| [Tessian](https://www.tessian.com/) | Partner integration: [Tessian for Sumo Logic](https://github.com/SumoLogic/sumologic-public-partner-apps/tree/master/Tessian#tessian-for-sumo-logic) |
+|
| [TheHive](https://thehive-project.org/) | Automation integration: [TheHive](/docs/platform-services/automation-service/app-central/integrations/thehive/) |
+|
| [Thinkst Canary](https://canary.tools/) | Cloud SIEM integration: [Thinkst Canary](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/0152e233-fce6-4cbf-9edc-721d7bef94f8.md) |
+|
| [ThreatConnect](https://threatconnect.com/) | Automation integration: [ThreatConnect](/docs/platform-services/automation-service/app-central/integrations/threatconnect/) |
+|
| [Threat Crowd](https://otx.alienvault.com/) | Automation integration: [Threat Crowd](/docs/platform-services/automation-service/app-central/integrations/threat-crowd/) |
+|
| [Threater](https://www.threater.com/) | Cloud SIEM integration: [Bandura](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/ec354a4c-a761-4e18-8ceb-194d6e8692e2.md) |
+|
| [ThreatMiner](https://www.threatminer.org/) | Automation integration: [ThreatMiner](/docs/platform-services/automation-service/app-central/integrations/threatminer/) |
+|
| [ThreatQ](https://www.threatq.com/) | Automation integration: [ThreatQ](/docs/platform-services/automation-service/app-central/integrations/threatq/) |
+|
| [Trellix](https://www.trellix.com/en-us/index.html) | Automation integrations:
| [Tufin](https://www.tufin.com/) | Automation integrations:
| [Uptime](https://uptime.com/) | Webhook: [Uptime](/docs/integrations/webhooks/uptime/) |
+|
| [URLScan.io](https://urlscan.io/) | Automation integration: [URLScan.io](/docs/platform-services/automation-service/app-central/integrations/urlscan.io/) |
+
+## V
+
+| Logo | Vendors and Products | Integrations |
+| :-- | :-- | :-- |
+|
| [Varnish](https://www.varnish-software.com/) | Apps:
| [Varonis](https://www.varonis.com/) | Cloud SIEM integration: [Varonis](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/20270f89-127e-4055-96ec-56045e67e163.md) |
+|
| [Vectra](https://www.vectra.ai/) | Automation integration: [Vectra](/docs/platform-services/automation-service/app-central/integrations/vectra/)
| [VirusTotal](https://www.virustotal.com/) | Automation integration: [VirusTotal](/docs/platform-services/automation-service/app-central/integrations/virustotal/) |
+|
| [VMRay](https://www.vmray.com/) | Automation integration: [VMRay](/docs/platform-services/automation-service/app-central/integrations/vmray/) |
+|
| [VMware](https://www.vmware.com/) | Apps:
| [Votiro](https://votiro.com/) | Partner integration: [Votiro](https://github.com/SumoLogic/sumologic-public-partner-apps/tree/master/Votiro#votiro) |
+
+## W
+
+| Logo | Vendors and Products | Integrations |
+| :-- | :-- | :-- |
+|
| [Watchguard](https://www.watchguard.com/) | Automation integration: [Panda EDR](/docs/platform-services/automation-service/app-central/integrations/panda-edr/) |
+|
| [WhoisXML](https://main.whoisxmlapi.com/) | Automation integration: [WhoisXML](/docs/platform-services/automation-service/app-central/integrations/whoisxml/) |
+|
| [Windows](https://www.microsoft.com/en-us/windows) | Apps:
| [WithSecure](https://www.withsecure.com/en/home) | Automation integrations:
| [Wittra](https://www.wittra.io/) | Automation integration: [Wittra](/docs/platform-services/automation-service/app-central/integrations/wittra/) |
+|
| [Wiz](https://www.wiz.io/) | Cloud SIEM integration: [Wiz](https://github.com/SumoLogic/cloud-siem-content-catalog/blob/master/vendors/2cde0cac-102b-4756-9a56-81437fea1400.md) |
+|
| [Workday](https://www.workday.com/) | App: [Workday](/docs/integrations/saas-cloud/workday/)
| [Zebrium](https://www.zebrium.com/) | Webhook: [Zebrium RCaaS](/docs/integrations/webhooks/zebrium-rcaas/) |
+|
| [Zendesk](https://www.zendesk.com/) | Automation integration: [Zendesk](/docs/platform-services/automation-service/app-central/integrations/zendesk/) |
+|
| [Zenduty](https://www.zenduty.com/) | Webhook: [Zenduty](/docs/integrations/webhooks/zenduty/) |
+|
| [ZeroFox](https://www.zerofox.com/) | Automation integration: [ZeroFOX](/docs/platform-services/automation-service/app-central/integrations/zerofox/)
| [Zoom](https://zoom.us/) | App: [Zoom](/docs/integrations/saas-cloud/zoom/)
| [Zscaler](https://www.zscaler.com/) | Apps: