What coroot/coroot shipped
Written by FoxPlug from the repository's own releases; not affiliated with Coroot. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/coroot/coroot; Coroot did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.
Get a weekly update like this for your product, free
Week of November 2, 2026
What shipped
- GOMEMLIMIT is now set automatically from the container memory limit. Pull request #1108
- Version 1.29.2 was released with the alerting rule config fix, JSON encoding error checks, and several code cleanups. Release
- Alerting rule for and keepFiringFor in config now accept 0s. Pull request #1090
- The Prometheus series endpoint now returns the actual error. Pull request #1102
- Custom Prometheus headers coming from the environment no longer cause a panic. Pull request #1103
- Label pair count and key index are now bounded in chunk v4 encoding. Pull request #1104
- Vulnerable transitive dependencies were bumped to patched versions. Pull request #1105
- A golangci-lint config and CI check were added so new code is checked by the same rules. Pull request #1098
- Errors returned by JSON encoding are now checked. Pull request #1091
- Perfsprint lint issues were fixed. Pull request #1094
Why it matters
This week brings two user-facing changes: GOMEMLIMIT is set from the container memory limit, and alerting rules can set for and keepFiringFor to 0s. Several fixes harden Prometheus integration, chunk v4 encoding and JSON encoding, and the 1.29.2 release collects the alerting config fix and cleanups. The golangci-lint config with a CI check keeps new code under the same rules going forward.
Changelog entry
- Feat: set GOMEMLIMIT automatically from the container memory limit Pull request #1108
- Allow 0s for alerting rule for and keepFiringFor in config Pull request #1090
- Release: 1.29.2 Release
- Fix: do not panic when custom Prometheus headers come from the environment Pull request #1103
- Fix: return the actual error from the Prometheus series endpoint Pull request #1102
- Fix: bound label pair count and key index in chunk v4 encoding Pull request #1104
- Fix: check errors returned by JSON encoding Pull request #1091
- Chore: bump vulnerable transitive dependencies to patched versions Pull request #1105
- Chore: do not shadow predeclared identifiers Pull request #1093
- Chore: remove ineffectual assignments Pull request #1092
- Chore: fix perfsprint lint issues Pull request #1094
- Ci: add golangci-lint config and CI check Pull request #1098
Coroot 1.29.2 is out. GOMEMLIMIT is now set automatically from the container memory limit, alerting rules accept 0s for for and keepFiringFor, and fixes cover Prometheus headers and series errors, chunk v4 encoding, and JSON encoding. New code is now checked by golangci-lint in C
Coroot 1.29.2 is released. GOMEMLIMIT is now set automatically from the container memory limit, so memory behavior follows the limit you already configure. Alerting rules now accept 0s for for and keepFiringFor in config. The release also includes fixes for custom Prometheus headers coming from the environment, the actual error returned by the Prometheus series endpoint, bounded label pair count and key index in chunk v4 encoding, and checked errors from JSON encoding. Vulnerable transitive dependencies were bumped to patched versions, and a golangci-lint config with a CI check was added so all new code is checked by the same rules.
Week of October 26, 2026
What shipped
- Version 1.29.0 was released with eBPF disk I/O profiles and pod grouping by DisaggregatedSet and LeaderWorkerSet. Release
- Version 1.29.1 was released and attributes database metrics to instances by
container_id. Release - Pods are now grouped by DisaggregatedSet and LeaderWorkerSet, covering llm-d and multi-node vLLM. Pull request #1079
- Database metrics are attributed to instances by
container_id. Pull request #1085 - EBPF disk I/O profiles were added. Pull request #1082
Why it matters
This week brought a new minor release with eBPF disk I/O profiles and pod grouping for DisaggregatedSet and LeaderWorkerSet, aimed at llm-d and multi-node vLLM setups. A patch release followed that attributes database metrics to instances by container_id, tightening how database activity is matched to the instances that run it. Together these give users more visibility into disk I/O and clearer per-instance database metrics.
Changelog entry
- Release 1.29.0: added eBPF disk I/O profiles and pod grouping by DisaggregatedSet and LeaderWorkerSet (llm-d, multi-node vLLM). Release
- Release 1.29.1: attribute database metrics to instances by
container_id. Release - Added eBPF disk I/O profiles. Pull request #1082
- Group pods by DisaggregatedSet and LeaderWorkerSet for llm-d and multi-node vLLM. Pull request #1079
- Attribute database metrics to instances by
container_id. Pull request #1085
Coroot 1.29.0 adds eBPF disk I/O profiles and groups pods by DisaggregatedSet and LeaderWorkerSet for llm-d and multi-node vLLM. 1.29.1 follows, attributing database metrics to instances by container_id.
Coroot 1.29.0 is out with eBPF disk I/O profiles and pod grouping by DisaggregatedSet and LeaderWorkerSet, covering llm-d and multi-node vLLM. Coroot 1.29.1 follows and attributes database metrics to instances by container_id, so database activity lines up with the instances running it. See the changelog for details.
Week of October 19, 2026
What shipped
- Released 1.28.1, which skips corrupted metrics cache chunks instead of failing the whole query. Release
- Released 1.28.0, which disables SLO tracking and alerting for job-like apps, groups KServe InferenceService pods into a single application, and groups pods by a non-controller owner. Release
- Fixed a database connection leak in check config reads, where failing to scan or decode a configuration left query rows open and could exhaust the connection pool. Pull request #1048
- Added grouping of pods by a non-controller owner. Pull request #1063
- Added grouping of KServe InferenceService pods into a single application. Pull request #1062
- Disabled SLO tracking and alerting for job-like apps. Pull request #1061
- Changed alerting to count events within KeepFiringFor and regroup unresolved Kubernetes events. Pull request #1064
Why it matters
This week brings a patch release that keeps metrics queries working when cached chunks are corrupted, and a minor release that changes how pods are grouped into applications for KServe and non-controller owners. It also removes SLO tracking and alerting for job-like apps, and fixes a connection leak in check config reads that could exhaust the pool after repeated failures.
Changelog entry
- 1.28.1: skip corrupted metrics cache chunks instead of failing the whole query. Release
- 1.28.0: disable SLO tracking and alerting for job-like apps. Release
- Close check config rows on errors to avoid retaining pooled connections. Pull request #1048
- Group pods by a non-controller owner. Pull request #1063
- Group KServe InferenceService pods into a single application. Pull request #1062
- Count alert events within KeepFiringFor and regroup unresolved Kubernetes events. Pull request #1064
Coroot 1.28.1 skips corrupted metrics cache chunks instead of failing the whole query. 1.28.0 groups KServe InferenceService pods and pods under non-controller owners into single applications, and disables SLO tracking for job-like apps.
Coroot 1.28.1 is out: corrupted metrics cache chunks are now skipped instead of failing the whole query. Coroot 1.28.0 disables SLO tracking and alerting for job-like apps, groups KServe InferenceService pods into a single application, and groups pods by a non-controller owner. A database fix closes check config rows on errors, so repeated failed reads no longer keep pooled connections open. Alerting also now counts events within KeepFiringFor and regroups unresolved Kubernetes events.
Week of October 12, 2026
What shipped
- Added support for Amazon ECS on EC2. Pull request #1053
- PromQL queries in dashboards and alerting now take a scope and default to global. Pull request #1060
- MySQL monitoring now shows a hint for enabling
performance_schema. Pull request #1058 - Raw SLIs are now loaded only for the last alert window. Pull request #1054
- Fixed service account creation failing when the browser autofills the email field. Pull request #1055
Why it matters
This week adds Amazon ECS on EC2 support, widening where the project can collect data. Dashboards and alerting got scoped PromQL queries that default to global, which changes how queries are resolved. MySQL users get a clearer path to enabling performance_schema, and two fixes reduce friction in alerts and service account creation.
Changelog entry
- Release 1.27.4: scoped PromQL queries, MySQL
performance_schemahint, raw SLI loading for the last alert window only, and a service account creation fix. Release - Release 1.27.3: add support for Amazon ECS on EC2. Release
- Add support for Amazon ECS on EC2. Pull request #1053
- Dashboards and alerting: add a scope to PromQL queries, defaulting to global. Pull request #1060
- MySQL: add a hint for enabling
performance_schema. Pull request #1058 - Constructor: load raw SLIs only for the last alert window. Pull request #1054
- Fix service account creation failing when the browser autofills the email field. Pull request #1055
Coroot 1.27.3 adds support for Amazon ECS on EC2. 1.27.4 lets dashboards and alerting set a scope on PromQL queries, defaulting to global, and adds a MySQL hint for enabling performance_schema. Also fixed: service account creation with autofilled email fields.
Two releases this week. 1.27.3 adds support for Amazon ECS on EC2. 1.27.4 lets dashboards and alerting set a scope on PromQL queries, defaulting to global, and adds a hint for enabling performance_schema in MySQL monitoring. It also loads raw SLIs only for the last alert window and fixes service account creation failing when the browser autofills the email field.
Week of October 5, 2026
What shipped
- Testing Slack, MS Teams, and webhook integrations now sends a test alert. Pull request #1044
- Released 1.27.2 with the notification test alert, WAL mode for the query state SQLite database, and a release workflow change to skip npm publish when the version is already published. Release
- The query state SQLite database now opens in WAL mode with synchronous=NORMAL. Pull request #1051
- Released 1.27.1 with docs for RHEL 7 and CentOS 7 support and the minimum kernel version, the minimum supported Postgres version stated on the Postgres page, a profiling fix for time range selection on the chart, and multi-cluster external service resolution. Release
- Trace tools now fall back to eBPF spans when there are no OpenTelemetry traces. Pull request #1042
- Multi-cluster now resolves external services to services on hosts and cloud instances of member projects. Pull request #1041
- Dropped read-only and do-not-check-slo flags removed from the docs. Pull request #1039
- The release workflow now skips npm publish if the version is already published. Pull request #1043
Why it matters
This week brings a test alert for Slack, MS Teams, and webhook integrations, so notification setup can be verified. The query state SQLite database opens in WAL mode and trace tools fall back to eBPF spans when OpenTelemetry traces are absent. Multi-cluster resolves external services to services on hosts and cloud instances of member projects, and the docs drop read-only and do-not-check-slo flags that are no longer in the code.
Changelog entry
- Release 1.27.2 Release
- Notifications: send a test alert when testing Slack, MS Teams, and webhook integrations Pull request #1044
- Cache: open the query state SQLite database in WAL mode with synchronous=NORMAL Pull request #1051
- Ci: skip npm publish in the release workflow if the version is already published Pull request #1043
- Release 1.27.1 Release
- Mcp: fall back to eBPF spans in the trace tools when there are no OpenTelemetry traces Pull request #1042
- Multi-cluster: resolve external services to services on hosts and cloud instances of member projects Pull request #1041
- Remove dropped read-only and do-not-check-slo flags from docs Pull request #1039
Coroot 1.27.2 is out. Testing Slack, MS Teams, and webhook integrations now sends a test alert. The query state SQLite database opens in WAL mode. Trace tools fall back to eBPF spans when there are no OpenTelemetry traces. Docs drop read-only and do-not-check-slo flags.
Coroot 1.27.2 is out. Testing Slack, MS Teams, and webhook integrations now sends a test alert, so notification setup can be verified. The query state SQLite database opens in WAL mode with synchronous=NORMAL. Trace tools fall back to eBPF spans when there are no OpenTelemetry traces. Multi-cluster resolves external services to services on hosts and cloud instances of member projects. The docs drop the read-only and do-not-check-slo flags that are no longer in the code. 1.27.1 also updated RHEL 7 and CentOS 7 support notes, stated the minimum supported Postgres version on the Postgres page, and fixed time range selection on the profiling chart.
Week of September 28, 2026
What shipped
- Release 1.27.0 adds a new Topology mode to the Service Map that displays applications and dependencies as an interactive graph with hover-based connection highlighting and key metrics. Release
- The Service Map now includes interactive graph mode, a forced-layout chart visualization for exploring service dependencies in complex environments. Pull request #1029
- Fixed time range selection on the profiling chart. Pull request #1037
- Logs filtering by SeverityText now uses the primary key for improved performance. Pull request #1030
- Incidents now tolerate corrupted rows and skip database data in recording rules worlds. Pull request #1031
- Documentation updated to specify Postgres 10 as the minimum supported version. Pull request #1035
- Documentation clarified RHEL 7 and CentOS 7 support along with the actual minimum kernel version requirement. Pull request #1034
Why it matters
Version 1.27.0 introduces a major visualization improvement for the Service Map with the new Topology mode, making it easier to understand service dependencies in complex environments. Several bug fixes and documentation updates improve reliability and clarity for users operating Coroot with specific platform requirements.
Changelog entry
- New Topology mode for Service Map displays applications and dependencies as interactive graph Release
- Service Map interactive graph mode with forced-layout chart visualization Pull request #1029
- Fixed time range selection on profiling chart Pull request #1037
- Logs filtering by SeverityText now uses primary key Pull request #1030
- Incidents tolerate corrupted rows and skip DB data in recording rules worlds Pull request #1031
- Documentation: Postgres minimum version is 10 Pull request #1035
- Documentation: RHEL 7 and CentOS 7 support with minimum kernel version details Pull request #1034
Coroot 1.27.0 is out. The Service Map now has a Topology mode that visualizes applications and dependencies as an interactive graph. Hover over services to highlight connections and see metrics.
Coroot 1.27.0 is now available. We've added a new Topology mode to the Service Map that renders applications and their dependencies as an interactive graph visualization. Hover over a service to highlight its connections and view key metrics alongside. This makes exploring complex service architectures much more intuitive. We also fixed time range selection in profiling charts and optimized log filtering with primary keys.
Week of September 21, 2026
What shipped
- Version 1.26.8 released with service accounts and user API keys for programmatic access to the MCP endpoint and API. Release
- Service accounts and user API keys added for programmatic access to the MCP endpoint and the API. Pull request #1024
- Service accounts documented in the operator reference and Authentication page. Pull request #1025
- Operator CR example for service accounts added to the MCP page. Pull request #1026
- OpenTelemetry SDK overhead benchmarks documented on the Performance Impact page. Pull request #1020
- Postgres and MongoDB instrumentation benchmarks added to performance documentation. Pull request #1018
- C++ added to the OpenTelemetry SDK overhead benchmark documentation. Pull request #1028
- Release artifact retention changed from 90 days to one day. Pull request #1027
Why it matters
Coroot 1.26.8 introduces service accounts and API keys for programmatic access, enabling automation and integration with other systems. This release also expands performance documentation with comprehensive instrumentation benchmarks across multiple databases and SDKs, helping users understand the overhead impact of monitoring their infrastructure.
Changelog entry
- Add service accounts and user API keys for programmatic access to the MCP endpoint and the API Release
- Docs: add OpenTelemetry SDK overhead benchmarks to Performance Impact page Pull request #1020
- Docs: add Postgres and MongoDB instrumentation benchmarks Pull request #1018
- Docs: add C++ to the OpenTelemetry SDK overhead benchmark Pull request #1028
- Docs: describe service accounts in the operator reference and Authentication page Pull request #1025
- Docs: add the operator CR example for service accounts to the MCP page Pull request #1026
- CI: keep release artifacts for one day instead of 90 Pull request #1027
Coroot 1.26.8 is out with service accounts and API keys for programmatic access, plus expanded performance benchmarks for Postgres, MongoDB, and OpenTelemetry SDKs.
Coroot 1.26.8 brings service accounts and user API keys for programmatic access to the MCP endpoint and API, enabling better automation workflows. We've also significantly expanded our performance documentation with benchmarks for MySQL, Postgres, MongoDB instrumentation, and OpenTelemetry SDK overhead across multiple languages including C++. These additions help teams make informed decisions about monitoring impact.
Week of September 14, 2026
What shipped
- Released 1.26.7 fixing TLS connections to ClickHouse when routing through a remote Coroot. Release
- Released 1.26.6 adding integrations for OCI MySQL HeatWave, PostgreSQL, and OCI Cache. Release
- Released 1.26.4 with GCP Cloud SQL and Memorystore integrations, WebSocket tunneling for ClickHouse, and improved caller reporting in the API. Release
- Released 1.26.2 with RDS and ElastiCache support including logs display, node page fixes, engine/version details, and Valkey cluster support. Release
- Released 1.26.1 with PostgreSQL vacuum horizon attribution, configurable default time range, AWS IAM role auth, and cluster-agent metrics documentation. Release
- Released 1.26.3 applying application selectors to Kubernetes event alerts. Release
- Released 1.26.5 bounding MCP response sizes and requiring full app/node identifiers. Release
- Added MySQL instrumentation benchmark documentation to the Performance Impact page. Pull request #1016
Why it matters
Five releases in one week bring cloud platform integrations (OCI, GCP, AWS), critical infrastructure fixes for remote Coroot connectivity, and expanded managed database support across RDS, ElastiCache, and Cloud services. The week represents significant expansion of Coroot's multi-cloud observability capabilities.
Changelog entry
- 1.26.7: Fix TLS to ClickHouse when connecting through a remote Coroot Release
- 1.26.6: Add OCI integration for MySQL HeatWave, PostgreSQL, and OCI Cache Release
- 1.26.5: Bound MCP response sizes and require full app/node IDs Release
- 1.26.4: Add GCP integrations (Cloud SQL, Memorystore), WebSocket ClickHouse tunneling, and report real callers in API clients field Release
- 1.26.3: Apply application selector to Kubernetes event alerts Release
- 1.26.2: Show RDS instance logs, fix node pages for RDS and ElastiCache, display engine/version/address/instance type, add Valkey ElastiCache support Release
- 1.26.1: Attribute PostgreSQL held vacuum horizons, delete alert notifications with projects, configurable default time range, AWS IAM role auth, document cluster-agent metrics Release
- Add MySQL instrumentation benchmark to Performance Impact documentation Pull request #1016
Five releases this week: OCI and GCP integrations, RDS/ElastiCache support, remote Coroot TLS fixes, and WebSocket ClickHouse tunneling. Cloud observability expanding across major platforms.
Shipped five releases of Coroot this week spanning major cloud observability improvements. Added first-class support for OCI (MySQL HeatWave, PostgreSQL, Cache), GCP (Cloud SQL, Memorystore), and AWS (RDS, ElastiCache) with managed database details on node pages. Fixed critical TLS routing through remote Coroot instances and switched to WebSocket tunneling for ClickHouse. Also improved Kubernetes alert filtering and PostgreSQL vacuum horizon tracking.