> For the complete documentation index, see [llms.txt](https://docs.expel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.expel.io/connect-your-technology/q-z-integrations/sumo-logic/considerations-for-sumo-logic-flex-pricing-customers.md).
# Considerations for Sumo Logic Flex Pricing Customers
If you are setting up a via SIEM integration utilizing Sumo Logic, and are subject to Sumo Logic’s new Flex pricing, you will need to use Sumo Logic indexes in your device configuration in Workbench. This will prevent Expel from querying data outside of the indices you wish us to monitor.
{% hint style="info" %}
If you are using the traditional Sumo Logic pricing model, no action is needed at this time.
{% endhint %}
## Verify Your Pricing Plan
If you are unsure of your Sumo Logic plan type, navigate to the [Account Overview page](https://www.sumologic.com/help/docs/manage/manage-subscription/sumo-logic-credits-accounts/#account-overview) in Sumo Logic and confirm your plan type.
## Obtain the Indices
Identify the indices you wish Expel to query, and make a comma-separated list of them. For example: `sumologic_default,sumologic_audit_events,sumologic_system_events`
You can reference names you may want to query by navigating to the [Partitions page](https://www.sumologic.com/help/docs/manage/partitions/) in Sumo Logic.
\
When adding the new security device in Workbench, you will enter the comma-separated list into the Sumologic query indices field.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.expel.io/connect-your-technology/q-z-integrations/sumo-logic/considerations-for-sumo-logic-flex-pricing-customers.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
