-
Notifications
You must be signed in to change notification settings - Fork 479
Description
Integration Name
Snyk [snyk]
Dataset Name
snyk.issues
Integration Version
2.0.0
Agent Version
9.0.1
Agent Output Type
elasticsearch
Elasticsearch Version
9.0.1
OS Version and Architecture
Docker image (elastic-package)
Software/API Version
Snyk SaaS
Error Message
No error message
Event Original
No event original
What did you do?
I ingested Snyk issues into the stack. Based on the way the fingerprint is set up, there should be
What did you see?
integrations/packages/snyk/data_stream/issues/elasticsearch/ingest_pipeline/default.yml
Lines 28 to 31 in 7d3232e
- fingerprint: | |
fields: | |
- snyk.issues.id | |
target_field: _id |
What did you expect to see?
Add a field (like the vulnerability status) as part of the fingerprint. We should probably add snyk.issues.attributes.status
and snyk.issues.attributes.ignored
.
Anything else?
This was never tested/confirmed. It's based of my analysis of the integration and a review from @SpencerLN and @christophercutajar. As the GitHub Secret Scanning contains multiple fields, it confirms our analysis.
integrations/packages/github/data_stream/secret_scanning/elasticsearch/ingest_pipeline/default.yml
Lines 31 to 37 in 7d3232e
- fingerprint: | |
fields: | |
- github.secret_scanning.number | |
- github.secret_scanning.updated_at | |
- github.secret_scanning.resolved_at | |
target_field: "_id" | |
ignore_missing: true |