What odigos-io/odigos shipped
Written by FoxPlug from the repository's own releases; not affiliated with Odigos. 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/odigos-io/odigos; Odigos 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 October 5, 2026
What shipped
- RenameAttribute now sorts its rename keys before building OTTL statements, so the Processor spec is deterministic across reconciles. Pull request #5975
- The RenameAttribute statement order fix was backported to the v1.36 release branch. Pull request #5983
- The RenameAttribute statement order fix was backported to the v1.37 release branch. Pull request #5984
- The RenameAttribute statement order fix was backported to the v1.38 release branch. Pull request #5985
- The actions GraphQL API now returns PII masking scopes, so a scoped PII masking action no longer appears to apply to all sources in the cluster. Pull request #5972
- OIDC authentication now also protects GraphQL, REST mutations, events, downloads and extension mounts, and a missing or empty OIDC secret no longer silently disables authentication. Pull request #6015
- Tail sampling gained opt-in noisy operations enforcement through sampling.tailSampling.noisyOperationsEnforcement with auto and always modes. Pull request #6003
- The autoscaler was migrated into the instrumentor; the autoscaler Go module is gone and Helm still ships an odigos-autoscaler Deployment at replicas 0. Pull request #5937
- The OSS webapp route /pipeline-collectors was renamed to /collectors. Pull request #5968
- Helm, GraphQL and config for live-traffic URL templatization learning were added, along with a cluster-local Redis named odigos-cache used as the shared cache. Pull request #5964
Why it matters
This week fixed a reconcile loop that kept the autoscaler at high CPU by making RenameAttribute OTTL statement order deterministic, and the fix was backported to the v1.36, v1.37 and v1.38 release branches. OIDC authentication now covers more of the API surface and a missing or empty OIDC secret no longer silently turns authentication off. Live-traffic URL templatization learning gained its config and shared cache, and tail sampling gained explicit noisy operations enforcement.
Changelog entry
- Fix: sort RenameAttribute rename keys so OTTL statement order is stable across reconciles Pull request #5975
- Fix: backport the RenameAttribute statement order fix to v1.36 Pull request #5983
- Fix: backport the RenameAttribute statement order fix to v1.37 Pull request #5984
- Fix: backport the RenameAttribute statement order fix to v1.38 Pull request #5985
- Fix: return PII masking scopes from the actions GraphQL API Pull request #5972
- Fix: close remaining OIDC authentication gaps in the frontend Pull request #6015
- Feat: opt-in noisy operations enforcement in tail sampling Pull request #6003
- Chore: migrate the autoscaler into the instrumentor Pull request #5937
- Rename the collectors route to /collectors Pull request #5968
- Feat: add live-traffic learning config and odigos-cache Pull request #5964
- Feat: append the unmatched-path exporter to the gateway traces pipeline Pull request #5967
- Fix: load the actions catalog in instrumentor.New Pull request #6022
RenameAttribute OTTL statement order is now deterministic, fixing a reconcile loop that kept the autoscaler at high CPU. Backported to v1.36, v1.37 and v1.38. OIDC now protects GraphQL, REST mutations, events, downloads and extension mounts.
This week: RenameAttribute now sorts its rename keys before building OTTL statements, so the Processor spec is deterministic across reconciles and the Action to Processor patch loop that kept the autoscaler at high CPU is fixed. The same fix was backported to the v1.36, v1.37 and v1.38 release branches. OIDC authentication now also protects GraphQL, REST mutations, events, downloads and extension mounts, and a missing or empty OIDC secret no longer silently disables authentication. The actions GraphQL API returns PII masking scopes. Tail sampling gained opt-in noisy operations enforcement. The autoscaler was migrated into the instrumentor. Live-traffic URL templatization learning gained its config and a shared cluster-local Redis cache.
Week of September 28, 2026
What shipped
- V1.38.0 released with an Instrumentation Agents page showing per-agent details and a Go offsets tab on enterprise clusters. Release
- Fixed enterprise release workflow to dispatch release PRs for stable versions, resolving a gap where v1.38.0 was not promoted to odigos-enterprise. Pull request #5961
- V1.39.0-pre1 released with operator version bump to v1.37.1 and certified operator catalog improvements. Release
- Fixed UI form handling so that setting sampling rules to 'All Operations' and scoped instrumentation rules to 'Entire Cluster' now properly clear previous values. Pull request #5954
- Merged scheduler into instrumentor, consolidating two components into one while keeping the scheduler deployment at zero replicas for backward compatibility. Pull request #5916
- Added release tracking for the odigos repository in Linear, matching the existing release pipeline for enterprise and agent projects. Pull request #5959
- Added Ruby 2.7.8 support through the ruby legacy distro with payload collection and head sampling capabilities. Pull request #5932
- Fixed SELinux volume mounting warnings in odiglet and data collection components to prepare for Kubernetes Enhancement Proposal 1710. Pull request #5950
- Exposed transaction limit and baseline saturation caps in GraphQL for better visibility into Insights learning constraints. Pull request #5931
- Applied eBPF log capture configuration for all distros instead of only language-specific ones. Pull request #5929
Why it matters
V1.38.0 is now available with new agent instrumentation visibility and enterprise Go offset management features. The release process improvements ensure better tracking and reliability across all odigos repositories. Several core architectural changes consolidate components and expand platform coverage.
Changelog entry
- Add Instrumentation Agents page showing per-agent details and Go offsets tab for enterprise clusters Release
- Add spec.collectors to connector CRD Release
- Bump operator to v1.37.1 Pull request #5864
- Add operator supported architecture labels to CSV Pull request #5952
- Fix sampling and instrumentation rule updates to properly clear fields with explicit null values Pull request #5954
- Add Ruby 2.7.8 support via ruby legacy distro Pull request #5932
- Merge scheduler into instrumentor component Pull request #5916
- Align odiglet and data collection SELinux options for KEP-1710 compatibility Pull request #5950
- Apply eBPF log capture configuration for all distros Pull request #5929
- Expose transaction limit and baseline saturation in GraphQL Pull request #5931
V1.38.0 ships Instrumentation Agents page with per-agent details and Go offsets management on enterprise clusters. v1.39.0-pre1 is out with operator and catalog improvements.
Odigos v1.38.0 is available with an Instrumentation Agents page displaying every injected agent and detailed Go offsets management for enterprise clusters. v1.39.0-pre1 brings operator enhancements and certified operator catalog improvements. This week also includes significant architectural work merging the scheduler into instrumentor and expanding Ruby support to version 2.7.8.
Week of September 21, 2026
What shipped
- The Insights GraphQL API now serves service guardrail recommendations with per-rule allowlists and live check counts. Pull request #5837
- Added an Instrumentation Agents page showing every agent the cluster injects, with per-agent details and a Go offsets diff tab on enterprise clusters. Pull request #5863
- InstrumentationRules created via the UI are now marked with managed-by ownership and exposed through a ManagedBy GraphQL enum. Pull request #5871
- Updated insights API models to drop the placeholder class and renumber database access and payload size attributes to match insights API 9.0.0. Pull request #5862
- Built static rsync without OpenSSL and IDN dependencies and bumped from 3.2.7 to 3.5.1 in odiglet. Pull request #5885
- Added payload collection to the insights profile. Pull request #5881
- Added k8s.node.name as a label to self metrics. Pull request #5860
- Removed unused SamplingSpec.Disabled in favor of per-rule disabled settings. Pull request #5882
- Stopped wiring odigosebpf into metrics pipelines and removed the JVM metrics map. Pull request #5805
- Removed the oTel collector release process from Odigos OSS. Pull request #5880
Why it matters
This week improves the Insights API capabilities with guardrail recommendations, adds visibility into instrumentation agents across the cluster, and clarifies ownership of configuration rules. The updates also streamline dependencies and align the codebase with the latest insights API specification.
Changelog entry
- The Insights GraphQL API now serves service guardrail recommendations in addition to attribute correlations, including their per-rule allowlists and live check counts. Pull request #5837
- Add an Instrumentation Agents page showing every agent the cluster's tier injects, with per-agent details and, on enterprise clusters, a Go offsets tab that diffs a pending offsets update before applying it. Pull request #5863
- InstrumentationRules created via the UI are now marked with odigos.io/managed-by=odigos-ui and expose a ManagedBy GraphQL enum for ownership presentation. Pull request #5871
- Updated insights API compatibility: dropped D6_attr_relations placeholder and renumbered D7/D8 to D6/D7 for
db_accessandpayload_size. Pull request #5862 - Added k8s.node.name as a label to self metrics. Pull request #5860
New week in Odigos: Insights now surfaces guardrail recommendations via GraphQL, Instrumentation Agents page shows cluster injection details, and InstrumentationRules track ownership.
This week's Odigos updates focus on observability insights and instrumentation visibility. The Insights GraphQL API now serves guardrail recommendations with live check counts. A new Instrumentation Agents page shows every agent injected by the cluster with per-agent details. InstrumentationRules now track ownership through managed-by labeling. Additional improvements include payload collection in the insights profile and updated metrics to include node names.
Week of September 14, 2026
What shipped
- Fixed missing Apply via UI buttons on recommendation cards that were not rendering in v1.37.0. Pull request #5843
- OpenShift odiglet now runs unprivileged by default, fixing API server rejection of the DaemonSet. Pull request #5832
- Insights guardrails now support attribute correlation rules scoped to transactions alongside per-service allowlists. Pull request #5827
- Ruby instrumentation falls back to otel-ebpf when an unsupported Ruby version is detected. Pull request #5831
- Profiling now has required capabilities to run unprivileged. Pull request #5821
- Findings now include a summary field. Pull request #5825
- URLTemplatization recommendation actions with empty fields now create proper config instead of being rejected. Pull request #5786
- Operator and components bumped to v1.35.3 with enterprise collector and agents added to preflight checks. Pull request #5833
- OpenShift preflight binary updated to version 1.21.0 to meet Red Hat requirements. Pull request #5849
- Documentation updated for non-root VM agent deployment and management. Pull request #5719
Why it matters
This week fixes several critical issues affecting recommendations UI rendering and OpenShift deployments, while expanding guardrails capabilities for transaction-scoped attribute correlation. The unprivileged container fixes ensure Odigos works properly in restricted OpenShift environments.
Changelog entry
- Fix(recommendations): serve canApplyViaUi so Apply via UI buttons render Pull request #5843
- Fix(openshift): run odiglet unprivileged by default Pull request #5832
- Feat(insights): transaction guardrails with attribute correlation Pull request #5827
- Chore: fallback to otel-ebpf if ruby version not supported Pull request #5831
- Fix(profiling): add required capabilities for running unprivileged Pull request #5821
- Feat: add summary to finding Pull request #5825
- Fix: create empty URLTemplatization config when action fields are omitted Pull request #5786
- Chore: bump operator and components to v1.35.3 Pull request #5833
- Chore: bump openshift preflight to 1.21.0 Pull request #5849
- Docs: update VM agent documentation for non-root deployment Pull request #5719
Fixed Apply via UI buttons on recommendations, unprivileged OpenShift odiglet, transaction-scoped guardrails, Ruby version fallback handling, and profiling capabilities. Several smaller fixes shipped too.
This week we fixed critical issues affecting the Odigos user experience and deployment reliability. The Apply via UI buttons on recommendation cards are now rendering properly, and OpenShift deployments work correctly with unprivileged odiglet containers. We've expanded guardrail capabilities with transaction-scoped attribute correlation, improved Ruby instrumentation with version fallback handling, and enhanced profiling to run unprivileged. Several additional fixes ensure URLTemplatization configs are created properly and findings include summaries.