I’m trying to create a pipeline rule to split a message containing comma seperated lines into individual fields. The first 3 fields are strings and work fine. The remaining three fields are converted to numbers, but always have zero as the value. Help please! Pipeline Rule: rule “Split Disk Poo…

Pipeline Rule - converted numbers changed to zeros

jan (Jan Doberstein) February 8, 2019, 8:45am 2

remove the number conversion in the processing pipelines. That does not make sense!

Because the type in the processing pipeline does not have any influence how the data is stored in Elasticsearch.

Topic		Replies	Views
Pipeline help convert field numeric field Graylog Central (peer support) pipeline-rules	3	3634	July 7, 2020
Changing a field type from string to numeric and mid-setup and past string values Graylog Central (peer support) pipeline-rules , debuggingpl	10	17295	December 13, 2017
Pipeline rules are not converting field datatypes, even though message throughput is > 0 with 0 errors Graylog Central (peer support) pipeline-rules	10	210	March 9, 2024
Pipeline Rules and when condition: string v. integer Graylog Central (peer support) pipeline-rules	5	1508	October 9, 2021
Pipeline Rule with unexpected result Graylog Central (peer support) pipeline-rules	4	1280	November 23, 2018