I built this after running into the same wall repeatedly: instrumenting applications sometimes requires a single agent that does it all. Today, we can use Agents (literally) that understands our needs.
The idea is that we support it all. Agents know all languages, it's about prompting the right prompt.
The approach for no-SDK languages is a small HTTP sidecar. The legacy process calls it with a simple POST, the sidecar translates to OTLP and forwards to Elastic APM. No rewrite, no upgrade — COBOL emitting spans in the same trace as your modern services.
The other thing I wanted to fix: generic agents instrument what the SDK detects (HTTP calls, DB queries). They don't read your code, so spans carry status codes but not fraud scores or order values. This reads first. Simple things should be simple.
I built this after running into the same wall repeatedly: instrumenting applications sometimes requires a single agent that does it all. Today, we can use Agents (literally) that understands our needs.
The idea is that we support it all. Agents know all languages, it's about prompting the right prompt.
The approach for no-SDK languages is a small HTTP sidecar. The legacy process calls it with a simple POST, the sidecar translates to OTLP and forwards to Elastic APM. No rewrite, no upgrade — COBOL emitting spans in the same trace as your modern services.
The other thing I wanted to fix: generic agents instrument what the SDK detects (HTTP calls, DB queries). They don't read your code, so spans carry status codes but not fraud scores or order values. This reads first. Simple things should be simple.
Happy to answer questions!