We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If you add a field in the prospector section of filebeat configuration
fields: widget_number: 10
This will be added to each document as:
"widget_number":"10"
but it would be better if numbers were not cast as string, and would remain:
"widget_number":10
The text was updated successfully, but these errors were encountered:
+1
Sorry, something went wrong.
I assigned the libbeat label here as this would be a general improvement to the way fields are handled.
This is the behavior in v5. Changed in #1092
From the 5.0 changelog:
Scalar values in used in the fields configuration setting are no longer automatically converted to strings. {pull}1092[1092]
fields
No branches or pull requests
If you add a field in the prospector section of filebeat configuration
This will be added to each document as:
but it would be better if numbers were not cast as string, and would remain:
The text was updated successfully, but these errors were encountered: