Previously -
The previous one had Bad Request displayed seperately as it had a space.
Now-
Is there a better way to generate chart with http status codes which has/not has spaces?
Previously -
Now-
Is there a better way to generate chart with http status codes which has/not has spaces?
The reason your status text is getting split on words is because the field value is "analyzed" to make it more searchable. If you store a non-analyzed version of the text it won't be split into individual tokens, but the entire value will be treated as a single token.
This is done automatically when you use logstash, it created .raw
versions of all string fields which stored the original non-analyzed version, so you will regularly see examples with status_text.raw
so that Not Found
is not treated as the two terms Not
and Found
Currently, I don't have *.raw fields. Is there any other way to implement it ?
I'm afraid not
© 2020. All Rights Reserved - Elasticsearch
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.