Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions packages/ti_custom/_dev/build/docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -85,6 +85,14 @@

To facilitate IOC expiration, source datastream-backed indices `.ds-logs-ti_custom.indicator-*` are allowed to contain duplicates from each polling interval. ILM policy is added to these source indices so it doesn't lead to unbounded growth. This means data in these source indices will be deleted after `5 days` from ingested date.

## Troubleshooting

### "exceeding maximum number of CEL executions"

The CEL input limits how many pages it fetches during a single polling interval. The default is `1000`. High-volume TAXII feeds with large collections may exceed this limit, causing the integration to enter a DEGRADED state with this message.

Check notice on line 92 in packages/ti_custom/_dev/build/docs/README.md

View workflow job for this annotation

GitHub Actions / Lint Documentation

Elastic.WordChoice: Consider using 'can, might' instead of 'may', unless the term is in the UI.

To resolve this, increase `Maximum Pages Per Interval` in the integration's advanced settings. The value must be a positive integer and should be large enough to allow the agent to paginate through the full result set within one interval. Alternatively, reduce the polling interval so each run has fewer pages to fetch.

## Logs reference

### indicator
Expand Down
5 changes: 5 additions & 0 deletions packages/ti_custom/changelog.yml
Original file line number Diff line number Diff line change
@@ -1,4 +1,9 @@
# newer versions go on top
- version: "1.6.0"
changes:
- description: Document `max_executions` setting and add troubleshooting guidance for the "exceeding maximum number of CEL executions" error.
type: enhancement
link: https://github.com/elastic/integrations/pull/18898
- version: "1.5.0"
changes:
- description: Expose `max_executions` as an optional advanced parameter so users can raise the cap for high-volume feeds.
Expand Down
8 changes: 8 additions & 0 deletions packages/ti_custom/docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -85,6 +85,14 @@

To facilitate IOC expiration, source datastream-backed indices `.ds-logs-ti_custom.indicator-*` are allowed to contain duplicates from each polling interval. ILM policy is added to these source indices so it doesn't lead to unbounded growth. This means data in these source indices will be deleted after `5 days` from ingested date.

## Troubleshooting

### "exceeding maximum number of CEL executions"

The CEL input limits how many pages it fetches during a single polling interval. The default is `1000`. High-volume TAXII feeds with large collections may exceed this limit, causing the integration to enter a DEGRADED state with this message.

Check notice on line 92 in packages/ti_custom/docs/README.md

View workflow job for this annotation

GitHub Actions / Lint Documentation

Elastic.WordChoice: Consider using 'can, might' instead of 'may', unless the term is in the UI.

To resolve this, increase `Maximum Pages Per Interval` in the integration's advanced settings. The value must be a positive integer and should be large enough to allow the agent to paginate through the full result set within one interval. Alternatively, reduce the polling interval so each run has fewer pages to fetch.

## Logs reference

### indicator
Expand Down
2 changes: 1 addition & 1 deletion packages/ti_custom/manifest.yml
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ name: ti_custom
title: Custom Threat Intelligence
description: Ingest threat intelligence data in STIX 2.1 format with Elastic Agent
type: integration
version: "1.5.0"
version: "1.6.0"
categories:
- custom
- security
Expand Down
Loading