Open topic with navigation

Data Publish Configuration

The Thunder metrics and logs can be published on the cloud platforms such as AWS, Azure, VMware, Kibana (Elasticsearch), Grafana (Prometheus and Pushgateway), Splunk, Google Cloud Platform (GCP), or Oracle Cloud Infrastructure (OCI). To publish the Thunder metrics or logs, configure the config.json file with the appropriate TOA parameters for the required cloud platform:

Config JSON

This file lists the TOA configurations to collect Thunder metrics or logs and enable the required cloud provider.

File Path: /usr/toaenv/thunder-observability-agent/config.json

ClosedMetrics

Depending on your cloud platform, configure the parameters to publish the Thunder metrics.

ClosedAWS

Configure the following parameters in the config.json to publish Thunder metrics to the AWS CloudWatch. By default, all the metrics are enabled. You can enable one or more Thunder Metrics.

NOTE: For better throughput, you must enable only those metrics which are required.
Table 36 : AWS Configuration Parameters
Parameter Description Default Value

aws_provider

Specify 1 to publish selected metric/s, logs, or both to AWS.

By default, it is disabled and does not send metric to AWS. To publish metric/s it is mandatory to enable AWS as a provider.

0

aws_metric

Specify 1 to publish metrics to AWS CloudWatch. It sends the data only if aws_provider is also enabled.

By default, it is disabled.

0

aws_cpu

Specify 1 to publish the deployed Thunder instances' average data CPU usage (percentage) on the AWS CloudWatch. If the aws_provider and aws_metrics parameters are enabled, TOA sends this metric to the AWS CloudWatch.

By default, it is enabled.

1

aws_memory

Specify 1 to publish the deployed Thunder instances' memory usage (percentage) on the AWS CloudWatch.

By default, it is enabled.

1

aws_disk

Specify 1 to publish the deployed Thunder instances' storage disk usage on the AWS CloudWatch.

By default, it is enabled.

1

aws_throughput

Specify 1 to publish the deployed Thunder instances' active throughput on the AWS CloudWatch.

By default, it is enabled.

1

aws_interfaces

Specify 1 to publish the deployed Thunder instances' interface down count on the AWS CloudWatch.

By default, it is enabled.

1

aws_cps

Specify 1 to publish the deployed Thunder instances' new connection rate per second on the AWS CloudWatch.

By default, it is enabled.

1

aws_tps

Specify 1 to publish the deployed Thunder instances' transaction rate per second on the AWS CloudWatch.

By default, it is enabled.

1

aws_server_down_count

Specify 1 to publish the deployed Thunder instances' server down count on the AWS CloudWatch.

By default, it is enabled.

1

aws_server_down_percentage

Specify 1 to publish the deployed Thunder instances' configured web/app servers down percentage on the AWS CloudWatch.

By default, it is enabled.

1

aws_ssl_cert

Specify 1 to publish the deployed Thunder instances' SSL cert error count on the AWS CloudWatch.

By default, it is enabled.

1

aws_server_error

Specify 1 to publish the deployed Thunder instances web/app servers 4xx, 5xx errors count on the AWS CloudWatch.

By default, it is enabled.

1

aws_sessions

Specify 1 to publish the deployed Thunder instances' active session count on the AWS CloudWatch.

By default, it is enabled.

1

aws_packet_rate

Specify 1 to publish the deployed Thunder instances' packet rate on the AWS CloudWatch.

By default, it is enabled.

1

aws_packet_drop

Specify 1 to publish the deployed Thunder instances' packet drop count on the AWS CloudWatch.

By default, it is enabled.

1

ClosedAzure

Configure the following parameters in the config.json to publish Thunder metrics to the Azure Application Insights. By default, all the metrics are enabled. You can enable one or more Thunder Metrics.

NOTE: For better throughput, you must enable only those metrics which are required.
Table 37 : Azure Configuration Parameters
Parameter Description Default Value

azure_provider

Specify 1 to publish selected metric/s, logs, or both to Azure.

By default, it is disabled and does not send metrics to Azure. To publish metric/s it is mandatory to enable Azure as a provider.

0

azure_metric

Specify 1 to send metrics to Azure Application Insights. It sends the data only if azure_provider is also enabled.

By default, it is disabled.

0

azure_metric_resource_id

Specifies the Azure Application Insights resource ID.

To get this value, go to Azure Portal > Azure services > Application Insights > <your_Thunder_instance> > Properties > Resource ID.

Example

/subscriptions/07dxxxxxxxxxxx/
resourceGroups/
<resource_group_name>/
providers/microsoft.insights/
components/<app-insight-name>

<azure_
metric_
resource_id>

azure_cpu

Specify 1 to publish the deployed Thunder instances' average data CPU usage (percentage) on the Azure Application Insights. If the azure_provider and azure_metrics parameters are enabled, TOA sends this metric to the Azure Application Insights.

By default, it is enabled.

1

azure_memory

Specify 1 to publish the deployed Thunder instances' memory usage (percentage) on the Azure Application Insights.

By default, it is enabled.

1

azure_disk

Specify 1 to publish the deployed Thunder instances' storage disk on the Azure Application Insights.

By default, it is enabled.

1

azure_throughput

Specify 1 to publish the deployed Thunder instances' active throughput on the Azure Application Insights.

By default, it is enabled.

1

azure_interfaces

Specify 1 to publish the deployed Thunder instances' interfaces down count on the Azure Application Insights.

By default, it is enabled.

1

azure_cps

Specify 1 to publish the deployed Thunder instances' new connection per second on the Azure Application Insights.

By default, it is enabled.

1

azure_tps

Specify 1 to publish the deployed Thunder instances' transaction rate per second on the Azure Application Insights.

By default, it is enabled.

1

azure_server_down_count

Specify 1 to publish the deployed Thunder instances' web/app servers down count on the Azure Application Insights.

By default, it is enabled.

1

azure_server_down_percentage

Specify 1 to publish the deployed Thunder instances' configured web/app servers down percentage on the Azure Application Insights.

By default, it is enabled.

1

azure_ssl_cert

Specify 1 to publish the deployed Thunder instances' SSL error count on the Azure Application Insights.

By default, it is enabled.

1

azure_server_error

Specify 1 to publish the deployed Thunder instances' web/app servers 4xx, 5xx errors count on the Azure Application Insights.

By default, it is enabled.

1

azure_sessions

Specify 1 to publish the deployed Thunder instances' active session count on the Azure Application Insights.

By default, it is enabled.

1

azure_packet_rate

Specify 1 to publish the deployed Thunder instances' packet rate on the Azure Application Insights.

By default, it is enabled.

1

azure_packet_drop

Specify 1 to publish the deployed Thunder instances' packet drop count on the Azure Application Insights.

By default, it is enabled.

1

ClosedVMware

Configure the following parameters in the config.json to publish Thunder metrics to the VMware vROps. By default, all the metrics are enabled. You can enable one or more Thunder Metrics.

NOTE: For better throughput, you must enable only those metrics which are required.
Table 38 : VMware Configuration Parameters
Parameter Description Default Value

vmware_provider

Specify 1 to publish selected metric/s, logs, or both to VMware.

By default, it is disabled and does not send metric to VMware. To publish metric/s it is mandatory to enable VMware as a provider.

0

vmware_metric

Specify 1 to publish the metrics to VMware vROps. It sends the data only if vmware_provider is also enabled.

By default, it is disabled.

 0

vmware_vrops_host

Specifies the VMware vROps host IP address. To get the host, go to ESXi host > Virtual Machines > <your_vROps_VM> > Networking > IP Address.

<vmware_vrops_
host_or_ip>

vmware_cpu

Specify 1 to publish the deployed Thunder instances' average data CPU usage (percentage) on the VMware vROps. If the vmware_provider and vmware_metrics parameters are enabled, TOA sends this metric to the VMware vROps.

By default, it is enabled.

1

vmware_memory

Specify 1 to publish the deployed Thunder instances' memory usage (percentage) on the VMware vROps.

By default, it is enabled.

1

vmware_disk

Specify 1 to publish the deployed Thunder instances' storage disk on the VMware vROps.

By default, it is enabled.

1

vmware_throughput

Specify 1 to publish the deployed Thunder instances' active throughput on the VMware vROps.

By default, it is enabled.

1

vmware_interfaces

Specify 1 to publish the deployed Thunder instances' interfaces down count on the VMware vROps.

By default, it is enabled.

1

vmware_cps

Specify 1 to publish the deployed Thunder instances' new connections per second on the VMware vROps.

By default, it is enabled.

1

vmware_tps

Specify 1 to publish the deployed Thunder instances' transaction rate per second on the VMware vROps.

By default, it is enabled.

1

vmware_server_down_count

Specify 1 to publish the deployed Thunder instances' web/app servers down count on the VMware vROps.

By default, it is enabled.

1

vmware_server_down_percentage

Specify 1 to publish the deployed Thunder instances' configured web/app servers down percentage on the VMware vROps.

By default, it is enabled.

1

vmware_ssl_cert

Specify 1 to publish the deployed Thunder instances' SSL error count on the VMware vROps.

By default, it is enabled.

1

vmware_server_error

Specify 1 to publish the deployed Thunder instances' web/app servers 4xx, 5xx errors count on the VMware vROps.

By default, it is enabled.

1

vmware_sessions

Specify 1 to publish the deployed Thunder instances' active session count on the VMware vROps.

By default, it is enabled.

1

vmware_packet_rate

Specify 1 to publish the deployed Thunder instances' packet rate on the VMware vROps.

By default, it is enabled.

1

vmware_packet_drop

Specify 1 to publish the deployed Thunder instances' packet drop count on the VMware vROps.

By default, it is enabled.

1

ClosedElasticsearch

Configure the following parameters in the config.json to publish Thunder metrics to Elasticsearch. By default, all the metrics are enabled. You can enable one or more Thunder Metrics.

NOTE: For better throughput, you must enable only those metrics which are required.
Table 39 : Elasticsearch Configuration Parameters
Parameter Description Default Value

es_provider

Specify 1 to publish selected metric/s, logs, or both to Elasticsearch.

By default, it is disabled and does not send metric to Elasticsearch. To publish metric/s it is mandatory to enable Elasticsearch as a provider.

0

es_metric

Specify 1 to publish the metrics to Elasticsearch. It sends the data only if es_provider is also enabled.

By default, it is disabled.

 0

es_host

Specify the Elasticsearch host IP address.

<host/ip:port>

es_cpu

Specify 1 to publish the deployed Thunder instances' average data CPU usage (percentage) on Elasticsearch. If the es_provider and es_metrics parameters are enabled, TOA sends this metric to Elasticsearch.

By default, it is enabled.

1

es_memory

Specify 1 to publish the deployed Thunder instances' memory usage (percentage) on Elasticsearch.

By default, it is enabled.

1

es_disk

Specify 1 to publish the deployed Thunder instances' storage disk on Elasticsearch.

By default, it is enabled.

1

es_throughput

Specify 1 to publish the deployed Thunder instances' active throughput on Elasticsearch.

By default, it is enabled.

1

es_interfaces

Specify 1 to publish the deployed Thunder instances' interfaces down count on Elasticsearch.

By default, it is enabled.

1

es_cps

Specify 1 to publish the deployed Thunder instances' new connections per second on Elasticsearch.

By default, it is enabled.

1

es_tps

Specify 1 to publish the deployed Thunder instances' transaction rate per second on Elasticsearch.

By default, it is enabled.

1

es_server_down_count

Specify 1 to publish the deployed Thunder instances' web/app servers down count on Elasticsearch.

By default, it is enabled.

1

es_server_down_percentage

Specify 1 to publish the deployed Thunder instances' configured web/app servers down percentage on Elasticsearch.

By default, it is enabled.

1

es_ssl_cert

Specify 1 to publish the deployed Thunder instances' SSL error count on Elasticsearch.

By default, it is enabled.

1

es_server_error

Specify 1 to publish the deployed Thunder instances' web/app servers 4xx, 5xx errors count on Elasticsearch.

By default, it is enabled.

1

es_sessions

Specify 1 to publish the deployed Thunder instances' active session count on Elasticsearch.

By default, it is enabled.

1

es_packet_rate

Specify 1 to publish the deployed Thunder instances' packet rate on Elasticsearch.

By default, it is enabled.

1

es_packet_drop

Specify 1 to publish the deployed Thunder instances' packet drop count on Elasticsearch.

By default, it is enabled.

1

ClosedPushGateway

Configure the following parameters in the config.json to publish Thunder metrics to the Pushgateway. By default, all the metrics are enabled. You can enable one or more Thunder Metrics.

NOTE: For better throughput, you must enable only those metrics which are required.
Table 40 : Pushgateway Configuration Parameters
Parameter Description Default Value

pushgateway_provider

Specify 1 to publish selected metric/s, logs, or both to Pushgateway.

By default, it is disabled and does not send metric to Pushgateway. To publish metric/s it is mandatory to enable Pushgateway as a provider.

0

pushgateway_metric

Specify 1 to publish the metrics to Pushgateway. It sends the data only if pushgateway_provider is also enabled.

By default, it is disabled.

 0

pushgateway_host

Specify the Pushgateway host IP address.

<host/ip:port>

pushgateway_cpu

Specify 1 to publish the deployed Thunder instances' average data CPU usage (percentage) on Pushgateway. If the pushgateway_provider and pushgateway_metrics parameters are enabled, TOA sends this metric to the Pushgateway.

By default, it is enabled.

1

pushgateway_memory

Specify 1 to publish the deployed Thunder instances' memory usage (percentage) on Pushgateway.

By default, it is enabled.

1

pushgateway_disk

Specify 1 to publish the deployed Thunder instances' storage disk on the Pushgateway.

By default, it is enabled.

1

pushgateway_throughput

Specify 1 to publish the deployed Thunder instances' active throughput on Pushgateway.

By default, it is enabled.

1

pushgateway_interfaces

Specify 1 to publish the deployed Thunder instances' interfaces down count on Pushgateway.

By default, it is enabled.

1

pushgateway_cps

Specify 1 to publish the deployed Thunder instances' new connections per second on Pushgateway.

By default, it is enabled.

1

pushgateway_tps

Specify 1 to publish the deployed Thunder instances' transaction rate per second on Pushgateway.

By default, it is enabled.

1

pushgateway_server_down_count

Specify 1 to publish the deployed Thunder instances' web/app servers down count on Pushgateway.

By default, it is enabled.

1

pushgateway_server_down_percentage

Specify 1 to publish the deployed Thunder instances' configured web/app servers down percentage on Pushgateway.

By default, it is enabled.

1

pushgateway_ssl_cert

Specify 1 to publish the deployed Thunder instances' SSL error count on Pushgateway.

By default, it is enabled.

1

pushgateway_server_error

Specify 1 to publish the deployed Thunder instances' web/app servers 4xx, 5xx errors count on Pushgateway.

By default, it is enabled.

1

pushgateway_sessions

Specify 1 to publish the deployed Thunder instances' active session count on Pushgateway.

By default, it is enabled.

1

pushgateway_packet_rate

Specify 1 to publish the deployed Thunder instances' packet rate on Pushgateway.

By default, it is enabled.

1

pushgateway_packet_drop

Specify 1 to publish the deployed Thunder instances' packet drop count on Pushgateway.

By default, it is enabled.

1

ClosedSplunk

Configure the following parameters in the config.json to publish Thunder metrics to the Splunk. By default, all the metrics are enabled. You can enable one or more Thunder Metrics.

NOTE: For better throughput, you must enable only those metrics which are required.
Table 41 : Splunk Configuration Parameters
Parameter Description Default Value

splunk_provider

Specify 1 to publish selected metric/s, logs, or both to Splunk.

By default, it is disabled and does not send metric to Splunk. To publish metric/s it is mandatory to enable Splunk as a provider.

0

splunk_metric

Specify 1 to publish the metrics to Splunk. It sends the data only if splunk_provider is also enabled.

By default, it is disabled.

 0

splunk_host

Specify the Splunk host IP address.

<host/ip:port>

splunk_cpu

Specify 1 to publish the deployed Thunder instances' average data CPU usage (percentage) on Splunk. If the splunk_provider and splunk_metrics parameters are enabled, TOA sends this metric to the Splunk.

By default, it is enabled.

1

splunk_memory

Specify 1 to publish the deployed Thunder instances' memory usage (percentage) on Splunk.

By default, it is enabled.

1

splunk_disk

Specify 1 to publish the deployed Thunder instances' storage disk on Splunk.

By default, it is enabled.

1

splunk_throughput

Specify 1 to publish the deployed Thunder instances' active throughput on Splunk.

By default, it is enabled.

1

splunk_interfaces

Specify 1 to publish the deployed Thunder instances' interfaces down count on Splunk.

By default, it is enabled.

1

splunk_cps

Specify 1 to publish the deployed Thunder instances' new connections per second on Splunk.

By default, it is enabled.

1

splunk_tps

Specify 1 to publish the deployed Thunder instances' transaction rate per second on Splunk.

By default, it is enabled.

1

splunk_server_down_count

Specify 1 to publish the deployed Thunder instances' web/app servers down count on Splunk.

By default, it is enabled.

1

splunk_server_down_percentage

Specify 1 to publish the deployed Thunder instances' configured web/app servers down percentage on Splunk.

By default, it is enabled.

1

splunk_ssl_cert

Specify 1 to publish the deployed Thunder instances' SSL error count on Splunk.

By default, it is enabled.

1

splunk_server_error

Specify 1 to publish the deployed Thunder instances' web/app servers 4xx, 5xx errors count on Splunk.

By default, it is enabled.

1

splunk_sessions

Specify 1 to publish the deployed Thunder instances' active session count on Splunk.

By default, it is enabled.

1

splunk_packet_rate

Specify 1 to publish the deployed Thunder instances' packet rate on Splunk.

By default, it is enabled.

1

splunk_packet_drop

Specify 1 to publish the deployed Thunder instances' packet drop count on Splunk.

By default, it is enabled.

1

ClosedGoogle Cloud Platform (GCP)

Configure the following parameters in the config.json to publish Thunder metrics to the GCP. By default, all the metrics are enabled. You can enable one or more Thunder Metrics.

NOTE: For better throughput, you must enable only those metrics which are required.

Additionally, you must enable the Strackdriver Monitoring API in the Google Cloud console. To do so, navigate to APIs & Services > Library > Strackdriver Monitoring API, and click Enable.

Table 42 : GCP Configuration Parameters
Parameter Description Default Value

gcp_provider

Specify 1 to publish selected metric/s, logs, or both to GCP.

By default, it is disabled and does not send metric to GCP. To publish metric/s it is mandatory to enable GCP as a provider.

0

gcp_metric

Specify 1 to publish the metrics to GCP. It sends the data only if gcp_provider is also enabled.

By default, it is disabled.

 0

gcp_cpu

Specify 1 to publish the deployed Thunder instances' average data CPU usage (percentage) on GCP. If the gcp_provider and gcp_metrics parameters are enabled, TOA sends this metric to the GCP.

By default, it is enabled.

1

gcp_memory

Specify 1 to publish the deployed Thunder instances' memory usage (percentage) on GCP.

By default, it is enabled.

1

gcp_disk

Specify 1 to publish the deployed Thunder instances' storage disk on GCP.

By default, it is enabled.

1

gcp_throughput

Specify 1 to publish the deployed Thunder instances' active throughput on GCP.

By default, it is enabled.

1

gcp_interfaces

Specify 1 to publish the deployed Thunder instances' interfaces down count on GCP.

By default, it is enabled.

1

gcp_cps

Specify 1 to publish the deployed Thunder instances' new connections per second on GCP.

By default, it is enabled.

1

gcp_tps

Specify 1 to publish the deployed Thunder instances' transaction rate per second on GCP.

By default, it is enabled.

1

gcp_server_down_count

Specify 1 to publish the deployed Thunder instances' web/app servers down count on GCP.

By default, it is enabled.

1

gcp_server_down_percentage

Specify 1 to publish the deployed Thunder instances' configured web/app servers down percentage on GCP.

By default, it is enabled.

1

gcp_ssl_cert

Specify 1 to publish the deployed Thunder instances' SSL error count on GCP.

By default, it is enabled.

1

gcp_server_error

Specify 1 to publish the deployed Thunder instances' web/app servers 4xx, 5xx errors count on GCP.

By default, it is enabled.

1

gcp_sessions

Specify 1 to publish the deployed Thunder instances' active session count on GCP.

By default, it is enabled.

1

gcp_packet_rate

Specify 1 to publish the deployed Thunder instances' packet rate on GCP.

By default, it is enabled.

1

gcp_packet_drop

Specify 1 to publish the deployed Thunder instances' packet drop count on GCP.

By default, it is enabled.

1

ClosedOracle Cloud Infrastructure (OCI)

Configure the following parameters in the config.json to publish Thunder metrics to the OCI. By default, all the metrics are enabled. You can enable one or more Thunder Metrics.

NOTE: For better throughput, you must enable only those metrics which are required.

Before publishing metrics in OCI, you must create and manage certain policies that define the necessary permissions. To do the same, see Create Policies to Publish Data in OCI.

Table 43 : OCI Configuration Parameters
Parameter Description Default Value

oci_provider

Specify 1 to publish selected metric/s, logs, or both to OCI.

By default, it is disabled and does not send metric to OCI. To publish metric/s it is mandatory to enable OCI as a provider.

0

oci_metric

Specify 1 to publish the metrics to OCI. It sends the data only if oci_provider is also enabled.

By default, it is disabled.

 0

oci_cpu

Specify 1 to publish the deployed Thunder instances' average data CPU usage (percentage) on OCI. If the oci_provider and oci_metrics parameters are enabled, TOA sends this metric to the OCI.

By default, it is enabled.

1

oci_memory

Specify 1 to publish the deployed Thunder instances' memory usage (percentage) on OCI.

By default, it is enabled.

1

oci_disk

Specify 1 to publish the deployed Thunder instances' storage disk on OCI.

By default, it is enabled.

1

oci_throughput

Specify 1 to publish the deployed Thunder instances' active throughput on OCI.

By default, it is enabled.

1

oci_interfaces

Specify 1 to publish the deployed Thunder instances' interfaces down count on OCI.

By default, it is enabled.

1

oci_cps

Specify 1 to publish the deployed Thunder instances' new connections per second on OCI.

By default, it is enabled.

1

oci_tps

Specify 1 to publish the deployed Thunder instances' transaction rate per second on OCI.

By default, it is enabled.

1

oci_server_down_count

Specify 1 to publish the deployed Thunder instances' web/app servers down count on OCI.

By default, it is enabled.

1

oci_server_down_percentage

Specify 1 to publish the deployed Thunder instances' configured web/app servers down percentage on OCI.

By default, it is enabled.

1

oci_ssl_cert

Specify 1 to publish the deployed Thunder instances' SSL error count on OCI.

By default, it is enabled.

1

oci_server_error

Specify 1 to publish the deployed Thunder instances' web/app servers 4xx, 5xx errors count on OCI.

By default, it is enabled.

1

oci_sessions

Specify 1 to publish the deployed Thunder instances' active session count on OCI.

By default, it is enabled.

1

oci_packet_rate

Specify 1 to publish the deployed Thunder instances' packet rate on OCI.

By default, it is enabled.

1

oci_packet_drop

Specify 1 to publish the deployed Thunder instances' packet drop count on OCI.

By default, it is enabled.

1

oci_compartment_id

Specify the compartment id, also known as Oracle Cloud Identifier (OCID), of your compartment in Oracle Cloud Infrastructure (OCI).

To obtain the OCID, perform the following steps:

  1. Open the OCI console and access the navigation menu.

  2. Click Identity & Security, and under the Identity section, select Compartments.

    A list of compartments that exist within your OCI tenancy will be displayed.

  3. Click the compartment of your choice.

    The Instance Information tab will be displayed.

  4. Under General Information, next to OCID, click Show.

    The full OCID value will be displayed.

  5. Click Copy to copy the OCID to your clipboard and then paste it into the service request form field.
 ocid1.compartment.oc1..xxxxxxxx
ClosedLogs

Depending upon your cloud platform, configure the following parameters to publish the Thunder logs:

ClosedAWS

Configure the following parameters in the config.json to publish Thunder Logs to the AWS CloudWatch.

Table 44 : AWS Configuration Parameters
Parameter Description Default Value

aws_provider

Specify 1 to publish selected metric/s, logs, or both to AWS.

By default, it is disabled and does not send logs to AWS. To publish logs it is mandatory to enable AWS as a provider.

0

aws_log

Specify 1 to publish the logs to AWS CloudWatch. It sends the data only if aws_provider is also enabled.

By default, it is disabled.

0

aws_log_group_name

Specifies the log group name under which all logs are sent to AWS CloudWatch.

To get this folder, it can be found under AWS Management Console > CloudWatch > Logs > <log_group_name>.

<aws_log_group_name>

For sample configuration, see Examples.

ClosedAzure

Configure the following parameters in the config.json to publish Thunder Logs to the Azure Log Analytics Workspace.

Table 45 : Azure Configuration Parameters
Parameter Description Default Value

azure_provider

Specify 1 to publish the selected metric/s, logs, or both to Azure.

By default, it is disabled and does not send logs to Azure. To publish logs, it is mandatory to enable Azure as a provider.

0

azure_log

Specify 1 to publish the logs to Azure Log Analytics Workspace. It sends the data only if azure_provider is also enabled.

By default, it is disabled.

0

azure_log_workspace_id

Specifies the Azure Log Analytics Workspace ID.

To get this value, go to Azure Portal > Azure services > Log Analytics workspaces > <your_log_analytics_workspace> > Settings > Agents.

<azure_log_workspace_id>

For sample configuration, see Examples.

ClosedVMware

Configure the following parameters in the config.json to publish Thunder Logs to the VMware vRLI.

Table 46 : VMware Configuration Parameters
Parameter Description Default Value

vmware_provider

Specify 1 to publish the selected metric/s, logs, or both to VMware.

By default, it is disabled and does not send logs to VMware. To publish logs, it is mandatory to enable VMware as a provider.

0

vmware_log

Specify 1 to publish the logs to VMware vRLI. It sends the data only if vmware_provider is also enabled.

By default, it is disabled.

0

vmware_vrli_host

Specifies the VMware vRLI host IP address. To get the host, go to ESXi host > Virtual Machines > <your_vRLI_VM> > Networking > IP Address.

<vmware_vrli_host_or_ip>

For sample configuration, see Examples.

ClosedElasticsearch

Configure the following parameters in the config.json to publish Thunder Logs to Elasticsearch.

Table 47 : Elasticsearch Configuration Parameters
Parameter Description Default Value

es_provider

Specify 1 to publish the selected metric/s, logs, or both to Elasticsearch.

By default, it is disabled and does not send logs to Elasticsearch. To publish logs, it is mandatory to enable Elasticsearch as a provider.

0

es_log

Specify 1 to publish the logs to Elasticsearch. It sends the data only if es_provider is also enabled.

By default, it is disabled.

0

es_host

Specify the Elasticsearch host IP address.

<host/ip:port>

For sample configuration, see Examples.

ClosedPrometheus

Configure the following parameters in the config.json to publish Thunder Logs to Pushgateway.

Table 48 : Prometheus Configuration Parameters
Parameter Description Default Value

pushgateway_provider

Specify 1 to publish the selected metric/s, logs, or both to Pushgateway.

By default, it is disabled and does not send logs to Pushgateway. To publish logs, it is mandatory to enable Pushgateway as a provider.

0

pushgateway_log

Specify 1 to publish the logs to Pushgateway. It sends the data only if pushgateway_provider is also enabled.

By default, it is disabled.

0

pushgateway_host

Specify the Pushgateway host IP address.

<host/ip:port>

For sample configuration, see Examples.

ClosedSplunk

Configure the following parameters in the config.json to publish Thunder Logs to Splunk.

Table 49 : Splunk Configuration Parameters
Parameter Description Default Value

splunk_provider

Specify 1 to publish the selected metric/s, logs, or both to Splunk.

By default, it is disabled and does not send logs to Splunk. To publish logs, it is mandatory to enable Splunk as a provider.

0

splunk_log

Specify 1 to publish the logs to Splunk. It sends the data only if splunk_provider is also enabled.

By default, it is disabled.

0

splunk_host

Specify the Splunk host IP address.

<host/ip:port>

For sample configuration, see Examples.

ClosedGoogle Cloud Platform (GCP)

Configure the following parameters in the config.json to publish Thunder Logs to GCP.

Table 50 : GCP Configuration Parameters
Parameter Description Default Value

gcp_provider

Specify 1 to publish the selected metric/s, logs, or both to GCP.

By default, it is disabled and does not send logs to GCP. To publish logs, it is mandatory to enable GCP as a provider.

0

gcp_log

Specify 1 to publish the logs to GCP. It sends the data only if gcp_provider is also enabled.

By default, it is disabled.

0

Additionally, you must enable the Cloud Logging API in the Google Cloud console. To do so, navigate to APIs & Services > Library > Cloud Logging API, and click Enable.

For sample configuration, see Examples.

ClosedOracle Cloud Infrastructure (OCI)

Configure the following parameters in the config.json to publish Thunder Logs to OCI.

Before publishing logs in OCI, you must create and manage certain policies that define the necessary permissions. To do the same, see Create Policies to Publish Data in OCI.

Table 51 : OCI Configuration Parameters
Parameter Description Default Value

oci_provider

Specify 1 to publish the selected metric/s, logs, or both to OCI.

By default, it is disabled and does not send logs to OCI. To publish logs, it is mandatory to enable OCI as a provider.

0

oci_log

Specify 1 to publish the logs to OCI. It sends the data only if oci_provider is also enabled.

By default, it is disabled.

0

oci_log_id

Specify the Oracle Cloud Identifier (OCID) of your log in OCI. To obtain the OCID, perform the following steps:

  1. Open the OCI console, access the navigation menu, and click Observability & Management.
  2. Under Logging, click Log Groups.
  3. Under List Scope, select the compartment where you have the permissions.
  4. On the Log Groups page, click Create Log Group.

  5. Enter a log group name, description (optional), and click Create.

    A new log group will be created.

  6. Click on the newly created log group, navigate to the Logs tab within the group and click Create custom log.
  7. Enter a log name, select the log group created in the previous step and click Create custom log.

  8. Click Cancel on the Create agent configuration page (if prompted).

    A new log will be created.

  9. Click the newly created log. The OCID of the log will be displayed under the Log Information tab.
  10. Click Copy to copy the OCID to your clipboard and then paste it into the service request form field.
ocid1.log.oc1.xxxx.xxxxxxx

For sample configuration, see Examples.

COMPANY INFORMATION: Copyright © 2024 A10 Networks, Inc. All Rights Reserved. Legal Notice