Shipped · Observability

What odigos-io/odigos shipped

The public repository of Odigos · github.com/odigos-io/odigos

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

Or Use it as a GitHub Action

See the update FoxPlug writes for odigos, free

Week of October 26, 2026

What shipped

Why it matters

This week broadened the destination catalogue considerably, with self-hosted storage and observability backends and several managed cloud services added for traces, metrics and logs. Users also get a simpler interrogation install, Ruby 4.0 support, and patch releases that fix known vulnerabilities in the Node.js, PHP and Python community agents.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: Apache SkyWalking, Apache Cassandra, Amazon Data Firehose, Microsoft Sentinel, Azure Event Hubs, Azure Data Explorer, PostHog, VictoriaLogs, VictoriaTraces and Google Managed Prometheus are now named destinations. Plus simpler interrogation installs, Ruby 4.0 support a

Post for LinkedIn

This week added many new named destinations: Apache SkyWalking and Apache Cassandra for self-hosted setups, Amazon Data Firehose, Microsoft Sentinel, Azure Event Hubs and Azure Data Explorer for Azure, PostHog, VictoriaLogs, VictoriaTraces and Google Managed Prometheus. Local File Archive, Generic Syslog and OpenStack Swift S3 Gateway also arrived, and Google Cloud Storage is now exposed and validated. Installing interrogation now enables insights and profiling by default, Ruby 4.0 workloads can use the ruby-community distro, and patch releases v1.36.7, v1.37.5 and v1.38.4 fix known vulnerabilities in the Node.js, PHP and Python community agents.

Week of October 19, 2026

What shipped

Why it matters

This week adds a dedicated Interrogations page and settings for it, and makes it easier to filter and page interrogation transactions. Token expiry is now surfaced in the UI, kernel traces can be turned on as an instrumentation rule from the UI, and custom probes carry notes, category and added time. Several fixes and packaging changes are also included, such as sorting merged URL templates by segment specificity, keyless signing of release checksums, and re-pinning the php-community agent to v0.9.0 across release branches.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: a new Interrogations page in the UI, filterable and pageable interrogation transactions, and read-only AI Interrogation settings. Also a token expiry warning modal, a kernel traces rule you can add from the UI, and notes and category on custom probes.

Post for LinkedIn

This week Odigos gained an Interrogations page in the UI, with a navbar entry that appears only when interrogation is enabled, plus a query that lists interrogated sources and their transaction counts. Interrogation transactions can now be filtered and paged. Settings shows the AI Interrogation fields as read-only. A modal warns when the API token is about to expire or has expired. A kernel traces instrumentation rule can be added from the UI. Custom probes on an InstrumentationRule accept optional notes, a category and an addedAt time, and the rule drawer shows that metadata along with a C++ probes table. Merged URL templates are now sorted by segment specificity, release checksums are signed keyless, and the yum repo install snippet enables gpgcheck.

Week of October 12, 2026

What shipped

Why it matters

This week hardened the shipped images and dependencies against a batch of Go standard library and module advisories across the v1.36, v1.37 and v1.38 lines, and moved interrogation and call-trie correlation into the insights service. It also removed the trace correlations feature outright, so anyone relying on the serviceio connector or the gateway tracecorrelations pipeline should expect that surface to be gone. A legacy Splunk destination was fixed so the gateway config loads again.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: interrogation and call-trie correlation moved into the insights service, trace correlations (service I/O) removed, legacy Splunk destinations fixed to use OTLP, and Go and x/net bumps across release lines to clear stdlib advisories.

Post for LinkedIn

This week in Odigos: interrogation moved into the insights pod along with call-trie correlation, and the gateway no longer wires the call-trie traces exporter. The trace correlations (service I/O) feature was removed, including the serviceio connector, the gateway tracecorrelations pipeline, its metrics store and the frontend surface. A legacy Splunk destination now reuses the existing Splunk OTLP/HTTP configuration so the gateway config loads. On the security side, Go was bumped to 1.26.9 in the odiglet base and builders, and golang.org/x/net to v0.60.0, with backports across the v1.36, v1.37 and v1.38 lines. A GraphQL API for workload URL templatization also landed.

Week of October 5, 2026

What shipped

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

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

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.

Post for LinkedIn

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

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

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

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.

Post for LinkedIn

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

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

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

New week in Odigos: Insights now surfaces guardrail recommendations via GraphQL, Instrumentation Agents page shows cluster injection details, and InstrumentationRules track ownership.

Post for LinkedIn

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

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

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

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.

Post for LinkedIn

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.

Weeks with too little public activity are left out rather than filled in. Last updated 2026-11-03.

Is this your repo? Ask us to remove this page.