Support non-string labels
See original GitHub issueAPM has support for that but in ECS, labels are mapped as keyword
@pgomulka would you need non-string MapMessage
values for Elasticsearch?
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Add support for non-string labels · Issue #444 - GitHub
Hello, I haven't found a way to use one representation for x-axis labels and another representation in tooltips.
Read more >How to handle label names for requests that don't have ...
But the solution is to pass the label values as empty strings or with a hyphen placeholder like Brian Candler suggests. Prometheus will...
Read more >Labels - Go Packages
MatchLabels returns a subset of Labels that matches/does not match with the provided label names based on the 'on' boolean.
Read more >Metric and label naming - Prometheus.io
Do not put the label names in the metric name, as this introduces redundancy and will cause confusion if the respective labels are...
Read more >Log queries | Grafana Loki documentation
The following label matching operators are supported: ... Log line does not contain string; |~ : Log line contains a match to the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
That works with this change: https://github.com/elastic/java-ecs-logging/pull/30
MapMessage
supports rendering the message asJSON
which EcsLayout is now delegating the rendering to. So you could either useMapMessage
, which would render the plain text message slightly differently (key="value"
). Or you could create your own class which implementsMultiformatMessage
(or betterMultiFormatStringBuilderFormattable
) and which supports aJSON
and a plain-text format.there are some fields that are non string but I format them as strings anyway so that is fine