Mutate converts integer to string

[cawoodm (Marc)]

We have the following filter (Logstash 6.2 Windows):

if [category] == "hybrisserver" and [raw] =~ "Starting up hybris server" {
	mutate { update => {"priority" => 2 "category" => "ServerStart" } }
}

The incoming events have priority as an integer (see 2nd event in screenshot below) but after mutate it's a string:

[Badger]

@cawoodm

The incoming events have priority as an integer [...] but after mutate it's a string

This is true. Update replaces the current value of a field with a string. You could convert the field if you need it to be an integer.

[cawoodm (Marc)]

Are you stating the obvious or saying this is by design?

IMHO it's a bug.

[cawoodm (Marc)]

Just to be clear: "priority" is not really in the input. It's created via the following filter:

translate {
	field => "type"
	destination => "priority"
	dictionary => {
		"ERROR" => 3
		"WARN" => 2
		"INFO" => 1
		"DEBUG" => 0
	}
}

[magnusbaeck (Magnus Bäck)]

IMHO it's a bug.

I agree. Logstash's configuration language doesn't have integer literals, and quotes are optional for strings so 2 is treated as "2".