-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Functionbeat GCP pub/sub requiring storage entry point when only pub/sub is enabled #29967
Comments
I wonder even if I manage to get this to run if I will run into this |
|
Pinging @elastic/integrations (Team:Integrations) |
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
We endeavor to address Functionbeat use cases via the new Serverless Forwarder project (https://github.com/elastic/elastic-serverless-forwarder)with a better integration with serverless functionality provided by major cloud providers. Enhancements to the current Functionbeat will therefore be limited. |
Deploying functionbeat on GCP with entry point
RunPubSub
returns an error complaining about storage entry point, which I am not using.I get the following error upon deploy
The problem is ,as I noticed it, Functionbeat is requiring storage entry point. I am NOT using the gcp storage functionality, I am using pub/sub functionality with
RunPubSub
. Why is it requiring the storage entry point? I am not able to provide multiple entry points to my knowledge.My config file
Including some references:
#24925
#26249
#22495
#28251
#27012
#28253
#25596
https://discuss.elastic.co/t/functionbeat-missing-package-io-fs/284975
GCP/FunctionBeat Errors [cannot find matching process for pid=1, name version already used] · Issue #25596 · elastic/beats · GitHub 1
The text was updated successfully, but these errors were encountered: