eMudhra – Coralogix Full Upgrade Guide
Blog post from Coralogix
Following the compromise of private keys for eight eMudhra intermediate CA certificates on October 20, 2026, Coralogix states that its platform, endpoints, and internal services are unaffected because they do not use eMudhra or emSign certificates. As a precaution, the company recommends customers include upgrades to their Coralogix integrations in normal maintenance, with priorities ranging from low to medium and target releases including the Kubernetes OpenTelemetry Helm chart 0.0.362, OpenTelemetry Collector Contrib 0.163.2, Coralogix Operator 2.16.0, Terraform provider 3.22.0, cx-cli 0.1.28, Lambda telemetry exporter layer 39, supervised collector and profiler 0.17.0, CDOT 0.5.18, AWS Shipper 1.4.20, and updated Python, Node.js, and Java Lambda layers. The guidance explains how users can identify deployed versions and outlines potential compatibility issues and telemetry changes across upgrade paths, such as renamed or removed configuration settings, changed metric labels and names, updated logging and tracing behavior, altered Terraform resource handling, and special considerations for legacy layers, FIPS deployments, AWS GovCloud, custom endpoints, and older operating system or runtime versions.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| OpenTelemetry | 32 | 646 | 129 | 53 | -9% |
| Serverless | 24 | 935 | 254 | 92 | -23% |
| Kubernetes | 18 | 4,045 | 384 | 100 | -7% |
| Observability | 3 | 2,250 | 553 | 165 | -19% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.