Add Wildcard widget #25671
Add Wildcard widget #25671
Conversation
Preview links (active after the
|
estherk15
force-pushed
the
esther/docs-8975-wildcard-widget
branch
from
ac2b405 to
2b6ecb0
Compare
|
|
||
| {{< img src="/dashboards/widgets/wildcard/example_configuration_query.png" alt="Example widget configuration metric query for system.cpu.user grouped by env" style="width:100%;" >}} | ||
|
|
||
| Notice the matching **query1** and **env** fields listed in the Vega-Lite specification and the Data Preview column. |
There was a problem hiding this comment.
It wasn't immediately clear to me what this JSON represents - and the highlighted values are env and example, so I wasn't sure where query1 came in. I think you could probably add a little more signposting around these examples to explain what you're showing the user. Is the point that the visualization starts out broken and then you fix it by reassigning the alias? If this is the case, it's useful to let the user know you're going to show them a broken example before the example appears.
Sidenote: I like the use of tables here.
There was a problem hiding this comment.
Copy paste error 😞 This should be query1. I agree this could be broken down more. I added a new section specifically to map values between Datadog and Vega-Lite, hopefully that makes it clearer!
Co-authored-by: Heston Hoffman <[email protected]>
|
/merge |
|
🚂 MergeQueue: pull request added to the queue The median merge time in Use |
dd-devflow
bot
added
mergequeue-status: queued
mergequeue-status: in_progress
and removed
mergequeue-status: queued
labels
dd-devflow
bot
added
mergequeue-status: done
and removed
mergequeue-status: in_progress
labels
* Add Wildcard widget info * Fixes from code review * Apply suggestions from code review Co-authored-by: Heston Hoffman <[email protected]> * Add more context to map values --------- Co-authored-by: Heston Hoffman <[email protected]>
What does this PR do? What is the motivation?
Merge instructions
Do not merge Pending GA