elastic / elastic/integrations
ssI: bug fixes for 19 beta→GA integrations (part-1)
- Dominant language
- Handlebars
- Stars
- 333
- Forks
- 647
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 209
Description
### Context
#20418 tracks promoting 19 beta integrations to GA (1.0.0)
### Fix two confirmed defects
Tagged telemetry pinpointed two real problems, as distinct from benign `on_failure`/`ignore_failure` probes that inflate failure counts without affecting the indexed document:
- [ ] `nozomi_networks` — `grok:grok_nozomi_networks_audit_username` fails on ~99.9% of `audit` documents (pattern requires an email followed by more text). It is `ignore_failure: true`, so no error surfaces, but `user.email` and `user.name` are effectively never populated. This is a broken enrichment, not an ingest error.
- [ ] `qualys_gav` — the `date:date_qualys_gav_asset_*_lifecycle_*_date` processors have an `on_failure` that appends to `error.message`, so documents are flagged as `pipeline_error` whenever Qualys returns a lifecycle date in neither `UNIX_MS` nor `ISO8601`. This drives a real, user-visible error rate (~9.7% overall on this integration).
Contributor guide
Research direction
Locate the `nozomi_networks` and `qualys_gav` integration pipeline definitions, then inspect `grok_nozomi_networks_audit_username` and the `date_qualys_gav_asset_*_lifecycle_*_date` processors. Reproduce the documented audit and lifecycle-date inputs, and verify that user fields are populated for Nozomi documents and unsupported Qualys date formats no longer produce `pipeline_error`.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- handlebars
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100