Configuring Functionbeat for GCP, where it creates a Cloud Function successfully for both pubhub and storage types of deployments, yet, no index pattern was being created within Kibana, only the Indice that gets created when running ./functionbeat setup

Speaking with Noémi, she believed the reason no index pattern was seen is due to there not being anything ingested from the function to ES. There are no errors upon setting up Functionbeat from the CentOS VM I am using to deploy the function, etc.

Looking into the Cloud Function logs, we can see the following:

{ "textPayload": "Exiting: error loading config file: open functionbeat.yml: no such file or directory", "insertId": "000000-f61bea65-d244-4bea-9e5a-00236c9fe657", "resource": { "type": "cloud_function", "labels": { "project_id": "elastic-product", "region": "us-central1", "function_name": "ams-pubsub" } }, "timestamp": "2020-08-31T14:20:09.461Z", "labels": { "execution_id": "2sdipwlzcweo" }, "logName": "projects/elastic-product/logs/cloudfunctions.googleapis.com%2Fcloud-functions", "trace": "projects/elastic-product/traces/22edc748fa0432a3e6329984aaf6a77d", "receiveTimestamp": "2020-08-31T14:20:10.029070476Z" }

I have also attached the functionbeat.yml file used when running the following command:

./functionbeat -v -e -d "*" deploy ams-pubsub

`
functionbeat-yaml-config-file.txt

`

Please include configurations and logs if available.

For confirmed bugs, please report:

• Version: 7.8.1 of Functionbeat as well as ES Cloud deployment
• Operating System: n/a but deployed on CentOS-6.1
• Discuss Forum URL: n/a discussed with N
• Steps to Reproduce: