Hey, has anyone configured metricbeat on a system with a AWS EFS share mounted? Because AWS shows that the volume has 9223372036854775808 bytes (8 Exabytes) free, I'm getting warnings like below showing up in the log.
2017-02-21T19:28:32Z WARN Can not index event (status=400): {"type":"mapper_parsing_exception","reason":"failed to parse [system.filesystem.total]","caused_by":{"type":"json_parse_exception","reason":"Numeric value (9223372036854775808) out of range of long (-9223372036854775808 - 9223372036854775807)\n at [Source: org.elasticsearch.common.bytes.BytesReference$MarkSupportingStreamInputWrapper@6e55ae3; line: 1, column: 398]"}}
2017-02-21T19:28:32Z WARN Can not index event (status=400): {"type":"mapper_parsing_exception","reason":"failed to parse [system.fsstat.total_size.free]","caused_by":{"type":"json_parse_exception","reason":"Numeric value (9223372051157159936) out of range of long (-9223372036854775808 - 9223372036854775807)\n at [Source: org.elasticsearch.common.bytes.BytesReference$MarkSupportingStreamInputWrapper@21e3b3e8; line: 1, column: 269]"}}
The relevant subsection of the config is:
metricbeat.modules:
- module: system
metricsets:
- filesystem
- fsstat
enabled: true
period: 30s
It is possible to use filtering to exclude events from the filesystem
metricset, but the fsstat
produces aggregate values, so will include the EFS mount regardless.
Steps to reproduce:
- Instantiate a linux box in AWS
- Create an AWS EFS share
- Mount the EFS share on the linux box
- Start Metricbeat, watch the logs
Any suggestions on how to handle situations where a system might have more that 2^63 bytes of storage available?
—Joey