You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Google Cloud client libraries use a strategy called Application Default Credentials (ADC) to find your application's credentials. When your code uses a client library, the strategy checks for your credentials in the following order:
First, ADC checks to see if the environment variable GOOGLE_APPLICATION_CREDENTIALS is set. If the variable is set, ADC uses the service account file that the variable points to.
If the environment variable isn't set, ADC uses the default service account that Compute Engine, Google Kubernetes Engine, Cloud Run, App Engine, and Cloud Functions provide, for applications that run on those services.
If ADC can't use either of the above credentials, an error occurs.
This issue is to track the work of adding ADC support into Metricbeat, similar to what #15668 is done for Filebeat.
Note: also needs to consider if there's enough code between Filebeat/Metricbeat around credentials to move to x-pack/libbeat/common directory.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Google Cloud client libraries use a strategy called Application Default Credentials (ADC) to find your application's credentials. When your code uses a client library, the strategy checks for your credentials in the following order:
This issue is to track the work of adding ADC support into Metricbeat, similar to what #15668 is done for Filebeat.
Note: also needs to consider if there's enough code between Filebeat/Metricbeat around credentials to move to
x-pack/libbeat/common
directory.The text was updated successfully, but these errors were encountered: