A custom script produces a json message and is logged into my new Graylog instance, but its numeric fields are being interpreted as String and are therefore treated and stored as String. Consequently, I cannot Chart against these values. Ex. Message: {"level": "6", "details": {"memorypercent": "0…

Ok pipeline field rewrite rule is not necessary in my case, because indeed Graylog/Elasticsearch does treat a numeric json value as numeric on store, provided the original value seen is numeric to begin with, and I can do numeric operations on them like Generate Chart. I’ll have to rewrite all my j…

Changing a field type from string to numeric and mid-setup and past string values

Graylog Central (peer support)

jan (Jan Doberstein) Split this topic November 29, 2017, 1:36pm 10

A post was split to a new topic: Change elasticsearch field mappings cause error in query

Topic		Replies	Views
Problem with numeric field created by JSON extractor Graylog Central (peer support)	5	2500	July 5, 2017
Forcing numeric fields Graylog Central (peer support)	7	7481	May 4, 2017
Unexpected behavior for handling numeric field Graylog Central (peer support)	6	469	February 4, 2019
Pipeline Rule - converted numbers changed to zeros Graylog Central (peer support) pipeline-rules , debuggingpl , sidecar , nxlog , nodatanx	25	3428	September 7, 2023
Pipeline help convert field numeric field Graylog Central (peer support) pipeline-rules	3	3659	July 7, 2020

Changing a field type from string to numeric and mid-setup and past string values

Related topics