-
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
[Maps] observability real user monitoring solution layer #64949
Conversation
Pinging @elastic/kibana-gis (Team:Geo) |
Pinging @elastic/apm-ui (Team:apm) |
done
Added |
done |
done |
@elasticmachine merge upstream |
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.
lgtm for Maps-code. Add-layer flow works really well, and good concept to start using for other "curated layers".
Main feedback is on the actual data-display side.
Use proper formatting of values
RUM Performance > SLA Percentage layer.
Format the % fields as actual percentages / trim decimal places
When these percentage values are shown as decimals, it looks funny on the map and the legend.
e.g.: This is how duration_sla_pct
field formatter would look like
Map-formatting looks "better" imho.
Rum Performance > Transaction Duration layer.
This would format ms
properly
@sqren : Is it possible to specify these formatters in the APM index pattern? The Maps-application will automatically pick these up to display values/format legends/tooltips etc...
Use custom ramps
It seems the performance-metrics are diverging. Presumably, a decrease is "better" (smaller than 0), and an increase is worse (larger than 0) (??) . Ideally, can we center the ramp at value 0
then. This would require a custom ramp iso using an out-of-the-box one.
@sqren Can you confirm if this is the case? Are the metrics for "transaction duration" and "SLA percentage" diverging? (either below or above 0.0
)?
cc @alexfrancoeur Are the above suggestions required?
I think so - but since the APM app doesn't use index patterns I'm not the most knowledgable about this. |
Seems like this would be the place to add a field-formatter to the
Would this impact any of the existing code @graphaelli (?) |
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
That thing is auto-generated, so adding anything there would be overwritten next time apm-server updates the index pattern. |
Tangent: This shows why index pattern in the current form is such a bad fit. Having somewhere (like index patterns) to store field formatters only relevant to the UI, and having that live in Kibana, is a good idea. But persisting the field mappings in a secondary location (away from the actual mappings) is a terrible idea. Moving field formatters out of index patterns (or removing mappings from index patterns) would be a huge step forward, and resolve a lot of issues imo. |
@thomasneirynck I agree that a better long term solution be metric specific field formatters. Similar to Lens, Canvas and TSVB. It's a common request that we don't want to rely on global formatters for visualizing data. I'll add as a topic for discussion to our 7.9 planning. It's a feature I've wanted for nearly every map I build, and I know I'm not alone. For this PR, maybe we merge without addressing formatting initially? |
+1 |
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.
+1 maps-side.
There seems to be a little uncertainty about this sla_duration_pct
field, where exactly this comes from. I would change the color-ramp to a custom diverging color-ramp that centers on 0. Depending on whether we get clarification on this field, we could consider this a bug fix and merge after FF. It seems that below 0 would indicate beating "sla", above 0 not meeting the SLA (?)
@thomasneirynck the index pattern is generated in APM Server via some libbeat functionality, and then copied over to Kibana to ensure the bundled index pattern is aligned with the APM Server index templates. The correct place to update any kind of formatting etc would be directly in APM Server, e.g. in the metricsets fields.yml. Do you have a list of fields and formats for which the format should be changed? |
hi @simitt two additions would be useful imho Field: Field: I guess details can be tweaked, but those two fields are used in the solution-layers. It would make the labels on the map and the legend more readable. I can create a separate issue for this as well, if that's easier. Thx! |
I have a suggestion for the text underneath the Format field: Formats allow you to control the display of specific values. Formats can also change the value and turn off highlighting in Discover. If these are just "numeric" values, use that word instead of specific in the first sentence. Also in the second sentence, what does "change the value" mean? Change the value of the data? |
* [Maps] observability real user monitoring solution layer * make stateful component * rename RUM to observability * layer select * metrics select * display select * clean up * create cholopleth map layer descriptor * get styling working * fix unique count agg * create geo grid source * render as heatmap * clusters * tslint errors * last tslint fix * only show card when APM index exists * layer label * clean up * fix getLayerWizards * add parans * review feedback * add cluster labels * use green to red ramp * tslint fix Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
@gchaps Would you mind making an issue for these field formatter text changes? That UI is not a part of this UI. The screen shots where just included to show how @thomasneirynck configured some field formatters. |
…5337) * [Maps] observability real user monitoring solution layer * make stateful component * rename RUM to observability * layer select * metrics select * display select * clean up * create cholopleth map layer descriptor * get styling working * fix unique count agg * create geo grid source * render as heatmap * clusters * tslint errors * last tslint fix * only show card when APM index exists * layer label * clean up * fix getLayerWizards * add parans * review feedback * add cluster labels * use green to red ramp * tslint fix Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Implements part of #64445.
This PR adds
Observability
layer wizard card making it easy to create map layers from Observability data. This PR provides two basic layer types for RUM transactions. Expect a lot more in this space in future PRs.The card is only displayed when APM index pattern is installed. The APM index pattern is automatically installed when opening the APM application with data in
apm-*
index.