Organization ID / user IDs: https://cloud.elastic.co/account/members
Billing api key: https://cloud.elastic.co/account/keys
Api_key:
This API key is used to read from the monitoring cluster; it requires read privileges to the .monitoring-es-8* index names.
API KEY - consumption_destination
API KEY - monitoring_source
In the monitoring_source cluster, the script will be reading the .monitoring-es-8* indices. The user (or API key) used to connect to the cluster will therefore need to have the corresponding read permission. The below API call can be used to provision the required API key on the monitoring_source cluster:
In the kibana_exports folder of the ZIP archive, there are .ndjson files for Kibana; these are saved objects intended for upload.
In Kibana, go to Stack Management -> Saved Objects and click Import (upper right, as of 8.12.1). Next, select Import again and then choose the .ndjson file (e.g. 8.11.2.ndjson) from your local filesystem. Click Done to close the sidebar window.
Using virtual environment
To delete the env
deactivate
andrm -r ./venv
Next, import initial Elasticsearch Service / Elastic Cloud billing data: get-billing-data
will recover the billing data from ESS, and index it into the target cluster. This will populate the organization overview dashboard.
Finally, pull initial cluster usage data from the Monitoring Cluster:
Review the config.yml