-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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.
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
[Ingest Manager] Moved from stream to dataset #18967
[Ingest Manager] Moved from stream to dataset #18967
Conversation
💚 Build SucceededExpand to view the summary
Build stats
Test stats 🧪
Steps errorsExpand to view the steps failures
|
@@ -8,7 +8,7 @@ filebeat: | |||
index: logs-generic-default | |||
processors: | |||
- add_fields: | |||
target: "stream" | |||
target: "dataset" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There a small thing missing here: dataset.dataset
need to be changed for dataset.name
, this will create these fields:
- dataset.type
- dataset.name
- dataset.namespace.
@michalpristas @ruflin The field in the agent configuration will also need to changes? Meaning we will need to adjust the index name generation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in configuration i would expect this
datasources:
- namespace: testing
use_output: default
inputs:
- type: docker/metrics
streams:
- metricset: status
dataset: docker.status
to become this
datasources:
- namespace: testing
use_output: default
inputs:
- type: docker/metrics
datasets:
- metricset: status
name: docker.status
is that correct?
but this feels weird as you can have
datasources:
- namespace: testing
use_output: default
inputs:
- type: docker/metrics
datasets:
- metricset: status
name: docker.status
- metricset: cpu
name: docker.status
i dont recall if we agreed to handle configuration change as a separate pack of PRs or the same with this one @ruflin
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@michalpristas Please handle config changes as a separate PR as it also has effects in Kibana. I plan to open an issue for this. These config changes we should directly in combination with the potential removal of datasources.
Pinging @elastic/ingest-management (Team:Ingest Management) |
@@ -8,7 +8,7 @@ filebeat: | |||
index: logs-generic-default | |||
processors: | |||
- add_fields: | |||
target: "stream" | |||
target: "dataset" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested this and it does not work as expected. The result is:
"dataset" : {
"type" : "metrics",
"dataset" : "system.cpu",
"namespace" : "default"
},
But it should be
"dataset" : {
"type" : "metrics",
"name" : "system.cpu",
"namespace" : "default"
},
I think the reason is on line 14 where it still states dataset
instead of name
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh right
@michalpristas I pushed a fix with the requested change above. Lets see what CI thinks. |
@michalpristas Seems like this does not apply yet to agent monitoring data. Where needs this change to happen? |
I filed #19070 as a follow up as it is really hard to validate these changes without manual testing. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested locally with elastic/kibana#68322 and works as expected.
[Ingest Manager] Moved from stream to dataset (elastic#18967)
[Ingest Manager] Moved from stream to dataset (elastic#18967)
What does this PR do?
Changes injected processor to events so it enriches them with dataset.* instead of stream.*
Why is it important?
elastic/package-registry#491
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.As draft until we are ready and in sync to merge
Fixes: elastic/package-registry#491
Fixes: #18826
cc @ruflin