Cloud-specific Configuration

The following information is required to setup the cloud-specific configuration to publish the Thunder metrics and logs.

• AWS Config
  (Applicable only if you want to publish the data to AWS CloudWatch)
• AWS Credentials
  (Applicable only if you want to publish the data to AWS CloudWatch)
• Azure Credentials
  (Applicable only if you want to publish the data to Azure Application Insights and Azure Log Analytics Workspace)
• VMware Credentials
  (Applicable only if you want to publish the data to vRealize Operations (vROps))

• Elasticsearch Credentials

  (Applicable only if you want to publish the data to Elasticsearch Kibana)

• PushGateway Credentials

  (Applicable only if you want to publish the data to Prometheus Grafana)

• Splunk Credentials

  (Applicable only if you want to publish the data to Splunk)

• GCP Credentials

  (Applicable only if you want to publish the data to GCP)

• OCI Credentials

  (Applicable only if you want to publish the data to OCI)

AWS Config

This file lists the AWS configurations to publish the Thunder metrics or logs to AWS CloudWatch.

File Path: /root/.aws/config

Update the following parameters according to your AWS setup:

[default]
region = XXXX
output = XXXX

Table 25 : AWS Config File Parameters

Parameter	Description
region	Specifies the AWS logged-in user's working region. Example us-east-1
output	Specify json as the AWS CLI output format.

For sample configuration, see Examples.

AWS Credentials

This file lists the AWS credential configurations to publish the Thunder metrics or logs to AWS CloudWatch.

File Path: /root/.aws/credentials

Update the following parameters according to your AWS setup:

[default]
aws_access_key_id = XXXX
aws_secret_access_key = XXXX

Table 26 : AWS Credentials File Parameters

Parameter	Description
aws_access_key_id	To get the access key ID and secret access key, perform the following steps: Open the IAM console. On the navigation menu, select Users. Select your IAM user name. Open the Security credentials tab, and select Create access key. To view the new access key, select Show.
aws_secret_access_key

For sample configuration, see Examples.

Azure Credentials

This file lists the Azure credential configurations to publish the Thunder metrics or logs to Azure Application Insights and Azure Log Analytics Workspace respectively.

File Path: /root/.azure/credentials

Update the following parameters according to your Azure setup:

azure_workspace_primary_key = XXXX
azure_client_id = XXXX
azure_secret_id = XXXX
azure_tenant_id = XXXX
azure_location = XXXX

Table 27 : Azure Credentials File Parameters

Parameter	Description
azure_workspace_primary_key	To get the workspace primary key, go to Azure Portal > Azure services > Log Analytics workspaces > <log_analytics_workspace> > Settings > Agents. Figure 4 : Agents window
azure_client_id	To get the client ID, secret ID, and tenant ID, go to Azure Portal > Azure services > Azure Active Directory > App Registration > Owned applications > <application_name>. Figure 5 : Azure active directory - App registrations window
azure_secret_id
azure_tenant_id
azure_location	To get the location, go to Azure Portal > Azure services > Resource Groups > <your_resource_group> > Overview > Essentials > Location. Figure 6 : Resource Group window

For sample configuration, see Examples.

VMware Credentials

This file lists the VMware credential configurations to publish the metrics or logs.

File Path: /root/.vmware/credentials

Update the following parameters according to your VMware setup:

vmware_vrops_username = XXXX
vmware_vrops_password = XXXX

Table 28 : VMware Credentials File Parameters

Parameter	Description
vmware_vrops_username	Specifies your vROps login credentials.
vmware_vrops_password

For sample configuration, see Examples.

Elasticsearch Credentials

This file lists the Elasticsearch credential configurations to publish the metrics or logs.

File Path: /root/.elasticsearch/credentials

Update the following parameters according to your Elasticsearch setup:

username = XXXX

password = XXXX

Table 29 : Elasticsearch Credentials File Parameters

Parameter	Description
username	Specifies your Elasticsearch login credentials.
password

For sample configuration, see Examples.

PushGateway Credentials

This file lists the PushGateway credential configurations to publish the metrics or logs.

File Path: /root/.pushgateway/credentials

Update the following parameters according to your PushGateway setup:

username = XXXX

password = XXXX

Table 30 : PushGateway Credentials File Parameters

Parameter	Description
username	Specifies your PushGateway login credentials.
password

For sample configuration, see Examples.

Splunk Credentials

This file lists the Splunk credential configurations to publish the metrics or logs.

File Path: /root/.splunk/credentials

Update the following parameters according to your Splunk setup:

token_log = XXXX

token_metric = XXXX

Table 31 : Splunk Credentials File Parameters

Parameter	Description
token_log	Specifies your Splunk HEC token for logs and metrics.
token_metric

For sample configuration, see Examples.

GCP Credentials

This file lists the GCP credential configurations to publish the metrics or logs.

File Path: /root/.gcp/credentials

Update the following parameters according to your GCP setup:

gcp_project_id = XXXX

gcp_service_key_path = XXXX

Table 32 : GCP Credentials File Parameters

Parameter	Description
gcp_project_id	Specifies your GCP project ID and path to the service account key file. To obtain the GCP project ID and service account key file path, perform the following steps: Open Google Cloud Console and select the project you want to work with. Navigate to IAM & Admin > Service Accounts. Click Create Service Account and provide the service account details. Click Create and continue, followed by Done. The service account will be created. On the Service Accounts page, select the created service account and click the three dots (...) on the Action column. Select Manage Keys. The Keys page will be displayed. Click the Add key drop-down menu and select Create new key. Select the Key type as JSON and click Create. The service account key file will be download to your system. Open the file in a text editor and locate the project_id field. The value of this keys represents gcp_project_id in the GCP credentials file. Store the downloaded JSON securely and provide its path as the gcp_service_key_path in the GCP credentials file.
gcp_service_key_path

For sample configuration, see Examples.

OCI Credentials

This file lists the OCI credential configurations to publish the metrics or logs.

File Path: /root/.oci/credentials

Update the following parameter according to your OCI setup:

oci_api_key_path= XXXXXXXX

Table 33 : OCI Credentials File Parameter

Parameter

Description

oci_api_key_path

Specifies the path to the private key file used for authenticating the OCI services. To obtain the oci_api_key_path, perform the following steps: Log in to the Oracle Cloud Infrastructure console, open the Profile menu, and click My Profile. In the Resources section, click API Keys. Click Add API Key. The Add API Key dialog will be displayed. Click Download Private Key. The file will be downloaded to your system. Store this file securely. Click Add. The Configuration File Preview page will be displayed. This page allows you to preview the configuration file. This file includes basic authentication information required to create your configuration file. Copy and paste the configuration snippet from the text box into your text editor and save the configuration file without specifying any file extension. After pasting the snippet, update the key_file parameter with the location where the private key file is saved (downloaded and saved previously). The newly created configuration file (without any file extension) is considered an OCI API key file. Provide this API key file path as the oci_api_key_path in the OCI credentials file.

For sample configuration, see Examples.