Skip to content

[wiz] Add Troubleshooting Note in Readme #14546

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 21, 2025
Merged

[wiz] Add Troubleshooting Note in Readme #14546

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8b3f754
Add troubleshooting note in readme
mohitjha-elastic Jul 15, 2025
21d8a18
Update changelog entry
mohitjha-elastic Jul 15, 2025
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
11 changes: 11 additions & 0 deletions packages/wiz/_dev/build/docs/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -98,6 +98,17 @@ Agentless deployments are only supported in Elastic Serverless and Elastic Cloud
- Vulnerability data is fetched for the previous day.
- Custom headers are not supported in this integration. Only the standard Authorization header (for example, Bearer token) is used for API requests.

### Troubleshooting

The transforms used in the Wiz integration depend on the presence of the `event.ingested` field to function correctly.

When using Fleet-managed Elastic Agents, the `.fleet_final_pipeline-1` is automatically executed and ensures that the `event.ingested` field is added to all events.

However, when using standalone Elastic Agents, this pipeline is not applied, and the `event.ingested` field is not automatically added.

📌 Action Required (for standalone agents):
You must manually add the `event.ingested` field, preferably via a custom ingest pipeline (e.g., using the @custom pipeline).

## Logs reference

### Audit
Expand Down
5 changes: 5 additions & 0 deletions packages/wiz/changelog.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,9 @@
# newer versions go on top
- version: "3.6.0"
changes:
- description: Add troubleshooting note in README on `event.ingested` requirement for standalone Elastic Agent.
type: enhancement
link: https://github.com/elastic/integrations/pull/14546
- version: "3.5.1"
changes:
- description: Update texts for the input fields helpers.
Expand Down
11 changes: 11 additions & 0 deletions packages/wiz/docs/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -98,6 +98,17 @@ Agentless deployments are only supported in Elastic Serverless and Elastic Cloud
- Vulnerability data is fetched for the previous day.
- Custom headers are not supported in this integration. Only the standard Authorization header (for example, Bearer token) is used for API requests.

### Troubleshooting

The transforms used in the Wiz integration depend on the presence of the `event.ingested` field to function correctly.

When using Fleet-managed Elastic Agents, the `.fleet_final_pipeline-1` is automatically executed and ensures that the `event.ingested` field is added to all events.

However, when using standalone Elastic Agents, this pipeline is not applied, and the `event.ingested` field is not automatically added.

📌 Action Required (for standalone agents):
You must manually add the `event.ingested` field, preferably via a custom ingest pipeline (e.g., using the @custom pipeline).

## Logs reference

### Audit
Expand Down
2 changes: 1 addition & 1 deletion packages/wiz/manifest.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
format_version: 3.4.0
name: wiz
title: Wiz
version: "3.5.1"
version: "3.6.0"
description: Collect logs from Wiz with Elastic Agent.
type: integration
categories:
Expand Down