Architecture
Container Observability ingests information from the application, Kubernetes orchestration, and infrastructure layers by tapping into the monitoring and configuration environment with lightweight gateway pods that are added to the Kubernetes cluster. While Container Observability collects a diverse set of telemetry data for analysis from open-source tools and Cloud infrastructure, they continue to be the long-term archival store.
Key aspects of the architecture:
Easy installation using Kubernetes and related popular tools like Helm.
No impact on the application workloads and worker nodes.
No changes to the application code and no added sidecars.
All connections to the Kubernetes API and the Cloud accounts originate only from the environment.
All credentials remain within Kubernetes and are not sent to the Container Observability SaaS servers.
Not personally identifiable, i.e., PII and PHI, data leaves the premises since the ingested operational data is primarily the output of system-level instrumentation.
You maintain control of your instrumented data (metrics, logs, traces, etc.), lowering expensive storage, and access costs and allowing data to be used for other purposes and by other tools.
The gateway pods communicate with Kubernetes, Cloud, Metrics, and Logs environments and send information in compressed and secure messages to the Container Observability SaaS backend. You can access the UI using a standard browser. All connections are outbound and use SSL/TLS. Container Observability emits highly enriched alerts that are sent to popular services such as email, PagerDuty, Slack, and ServiceNow.
Related topics: