Hyphen
Log In

Observability

Connect Kubernetes telemetry data (metrics and logs) to Hyphen for enhanced cluster observability with New Relic and Google Cloud integrations.

Connect Kubernetes telemetry to a registered cluster so Hyphen Agent can use runtime metrics and logs alongside inventory. Kubernetes observability currently supports New Relic and Google Cloud.

Observability is optional for inventory and cleanup. It gives Kubernetes Optimizer more evidence about workload utilization, restarts, and runtime behavior.

Table of Contents

Before You Start

You need:

  • A registered Kubernetes cluster with Horizon connected.
  • A New Relic or Google Cloud organization integration in Hyphen.
  • Permission to manage organization integrations and cluster settings.
  • Kubernetes telemetry available in the selected provider.

Connect an Observability Source

  1. Open Kubernetes and select the cluster.
  2. Open Settings.
  3. In Observability, click Setup connection.
  4. Select one observability integration.
  5. Enter the provider-specific cluster identifier.
  6. Click Connect.

Connect a Kubernetes cluster to an observability integration

Hyphen validates the identifier and shows the connection while it is being prepared. A ready connection can supply metrics and logs to supported Agent runs.

New Relic

Enter the cluster name configured when the New Relic Kubernetes integration was installed. Hyphen verifies that the connected New Relic account contains a Kubernetes cluster sample with that name.

If Horizon detects one New Relic cluster name and the organization has exactly one New Relic integration, Hyphen can create the connection automatically. A newly installed New Relic agent may take time to send its first cluster sample; Hyphen retries retryable connection failures while telemetry becomes available.

See New Relic for integration requirements.

Google Cloud

Enter the full GKE cluster resource name:

projects/PROJECT_ID/locations/LOCATION/clusters/CLUSTER_NAME

The Hyphen service account needs these roles for the selected cluster and its telemetry:

  • Logs Viewer (roles/logging.viewer)
  • Monitoring Viewer (roles/monitoring.viewer)
  • Kubernetes Engine Cluster Viewer (roles/container.clusterViewer)

Hyphen can discover the resource name automatically when Horizon detects Google Cloud observability, the organization has exactly one Google Cloud integration, and Cloud Asset Inventory can resolve the cluster.

See Google Cloud for integration requirements.

Connection States and Errors

  • Pending - Hyphen is validating the provider and cluster identifier.
  • Ready - Metrics and logs are available to supported Agent analysis.
  • Error - Hyphen could not validate the cluster or query the provider. Open the connection to review the error and retry when available.

A missing New Relic cluster sample may be temporary while telemetry is first ingested. A Google Cloud not-found error can mean the resource name is incorrect or the Hyphen service account is missing the required viewer roles.

Remove a Connection

Open the cluster's Settings tab, find the provider under Observability, and remove its connection. Removing the connection does not uninstall an observability agent or delete provider telemetry. Agent continues to use Kubernetes inventory, but no longer queries that provider for the cluster.

Things to Know

  • Metrics and logs are supporting evidence; missing or partial telemetry does not prevent inventory from working.
  • Hyphen limits telemetry queries by time, workload, and pod context. Provider query errors are reported as capability gaps instead of being treated as healthy evidence.
  • Connect the provider account that receives telemetry for the registered cluster.
  • Hyphen does not request Kubernetes Secret contents for optimizer analysis.