Orchestrion, a compile-time auto-instrumentation tool for Go applications, is now generally available. It enables you to set up Datadog Application Performance Monitoring (APM) for your applications written in Go without any code changes. Orchestrion processes Go source code at compilation time and inserts instrumentation to produce Datadog APM traces, so that you don’t have to do it manually.
With Orchestrion now you can:
- Instrument your code and all supported dependencies, including the Go standard library resulting in richer traces
- Prevent gaps in traces created due to overlooked manual instrumentation
- Enable the Exploit Prevention capability of Datadog Application Security Management
To set up Datadog APM for your Go applications and to learn more about Orchestrion, check out the blog post or the documentation .
Highlights
As we declare v1.0.0, we are signaling that the overall API and experience of orchestrion is now deemed stable, and ready for use with production workloads. Orchestrion's versioning scheme adheres to semantic versioning.
Starting with release v1.0.0, the //dd:ignore directive was renamed to //orchestrion:ignore. To ensure a smooth transition, the //dd:ignore directive still applies, although it emits a warning indicating it should be renamed.
Release v1.0.0 also marks the introduction of a completely re-designed orchestrion pin mechanism, which enables orchestrion to discover and use integrations from any Go package. In the coming few releases, we will be moving all existing built-in integrations over to gopkg.in/DataDog/dd-trace-go.v1, making it easier than ever to control exactly what instrumentation is added by Orchestrion; and making it possible for third-party vendors to offer their own instrumentation if they wish to.
A new github.com/DataDog/orchestrion/runtime/built package exposes a built.WithOrchestrion constant that can be used to implement a runtime check to ensure the application was built using orchestrion.
What's Changed
- fix: fingerprint mismatch when using
-tagsthat affect injected packages by @RomainMuller in #429
Full Changelog: v1.0.0...v1.0.1
