[gcp] Fix ingest pipeline to parse cluster notifications in audit data stream#17830
Open
brijesh-elastic wants to merge 2 commits intoelastic:mainfrom
Open
[gcp] Fix ingest pipeline to parse cluster notifications in audit data stream#17830brijesh-elastic wants to merge 2 commits intoelastic:mainfrom
brijesh-elastic wants to merge 2 commits intoelastic:mainfrom
Conversation
brijesh-elastic
added
documentation
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
Contributor
✅ Vale Linting ResultsNo 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. |
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
|
andrewkroh
added
Team:obs-ds-hosted-services
kcreddy
reviewed
Mar 16, 2026
Comment on lines
+5
to
+7
| "input": { | ||
| "type": "gcp-pubsub" | ||
| }, |
Contributor
There was a problem hiding this comment.
input.type comes from agent. we can omit this inside pipeline tests raw event.
| | gcp.audit.logentry_operation.producer | Optional. An arbitrary producer identifier. The combination of id and producer must be globally unique. | keyword | | ||
| | gcp.audit.metadata | Service-specific data about the request, response, and other information associated with the current audited event. | flattened | | ||
| | gcp.audit.method_name | The name of the service method or operation. For API calls, this should be the name of the API method. For example, 'google.datastore.v1.Datastore.RunQuery'. | keyword | | ||
| | gcp.audit.notification | | keyword | |
Contributor
There was a problem hiding this comment.
Can you add field description?
Comment on lines
+4
to
+5
| - description: Fix ingest pipeline to parse cluster notifications in audit data stream. | ||
| type: bugfix |
Contributor
There was a problem hiding this comment.
I think this should be an enhancement. Let me know what you think.
kcreddy
reviewed
Mar 16, 2026
Comment on lines
+24
to
+31
| "cluster_location": "us-central1-a", | ||
| "cluster_name": "test-qa", | ||
| "payload": { | ||
| "currentVersion": "1.33.5-gke.2228001", | ||
| "operation": "operation-1234567890", | ||
| "resource": "projects/elastic-test/locations/us-central1-a/clusters/test-qa/nodePools/test-custom", | ||
| "resourceType": "NODE_POOL", | ||
| "targetVersion": "1.33.5-gke.2326000" |
| "resourceType": "NODE_POOL", | ||
| "targetVersion": "1.33.5-gke.2326000" | ||
| }, | ||
| "project_id": "elastic-test", |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed commit message
Checklist
changelog.ymlfile.How to test this PR locally
Related issues