Rename dataset to avoid ambiguous index pattern generation#4669
Rename dataset to avoid ambiguous index pattern generation#4669jalvz merged 3 commits intoelastic:masterfrom
Conversation
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Steps errors
Expand to view the steps failures
|
axw
left a comment
There was a problem hiding this comment.
Thanks, I'd forgotten about that one.
Please delete the checklist section in the description.
| title: APM application metrics | ||
| type: metrics | ||
| dataset: apm | ||
| dataset: apm.user |
There was a problem hiding this comment.
| dataset: apm.user | |
| dataset: apm.app |
The title of the stream is "app metrics" after all :)
There was a problem hiding this comment.
ha, I was 50/50 between "app" and "user"
|
This PR fixes the apm issue; we still need to find a more generic answer to the question around how to avoid such conflicts right? |
Codecov Report
@@ Coverage Diff @@
## master #4669 +/- ##
=======================================
Coverage 76.16% 76.16%
=======================================
Files 161 161
Lines 9892 9892
=======================================
Hits 7534 7534
Misses 2358 2358
|
There is no much about it, if one dataset name is prefix of another, it is going to be ambiguous. Maybe it can be validated in the package registry. |


Motivation/summary
Solves the issue described in elastic/kibana#88307 (comment)
While we could maybe find a way out with priority ordering, that would introduce unnecessary complexity.
Happy to replace "user" with something more appropriate if there are better ideas.
How to test these changes
Wait for package 0.5.0 release