I have just upgraded to 4.2 and am having issues with rangemap. The below snippet worked fine in 4.1 and returned low,elevated or severe based on the input value, however no matter what value is in count for v4.2 I am always getting severe.
Am I missing something, do I need to rewrite something in 4.2 to get rangemaps to work ?
... | table count | rangemap field="count" low=0-5 elevated=6-20 default=severe
I had a look at the documentation and couldn't see anything listed in there for 4.2, anyone else having this issue ?
Take the quotes off the field name. It worked fine for me, then I added quotes around the field name and it messed up.
The workaround is pretty simple, but you might want to consider filing a bug, as this workaround fails if your field name, e.g., has spaces in it.
Take the quotes off the field name. It worked fine for me, then I added quotes around the field name and it messed up.
The workaround is pretty simple, but you might want to consider filing a bug, as this workaround fails if your field name, e.g., has spaces in it.
Thanks, sorted the issue and all queries working again.
As a test I also tried the following search query, this time it is always returning gray instead of severe for all values.
... | table count | rangemap field="count" green=0-5 blue=6-20 red=21-59 default=gray