# Kubernetes enrichment options

Copy as Markdown[Open in ChatGPT](https://chatgpt.com/?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fuser-guides%2Finfrastructure%2Finfrastructure-explorer%2Fkubernetes-enrichment-options.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)[Open in Claude](https://claude.ai/new?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fuser-guides%2Finfrastructure%2Finfrastructure-explorer%2Fkubernetes-enrichment-options.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)

## Host data[​](#host-data "Direct link to Host data")

After connecting your Kubernetes clusters to Coralogix Infrastructure Explorer, enrich host metadata for the cloud instances running your clusters by following [Getting started with host monitoring](https://coralogix.com/docs/docs/user-guides/infrastructure/infrastructure-explorer/getting-started-host-monitoring/.md). The [AWS Infrastructure Explorer integration](https://coralogix.com/docs/docs/integrations/aws/aws-infrastructure-explorer/.md) ingests metadata for AWS EC2 instances, the [Azure Infrastructure Explorer integration](https://coralogix.com/docs/docs/integrations/azure/azure-infrastructure-explorer/.md) ingests metadata for Azure Virtual Machines and Virtual Machine Scale Set instances, and the [GCP Infrastructure Explorer integration](https://coralogix.com/docs/docs/integrations/gcp/gcp-infrastructure-explorer/.md) ingests metadata for Google Compute Engine instances.

The example below shows how resource metadata appears before and after enrichment is enabled.

Before enrichment:

[![Resource metadata before enrichment](/docs/assets/images/Before-enrichment-60a141afb3bf013ac566ec454f081846.webp)](https://coralogix.com/docs/docs/assets/images/Before-enrichment-60a141afb3bf013ac566ec454f081846.webp)

After enrichment:

[![Resource metadata after enrichment](/docs/assets/images/after-enrichment-63e518dbe9f2be1129269b791b471f43.webp)](https://coralogix.com/docs/docs/assets/images/after-enrichment-63e518dbe9f2be1129269b791b471f43.webp)

> **Note:** Metadata enrichment is supported for AWS EC2 instances, Azure Virtual Machines (including Virtual Machine Scale Set instances), and Google Compute Engine instances.

### Host metrics[​](#host-metrics "Direct link to Host metrics")

The `hostMetrics` preset is enabled by default in the Coralogix Kubernetes OpenTelemetry deployment. To add CloudWatch metrics to your dashboards, install the [AWS CloudWatch Metrics Connector](https://coralogix.com/docs/docs/integrations/aws/aws-cloudwatch/aws-metrics-via-cloudwatch/.md).

With the connector installed, CloudWatch metrics for hosts running your Kubernetes workloads become available:

* Metrics are collected every 10 minutes by default (increase the interval to reduce usage).
* Metric definitions are refreshed every 5 minutes.

If you require more frequent metric updates, use the [Firehose-based integration](https://coralogix.com/docs/docs/integrations/aws/amazon-data-firehose/aws-cloudwatch-metric-streams-with-amazon-data-firehose/.md) for near real-time ingestion.

### Host process[​](#host-process "Direct link to Host process")

The Process preset, part of `hostMetrics`, is disabled by default. To enable it, update your OpenTelemetry agent configuration as shown below:

```
hostMetrics:

  process:

    enabled: true
```

Find more details in the [advanced agent configuration guide](https://coralogix.com/docs/docs/opentelemetry/kubernetes-observability/advanced-configuration/.md#agent-presets). Once enabled, host process data will be available in the **Process** tab of your host dashboard.

## Send application telemetry to the Coralogix agent[​](#send-application-telemetry-to-the-coralogix-agent "Direct link to Send application telemetry to the Coralogix agent")

In addition to infrastructure data, send application logs, metrics, and traces to the Coralogix agent running on each Kubernetes node.

### Step 1: Set up the Kubernetes Complete Observability integration[​](#step-1-set-up-the-kubernetes-complete-observability-integration "Direct link to Step 1: Set up the Kubernetes Complete Observability integration")

Follow the [Kubernetes Complete Observability integration setup guide](https://coralogix.com/docs/opentelemetry/kubernetes-observability/kubernetes-complete-observability-basic-configuration/?utm_source=chatgpt.com) to deploy the required components.

### Step 2: Configure your applications to export telemetry[​](#step-2-configure-your-applications-to-export-telemetry "Direct link to Step 2: Configure your applications to export telemetry")

Add the following environment variables to your application deployments to direct telemetry to the node-local agent:

```
- name: NODE_IP

  valueFrom:

    fieldRef:

      fieldPath: status.hostIP



- name: OTEL_EXPORTER_OTLP_ENDPOINT

  value: "$(NODE_IP):4317"



- name: OTEL_EXPORTER_OTLP_PROTOCOL

  value: "grpc"



- name: OTEL_EXPORTER_OTLP_INSECURE

  value: "true"
```

These settings ensure that logs, metrics, and traces from your applications are sent to the OpenTelemetry agent over OTLP (gRPC).

Once applied, your application telemetry will appear in Coralogix Infrastructure Explorer alongside infrastructure data.

## Next steps[​](#next-steps "Direct link to Next steps")

Enable host monitoring for your cloud and on-prem machines by following [Getting started with host monitoring](https://coralogix.com/docs/docs/user-guides/infrastructure/infrastructure-explorer/getting-started-host-monitoring/.md).

## Related resources[​](#related-resources "Direct link to Related resources")

* [Getting started with Kubernetes monitoring](https://coralogix.com/docs/docs/user-guides/infrastructure/infrastructure-explorer/getting-started-kubernetes-monitoring/.md)
* [Host data enrichments](https://coralogix.com/docs/docs/user-guides/infrastructure/infrastructure-explorer/host-data-enrichment/.md)
* [Configure applications to send telemetry](https://coralogix.com/docs/docs/user-guides/infrastructure/infrastructure-explorer/configure-application-telemetry/.md)