# Metricbeat with AWS EFS **URL:** \ **Category:** Beats\ **Created:** [February 21, 2017, 8:01pm UTC](https://discuss.elastic.co/t/metricbeat-with-aws-efs/75950 "2017-02-21T20:01:41Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Joey\_Coleman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joey_coleman/32/15758_2.png) [@Joey\_Coleman](https://discuss.elastic.co/u/Joey_Coleman)\ **Post date:** [February 21, 2017, 8:01pm UTC](https://discuss.elastic.co/t/metricbeat-with-aws-efs/75950/1 "2017-02-21T20:01:41Z")
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. ```nohighlight 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: ```nohighlight 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: 1. Instantiate a linux box in AWS 2. Create an AWS EFS share 3. Mount the EFS share on the linux box 4. 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 ---
**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\ **Post date:** [February 22, 2017, 1:40am UTC](https://discuss.elastic.co/t/metricbeat-with-aws-efs/75950/2 "2017-02-22T01:40:29Z")
I'm curious what `stat -f` and `df` show for that EFS volume? This is kind of similar to [Failed to parse [system.filesystem.files]: Numeric value (18446744073709551615) out of range of long](https://discuss.elastic.co/t/failed-to-parse-system-filesystem-files-numeric-value-18446744073709551615-out-of-range-of-long/66860) but in this case it's for a huge filesystem instead of a invalid value. So I think we need to come up with some way to handle this. ---
**Author:** ![Joey\_Coleman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joey_coleman/32/15758_2.png) [@Joey\_Coleman](https://discuss.elastic.co/u/Joey_Coleman)\ **Post date:** [February 22, 2017, 1:56am UTC](https://discuss.elastic.co/t/metricbeat-with-aws-efs/75950/3 "2017-02-22T01:56:24Z")
Easy to produce. From `stat` you can see that AWS provides exactly 2^63 bytes of storage (2^43 1MB blocks). ```auto $ df /mnt/efs Filesystem 1K-blocks Used Available Use% Mounted on fs-xxxxxxxx.efs.us-east-1.amazonaws.com:/ 9007199254740992 19168256 9007199235572736 1% /mnt/efs $ df -h /mnt/efs Filesystem Size Used Avail Use% Mounted on fs-xxxxxxxx.efs.us-east-1.amazonaws.com:/ 8.0E 19G 8.0E 1% /mnt/efs $ stat -f /mnt/efs File: "/mnt/efs" ID: 0 Namelen: 255 Type: nfs Block size: 1048576 Fundamental block size: 1048576 Blocks: Total: 8796093022208 Free: 8796093003489 Available: 8796093003489 Inodes: Total: 0 Free: 0 ``` ---
**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\ **Post date:** [February 28, 2017, 12:04am UTC](https://discuss.elastic.co/t/metricbeat-with-aws-efs/75950/4 "2017-02-28T00:04:26Z")
@Joey_Coleman Would you mind opening a bug report on [Github](https://github.com/elastic/beats/issues/new) for this so we don't lose track of it? ---
**Author:** ![Joey\_Coleman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joey_coleman/32/15758_2.png) [@Joey\_Coleman](https://discuss.elastic.co/u/Joey_Coleman)\ **Post date:** [February 28, 2017, 1:22am UTC](https://discuss.elastic.co/t/metricbeat-with-aws-efs/75950/5 "2017-02-28T01:22:34Z")
Happy to — didn't initially as the guidelines suggested posting on the boards first ---
**Author:** ![Joey\_Coleman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joey_coleman/32/15758_2.png) [@Joey\_Coleman](https://discuss.elastic.co/u/Joey_Coleman)\ **Post date:** [February 28, 2017, 1:32am UTC](https://discuss.elastic.co/t/metricbeat-with-aws-efs/75950/6 "2017-02-28T01:32:17Z")
Opened as [https://github.com/elastic/beats/issues/3687](https://github.com/elastic/beats/issues/3687) ---
**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\ **Post date:** [February 28, 2017, 7:31am UTC](https://discuss.elastic.co/t/metricbeat-with-aws-efs/75950/7 "2017-02-28T07:31:19Z")
Thanks @Joey_Coleman. We really appreciate you posted it first here for discussions. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 14, 2017, 8:01pm UTC](https://discuss.elastic.co/t/metricbeat-with-aws-efs/75950/8 "2017-03-14T20:01:44Z")
This topic was automatically closed after 21 days. New replies are no longer allowed.