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
Just noticed port numbers in the json document exported by heartbeat are string, not numbers. See sample output from event refactoring: #4091
The fields.yml file already configures the port number to be an integer.
The text was updated successfully, but these errors were encountered:
I just tested this on master and it seems to be integer there now. Must be a change between 5.x and 6.x where we fixed this?
The initial thread where this popped up: https://discuss.elastic.co/t/what-type-is-the-port-field-in-heartbeat-output/108586/11
Sorry, something went wrong.
Pinging @elastic/uptime
Given that it's fixed in 6.x I'm going to close this since 5.x isn't supported.
No branches or pull requests
Just noticed port numbers in the json document exported by heartbeat are string, not numbers. See sample output from event refactoring: #4091
The fields.yml file already configures the port number to be an integer.
The text was updated successfully, but these errors were encountered: