-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Dataset quality] 🐞 Dataset is not marked as part of the integration #181542
Labels
bug
Fixes for quality problems that affect the customer experience
Feature:Dataset Health
Team:obs-ux-logs
Observability Logs User Experience Team
Comments
yngrdyn
added
bug
Fixes for quality problems that affect the customer experience
Team:obs-ux-logs
Observability Logs User Experience Team
Feature:Dataset Health
labels
Apr 24, 2024
Pinging @elastic/obs-ux-logs-team (Team:obs-ux-logs) |
yngrdyn
changed the title
[Dataset quality] Dataset is not marked as part of the integration
[Dataset quality] 🐞 Dataset is not marked as part of the integration
Apr 24, 2024
This is a tricky one. I would love to hear what your plans are for this. |
@weltenwort I'm planning to use the metadata in |
Interesting, I wasn't aware that these metadata exist. Thanks for the explanation! |
yngrdyn
added a commit
that referenced
this issue
Apr 29, 2024
…rt of the integration (#181836) Closes #181542 ## 📝 Summary This PR uses`IndicesDataStream` metadata info to determine whether a non-default dataset belongs to an integration or not ## 🎥 Demo ### Before changes https://github.com/elastic/kibana/assets/1313018/23fbbb9d-ae52-4e30-b525-8176f89d6462 ### After changes https://github.com/elastic/kibana/assets/1313018/5423dba2-fbcf-47b4-87b7-2987f5a1f6d2 --------- Co-authored-by: mohamedhamed-ahmed <[email protected]>
yngrdyn
added a commit
that referenced
this issue
Apr 30, 2024
…rt of the integration (#182097) Closes #181542 ## 📝 Summary This PR uses`IndicesDataStream` metadata info to determine whether a non-default dataset belongs to an integration or not ## 🎥 Demo ### Before changes https://github.com/elastic/kibana/assets/1313018/23fbbb9d-ae52-4e30-b525-8176f89d6462 ### After changes https://github.com/elastic/kibana/assets/1313018/5423dba2-fbcf-47b4-87b7-2987f5a1f6d2 --------- Co-authored-by: mohamedhamed-ahmed <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Fixes for quality problems that affect the customer experience
Feature:Dataset Health
Team:obs-ux-logs
Observability Logs User Experience Team
In #180560 we separated the integrations request from the DataStreamStats one, as part of the separation we are discovering datasets from integrations directly, the problem with this comes with datasets that are not the default/original ones for example these ones in APM
They should be marked as part of APM integration.
The text was updated successfully, but these errors were encountered: