Skip to content

Tenable IO: add max_executions to asset, audit, plugin, and scan data streams - #20192

Merged
chemamartinez merged 2 commits into
elastic:mainfrom
chemamartinez:tenable-io-max-executions
Jul 22, 2026
Merged

Tenable IO: add max_executions to asset, audit, plugin, and scan data streams#20192
chemamartinez merged 2 commits into
elastic:mainfrom
chemamartinez:tenable-io-max-executions

Conversation

@chemamartinez

Copy link
Copy Markdown
Contributor

Proposed commit message

[tenable_io] Add configurable max_executions to asset, audit, plugin, and scan data streams

The max_executions parameter was only exposed in the Fleet UI for the
vulnerability data stream. The asset, audit, plugin, and scan streams
all use CEL inputs with paginated API calls that can exceed the default
limit of executions under sufficient data volume, causing them to go
DEGRADED.

This change brings those streams to parity with vulnerability
by exposing the same optional parameter (default: 2000) in both the
manifest and the CEL template for each affected data stream.

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.
  • I have verified that any added dashboard complies with Kibana's Dashboard good practices
@chemamartinez chemamartinez self-assigned this Jul 17, 2026
@chemamartinez chemamartinez added enhancement New feature or request Integration:tenable_io Tenable Vulnerability Management Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations] labels Jul 17, 2026
@github-actions

Copy link
Copy Markdown
Contributor

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!


The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

@chemamartinez
chemamartinez marked this pull request as ready for review July 17, 2026 11:48
@chemamartinez
chemamartinez requested review from a team as code owners July 17, 2026 11:48
@infra-vault-gh-plugin-prod

Copy link
Copy Markdown

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

@elastic-vault-github-plugin-prod

Copy link
Copy Markdown
Contributor

✅ All changelog entries have the correct PR link.

@vera-review-bot

Copy link
Copy Markdown

⚠️ @chemamartinez I couldn't complete the review for commits 7d47185 after several attempts. A maintainer can re-run it with @vera-review-bot review.

@elastic-vault-github-plugin-prod

Copy link
Copy Markdown
Contributor

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@infra-vault-gh-plugin-prod

Copy link
Copy Markdown

💚 Build Succeeded

cc @chemamartinez

@mergify

mergify Bot commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

  • Queue this pull request
@chemamartinez
chemamartinez merged commit 16e24e4 into elastic:main Jul 22, 2026
9 checks passed
@elastic-vault-github-plugin-prod

Copy link
Copy Markdown
Contributor

Package tenable_io - 4.12.0 containing this change is available at https://epr.elastic.co/package/tenable_io/4.12.0/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request Integration:tenable_io Tenable Vulnerability Management Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations]

2 participants