# Functionbeat cant send events with warning \[float\] supports only finite values, but got \[Infinity\]

**URL:** https://discuss.elastic.co/t/functionbeat-cant-send-events-with-warning-float-supports-only-finite-values-but-got-infinity/236916
**Category:** Beats
**Tags:** functionbeat
**Created:** [June 12, 2020, 3:43pm UTC](https://discuss.elastic.co/t/functionbeat-cant-send-events-with-warning-float-supports-only-finite-values-but-got-infinity/236916 "2020-06-12T15:43:54Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![thiago.dantas](https://avatars.discourse-cdn.com/v4/letter/t/8797f3/32.png) [@thiago.dantas](https://discuss.elastic.co/u/thiago.dantas)
#### Post date: [June 12, 2020, 3:43pm UTC](https://discuss.elastic.co/t/functionbeat-cant-send-events-with-warning-float-supports-only-finite-values-but-got-infinity/236916/1 "2020-06-12T15:43:54Z")

</div>

A few of our log group subscriptions seem unable to send events to elasticsearch with the following message

> 2020-06-12T15:07:36.434Z WARN elasticsearch/client.go:535 Cannot index event publisher.Event{Content:beat.Event{Timestamp:time.Time{wall:0x13038dc0, ext:63727571250, loc:(_time.Location)(0x3fefa20)}, Meta:common.MapStr(nil), Fields:common.MapStr{"agent":common.MapStr{"ephemeral\_id":"dc3e7bf9-c71a-42df-859e-6100ed746e19", "hostname":"169.254.7.117", "id":"4e8565ce-30ec-4c73-8036-7cbf262c9e5c", "type":"functionbeat", "version":"7.4.2"}, "ecs":common.MapStr{"version":"1.1.0"}, "host":common.MapStr{"name":"169.254.7.117"}, "id":"35502216579134867304159445057927463312451053998037205001", "log\_group":"/aws/lambda/\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*", "log\_stream":"2020/06/12/[$LATEST]c86d8a46ad684057bf45de62e4bfc430", "message":"REPORT RequestId: 6482ad50-eea5-4148-83f8-befac91a47bb\tDuration: 232.55 ms\tBilled Duration: 300 ms\tMemory Size: 256 MB\tMax Memory Used: 152 MB\t\n", "message\_type":"DATA\_MESSAGE", "owner":"83385_\*\*\*\*\*\*", "subscription\_filters":[\*]string{"\*\*\*\*\*\*\*\*\*\*"}}, Private:interface {}(nil), TimeSeries:false}, Flags:0x1} (status=400):  
> {  
> "type": "mapper\_parsing\_exception",  
> "reason": "failed to parse field [id] of type [float] in document with id 'yKASqXIB5DQTaPr7bP8J'. Preview of field's value: '3.550221657913487E55'",  
> "caused\_by": {  
> "type": "illegal\_argument\_exception",  
> "reason": "[float] supports only finite values, but got [Infinity]"  
> }  
> }

The id field is defined by AWS and I don't believe I have control of it's definition.  
While I do believe functionbeat should be able to recover from this, is there anything I can do to avoid this error?

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 10, 2020, 5:43pm UTC](https://discuss.elastic.co/t/functionbeat-cant-send-events-with-warning-float-supports-only-finite-values-but-got-infinity/236916/2 "2020-07-10T17:43:56Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
