# Functionbeat missing package io/fs

**URL:** <https://discuss.elastic.co/t/functionbeat-missing-package-io-fs/284975>\
**Category:** Beats\
**Tags:** functionbeat\
**Created:** [September 23, 2021, 9:18am UTC](https://discuss.elastic.co/t/functionbeat-missing-package-io-fs/284975 "2021-09-23T09:18:56Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![Edoardo\_Tenani](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/edoardo_tenani/32/94302_2.png) [@Edoardo\_Tenani](https://discuss.elastic.co/u/Edoardo_Tenani)\
**Post date:** [October 5, 2021, 1:13pm UTC](https://discuss.elastic.co/t/functionbeat-missing-package-io-fs/284975/10 "2021-10-05T13:13:32Z")

</div>

I have good news! There is an [open pr](https://github.com/elastic/beats/pull/28251) (thanks @kvch!) to proper update functionbeat to go 1.16.

There is another solution we announced recently that could bypass `functionbeat` altogether, that is using GCP Dataflow to forward logs to Elasticsearch. You can read more in [this announcement blog post](https://www.elastic.co/blog/ingest-data-directly-from-google-pub-sub-into-elastic-using-google-dataflow). With it you can route logs to GCP Pub/Sub and then forward them to your public routable Elasticsearch cluster with a GCP Dataflow Job.  
I worked on a [Terraform based example for GCP Audit logs](https://github.com/elastic/examples/pull/381), you may want to check that out too.

---

_[View the full topic](https://discuss.elastic.co/t/functionbeat-missing-package-io-fs/284975)._
