Skip to content

tenable_io: terminate ingest pipeline execution in agent error conditions - #19489

Merged
efd6 merged 1 commit into
elastic:mainfrom
efd6:tenable_io-terminations
Jun 12, 2026
Merged

tenable_io: terminate ingest pipeline execution in agent error conditions#19489
efd6 merged 1 commit into
elastic:mainfrom
efd6:tenable_io-terminations

Conversation

@efd6

@efd6 efd6 commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

Proposed commit message

tenable_io: terminate ingest pipeline execution in agent error conditions

When there is no message or event.original, but event.error is set, we
should not attempt to continue.

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

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Screenshots

@efd6 efd6 self-assigned this Jun 11, 2026
@efd6 efd6 added Integration:tenable_io Tenable Vulnerability Management bugfix Pull request that fixes a bug issue Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations] labels Jun 11, 2026
@github-actions

github-actions Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

Elastic Docs Style Checker (Vale)

Summary: 1 suggestion found

💡 Suggestions (1): Optional style improvements. Apply when helpful.
File Line Rule Message
packages/tenable_io/changelog.yml 4 Elastic.WordChoice Consider using 'stop, exit' instead of 'terminate', unless the term is in the UI.

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.

@efd6
tenable_io: terminate ingest pipeline execution in agent error condit…
0f5821f 
…ions

When there is no message or event.original, but event.error is set, we
should not attempt to continue.
@efd6
efd6 force-pushed the tenable_io-terminations branch from b83c838 to 0f5821f Compare June 11, 2026 02:31
@github-actions

github-actions Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

TL;DR

Buildkite failed due to an invalid changelog PR link in packages/tenable_io/changelog.yml (link resolves to .../pull/ with no number). Fix that link to this PR (https://github.com/elastic/integrations/pull/19489) or an issue URL, then rerun CI.

Remediation

  • Update the new changelog entry in packages/tenable_io/changelog.yml so link is a valid URL with a positive numeric ID (for this PR: https://github.com/elastic/integrations/pull/19489).
  • Re-run check_changelog_entries.sh / package check after updating the changelog link.
Investigation details

Root Cause

Both failed jobs point to the same metadata validation failure in the changelog entry introduced in this PR:

  • :scroll: Check changelog PR links fails with an explicit mismatch.
  • Check integrations tenable_io fails during package lint with the same changelog-link parse error.

Evidence

  • Build: https://buildkite.com/elastic/integrations/builds/44388
  • Jobs/steps:
    • :scroll: Check changelog PR links
    • Check integrations tenable_io
  • Key log excerpts:
    • ERROR: unexpected link: 'https://github.com/elastic/integrations/pull/'
    • expected: 'https://github.com/elastic/integrations/pull/19489'
    • issue number in changelog link should be a positive number
  • File referenced by failing checks: packages/tenable_io/changelog.yml

Verification

  • Not run locally against PR commit: this runner checkout does not contain commit b83c838bf44b5c811c81b2d17ad9cb3fd8a4fe94, so analysis is based on Buildkite logs and local repository inspection.

Follow-up

If this link is intentionally not a PR reference, use an issue link format (.../issues/<n>) or apply the changelog-link-check:skip label as indicated by the CI message.

Note

🔒 Integrity filter blocked 2 items

The following items were blocked because they don't meet the GitHub integrity level.

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

What is this? | From workflow: PR Buildkite Detective

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

@efd6

efd6 commented Jun 11, 2026

Copy link
Copy Markdown
Contributor Author

/test

@elastic-vault-github-plugin-prod

elastic-vault-github-plugin-prod Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

✅ All changelog entries have the correct PR link.

@elastic-vault-github-plugin-prod

elastic-vault-github-plugin-prod Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@elasticmachine

elasticmachine commented Jun 11, 2026

Copy link
Copy Markdown

💚 Build Succeeded

History

cc @efd6

@efd6
efd6 marked this pull request as ready for review June 11, 2026 03:14
@efd6
efd6 requested review from a team as code owners June 11, 2026 03:14
@infra-vault-gh-plugin-prod

infra-vault-gh-plugin-prod Bot commented Jun 11, 2026

Copy link
Copy Markdown

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

@efd6
efd6 merged commit 81060d3 into elastic:main Jun 12, 2026
9 checks passed
@elastic-vault-github-plugin-prod

elastic-vault-github-plugin-prod Bot commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

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

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

Reviewers

@brijesh-elastic brijesh-elastic brijesh-elastic approved these changes

Assignees

@efd6 efd6

Labels

bugfix Pull request that fixes a bug issue Integration:tenable_io Tenable Vulnerability Management Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations]

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

tenable_io: some data streams do not terminate on agent error

3 participants

@efd6 @elasticmachine @brijesh-elastic