# Filebeat Context Error

**URL:** https://discuss.elastic.co/t/filebeat-context-error/348366
**Category:** Elasticsearch
**Created:** [November 30, 2023, 8:41pm UTC](https://discuss.elastic.co/t/filebeat-context-error/348366 "2023-11-30T20:41:57Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![bigdaddy0918](https://avatars.discourse-cdn.com/v4/letter/b/c6cbf5/32.png) [@bigdaddy0918](https://discuss.elastic.co/u/bigdaddy0918)
#### Post date: [November 30, 2023, 8:41pm UTC](https://discuss.elastic.co/t/filebeat-context-error/348366/1 "2023-11-30T20:41:57Z")

</div>

I was able to push a new CEL input to Filebeat v8.7.1 via puppet. When we launch filebeat v.8.7.1 I see this message pop up in the log:

`{"log.level":"info","@timestamp":"2023-11-30T19:59:28.167Z","log.logger":"input.cel","log.origin":{"file.name":"cel/input.go","file.line":446},"message":"input stopped because context was cancelled with: context canceled","service.name":"filebeat","id":"6875877FA9FF2178","input_source":"/data/master/gpseg-1/pg_hba.conf","input_url":"/data/master/gpseg-1/pg_hba.conf","ecs.version":"1.6.0"}`

Filebeat does not seem to recognize when my source file changes to send a record to my Elastic cluster.

How do I resolve this?

Marty Pacocha

---

<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: [December 28, 2023, 8:42pm UTC](https://discuss.elastic.co/t/filebeat-context-error/348366/2 "2023-12-28T20:42:45Z")

</div>

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