Skip to main content
Densify recommends using the Kubex Automation Stack Helm Chart. This Helm chart bundles all of the components required for Kubex and is the preferred method of data collection. The following configuration options support multi-cluster configurations and observability platforms. See Container Data Collection Prerequisites for required prerequisite software.
In this configuration you can deploy the data forwarder with OpenShift (e.g. Authenticated Prometheus). Refer to Example: bearer-openshift for details. Figure: Container Data Collection Using Authenticated PrometheusSee Container Data Collection Prerequisites for details on prerequisite software.
In this example the data forwarder is setup in an EKS cluster to connect to Amazon Managed Prometheus (AMP) and send container data to Densify on an hourly basis. Using an EKS cluster allows you to use EKS’s ability to associate an IAM role with a Kubernetes service account and configure your pods to use the service account. This is the preferred way to connect to AMP. Figure: Container Data Collection Using EKS-AMP
Azure Monitor managed service for Prometheus can be used when deploying AKS clusters. Figure: Container Data Collection Using Azure Monitor with Managed Prometheus
The data forwarder can be setup to connect to Prometheus or an observability platform that supports the Prometheus API with HTTP basic authentication and sends container data from multiple clusters to Densify on an hourly basis. Figure: Container Data Collection from an Observability Platform