# ELK-functionbeat-not-able-to-push-data

**URL:** <https://discuss.elastic.co/t/elk-functionbeat-not-able-to-push-data/311662>\
**Category:** Beats\
**Tags:** functionbeat\
**Created:** [August 8, 2022, 5:17pm UTC](https://discuss.elastic.co/t/elk-functionbeat-not-able-to-push-data/311662 "2022-08-08T17:17:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vijay23vikram](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vijay23vikram/32/105984_2.png) [@vijay23vikram](https://discuss.elastic.co/u/vijay23vikram)\
**Post date:** [August 8, 2022, 5:17pm UTC](https://discuss.elastic.co/t/elk-functionbeat-not-able-to-push-data/311662/1 "2022-08-08T17:17:46Z")

</div>

Hello Team,

We are facing the below error in AWS function beat lambda.  
Cannot index event publisher.Event{Content:beat.Event  
More error details as below:  
Error:  
2022-07-22T15:15:01.087Z WARN [elasticsearch] elasticsearch/client.go:408 Cannot index event publisher.Event{Content:beat.Event  
{Timestamp:time.Time{wall:0xf424000, ext:6379400000, loc:(\*time.Location)(0x45414e0)}, Meta:null, Fields:{"agent":  
{"ephemeral\_id":"6afb6acd-2196-49cc-bfa6-762b203a5037","hostname":"169.254.129.10","id":"02286e5a-6229-4a8b-92b0-8c9577eec5d8","name":"169.254.129.10",  
"type":"functionbeat","version":"7.10.1"},"asctime":"2022-07-22T15:14:49+0000","cloud":{"provider":"aws"},"ecs":{"version":"1.6.0"},  
"event":{"kind":"event"},"host":{"architecture":"x86\_64","containerized":true,"hostname":"169.254.129.10","ip":["169.254.xx.x","169.254.xx.x"],"  
mac":["06:f3:df:c1:44:6c","7e:74:63:86:f1:fa"],"name":"169.254.129.10","os":{"family":"redhat","kernel":"4.14.255-276-224.499.amzn2.x86\_64",  
"name":"Amazon Linux AMI","platform":"amzn","version":"2018.03"}},"id":"369858",  
"levelname":"INFO","lineno":76,"log\_group":"/aws/lambda/test-lambda-dev-us-east-1","log\_stream":"2022/07/22/[$LATEST]d49617204e0f4035acdea",  
"message":"Quote None error response from legacy: POST HTTPSConnectionPool(host='[api.test.test.io](http://api.test.test.io)', port=443): Max retries exceeded with url:  
/legacy/offers (Caused by NewConnectionError('\u003curllib3.connection.HTTPSConnection object at 0x7f95962e5a90\u003e:  
Failed to establish a new connection: [Errno -2] Name or service not known'))","message\_type":"DATA\_MESSAGE",  
"name":"root","owner":"94517143256","process":8,"subscription\_filters":  
["fnb-test-lambda-dev-functionbeat-stack-fnbtestlambdadevuseast1-4KPHULZEP7B1"],  
"traceId":"olesiarequest"}, Private:interface {}(nil), TimeSeries:false}, Flags:0x1, Cache:publisher.EventCache{m:common.MapStr(nil)}} (status=400):

{  
"type": "mapper\_parsing\_exception",  
"reason": "object mapping for [process] tried to parse field [process] as object, but found a concrete value"  
}

Please Suggest any leads on this.

Thanks in Advance,

---

<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:** [September 5, 2022, 5:18pm UTC](https://discuss.elastic.co/t/elk-functionbeat-not-able-to-push-data/311662/2 "2022-09-05T17:18:45Z")

</div>

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