Skip to main content

Elasticsearch Event Collector

This Integration is part of the Elasticsearch Pack.#

Supported versions

Supported Cortex XSOAR versions: 8.4.0 and later.

Elasticsearch Event Collector integration is used to search for and analyze data in real time. Supports version 6 and later.

Configure Elasticsearch Event Collector in Cortex#

ParameterDescriptionRequired
Server URLThe Elasticsearch server to which the integration connects. Ensure that the URL includes the correct Elasticsearch port. The default port for Elasticsearch v7 and below is 9200. Use the Server URL for on-premises deployments.False
Authorization typeSelect the authentication type and enter the appropriate credentials:
- Basic Auth: Enter Username and Password.
- Bearer Auth: Enter Username and Password.
- API Key Auth: Enter the API Key ID and API Key.
True
API key IDUse for API key authFalse
API KeyUse for API key authFalse
UsernameUse for Basic auth. Optionally you can use Username as an API key ID and Password as an API key for API Key auth.False
PasswordUse for Basic auth. Optionally you can use Username as an API key ID and Password as an API key for API Key auth.False
Trust any certificate (not secure)False
Use system proxy settingsFalse
Client typeIn some hosted ElasticSearch environments, the standard ElasticSearch client is not supported. If you encounter any related client issues, please consider using the OpenSearch client type.False
Index to fetch events fromCSVFalse
Query StringQuery string uses the Lucene syntax.
For more information about the Lucene syntax see here.
The query will be used when fetching events. Index time field will be used as a filter in the query.
False
Index time fieldThe time field used for sorting and limiting results. If using a nested field, separate field names with dot notation.False
Raw QueryRaw Query allows raw DSL queries and will override the 'Query String' Lucene syntax string.
Results will not be filtered or sorted. Use additional parameters in the raw query for these purposes.
For more information about Query DSL see here.
False
Time field type3 formats supported:
Simple-Date - A plain date string. You must specify the format in which the date is stored.
For more information about time formatting, see here.
Timestamp-Second - A numeric value representing the number of seconds since the Unix epoch (00:00:00 UTC on 1 January 1970). Example: '1572164838'
* Timestamp-Milliseconds - A numeric value representing the number of milliseconds since the Unix epoch. Example: '1572164838123'
False
Map JSON fields into labelsFalse
The maximum number of results per fetchFalse
Request timeout (in seconds).False
Fetch eventsFalse

Commands#

You can execute these commands from the Cortex XSOAR CLI, as part of an automation, or in a playbook. After you successfully execute a command, a DBot message appears in the War Room with the command details.

es-get-events#


Gets events from Elasticsearch. This command is used for developing/ debugging and is to be used with caution, as it can cause the API request limit to be exceeded.

Base Command#

es-get-events

Input#

Argument NameDescriptionRequired
start_timeStart time for fetching events. Supports ISO format ("2023-01-01T23:59:59") or natural language ("2 hours ago", "now").Required
end_timeEnd time for fetching events. Supports ISO format ("2023-01-01T23:59:59") or natural language ("2 hours ago", "now").Optional
time_methodFor more information see the explanation in the help section.Required
fetch_sizeThe maximum number of results per fetch, default 10.Optional
fetch_indexCSV.Optional
fetch_time_fieldThe time field used for sorting and limiting results. If using a nested field, separate field names with dot notation.Required
fetch_queryQuery string uses the Lucene syntax.Optional
raw_queryRaw Query allows raw DSL queries and will override the 'Query String' Lucene syntax string.Optional

Context Output#

There is no context output for this command.