# Sumo Logic
{% hint style="info" %}
Cortex connects to many third-party vendors whose system interfaces frequently change. As a result, integration behavior or configuration steps may shift without notice. If you encounter unexpected issues, check with your system administrator or refer to the vendor's documentation for the most current information. Additionally, integration sync times vary and are subject to scheduling overrides and timing variance.
{% endhint %}
## Overview
[Sumo Logic](https://www.sumologic.com/) is a cloud-based observability platform that provides log management and analytics. Integrate Sumo Logic with Cortex to drive insights into service-level objectives (SLOs).
## How to configure Sumo Logic with Cortex
### Prerequisites
Before getting started:
* [Generate an access key](https://help.sumologic.com/docs/api/getting-started/#authentication) in Sumo Logic.
* Determine your [assigned deployment](https://help.sumologic.com/docs/api/getting-started/#sumo-logic-endpoints-by-deployment-and-firewall-security) in Sumo Logic.
### Configure the integration in Cortex
1. In Cortex, navigate to the [Sumo Logic settings page](https://app.getcortexapp.com/admin/integrations/sumologic):
* Click **Integrations** from the main nav. Search for and select **Sumo Logic**.
2. Click **Add configuration**.
3. Configure the Sumo Logic integration form:
* **Access ID**: Enter the access ID for Sumo Logic.
* **Access key**: Enter the access key you generated in Sumo Logic.
* **Deployment**: Enter your Sumo Logic deployment.
4. Click **Save**.
### Linking SLOs in Cortex
You can create and manage SLOs by listing SLO IDs in the entity descriptor:
```yaml
x-cortex-slos:
sumologic:
- id: 000000000001234
- id: 000000000006789
```
## Using the Sumo Logic integration
#### Entity pages
When an SLO is defined in an entity's descriptor, you'll see an overview of SLO information in the **Monitoring** block on an [entity details page](/ingesting-data-into-cortex/entities-overview/entities/details.md) overview.
On the left side of an entity, click **Monitoring > Sumo Logic** to view the SLO query, target(s), current value for each SLO, a graph of SLO performance over time, and the period of time the SLO is being calculated for. For example, if the time listed is "7 days ago," then the SLO is looking at the time range starting 7 days ago to now.
### Scorecards and CQL
With the Sumo Logic integration, you can create Scorecard rules and write CQL queries based on Sumo Logic SLOs.
See more examples in the [CQL Explorer](https://app.getcortexapp.com/admin/cql-explorer) in Cortex.
SLOs
SLOs associated with the entity via ID or tags. You can use this data to check whether an entity has SLOs associated with it, and if those SLOs are passing.
**Definition:** `slos: List`
**Example**
In a Scorecard, you can use this expression to make sure an entity is passing its SLOs:
```
slos().all((slo) => slo.passing) == true
```
Use this expression to make sure latency Service Level Indicator (SLI) value is above 99.99%:
```
slos().filter((slo) => slo.name.matchesIn("latency") and slo.sliValue >= 0.9999).length > 0
```
### View integration logs
{% hint style="info" %}
This feature is available in Cortex cloud.
{% endhint %}
While viewing an integration's settings page, select the **Logs** tab to view error logs from the last 7 days. You can filter the logs list by configuration and by operation (for example, you could filter to view errors surfaced only via Scorecards).
Click into a row to get more information, including time stamp, status code, full error, and request path.
## Still need help?[](https://docs.cortex.io/docs/reference/integrations/aws#still-need-help)
The following options are available to get assistance from the Cortex Customer Engineering team:
* **Email**: , or open a support ticket in the in app Resource Center
* **Slack**: Users with a connected Slack channel will have a workflow added to their account. From here, you can either @CortexTechnicalSupport or add a `:ticket:` reaction to a question in Slack, and the team will respond directly.
Don’t have a Slack channel? Talk with your Customer Success Manager.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.cortex.io/ingesting-data-into-cortex/integrations/sumologic.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.