Inconsistent patterns
Different teams, frameworks and vendor SDKs lead to inconsistent instrumentation across your codebase.
OllyGarden Rose
OllyGarden Rose adds missing instrumentation, migrates vendor SDKs to OpenTelemetry®, reviews what’s already there for gaps and inconsistencies, and fixes the issues you select.
Across your repositories: autonomously in the background, locally on your machine, or inside your favorite coding agent.
Minimum Viable Instrumentation (MVI)New
Rose can make your currently unobservable services observable.
The problem
An observability engineer knows exactly what good instrumentation should look like. What they cannot do is sit with every team, in every repository, on every pull request.
Rose is the telemetry expert for all your teams.
Different teams, frameworks and vendor SDKs lead to inconsistent instrumentation across your codebase.
Telemetry without business context makes it harder to understand and resolve issues.
New services and features often ship with little or no instrumentation.
AI coding agents can introduce gaps, duplication or other poor instrumentation practices.
Meet Rose
Adds missing instrumentation and expands coverage in already instrumented services with targeted business context.
Moves vendor-specific or custom instrumentation to OpenTelemetry.
Continuously reviews the whole codebase in the background as your code evolves.
Turns selected findings into pull requests your team reviews and controls.
How Rose works
Rooted in OpenTelemetry. Curated by OllyGarden. Rose connects patterns across your services with OpenTelemetry standards, OllyGarden’s instrumentation expertise, and your organization’s context and skills.
Explore the open source skills behind RoseOrg context and skills feed OllyGarden Rose. Rose opens a pull request against your service. Your service sends telemetry to the OpenTelemetry Collector, which forwards it to your observability backend and, optionally, to OllyGarden Insights. Insights findings flow back into Rose.
Rose reviews your code using your org context and skills, plus Insights findings from your telemetry when available.
Rose opens a pull request to fix the instrumentation at the source.
Your team reviews and merges it, new telemetry is sent, and the loop starts over.
New in Rose
For repositories with no instrumentation, Rose creates an OpenTelemetry baseline, combining zero-code instrumentation with the business context needed to investigate problems.
Point Rose at a repository with no instrumentation.
One repository at a time, or many at once.
Your team reviews it and decides what ships.
POST /orders
↳ SELECT orders
↳ POST payments-api
↳ publish order.created
You can see the request was slow, but not the checkout outcome, payment method, or number of items in the cart.
POST /orders
↳ checkout.submit MANUAL
↳ SELECT orders
↳ POST payments-api
↳ publish order.created
checkout.result, payment.method, cart.item_count
Useful coverage and meaningful context, with less unnecessary telemetry.
Rose in Action
Watch OllyGarden Rose in action and see how it turns service analysis into practical OpenTelemetry recommendations your team can use.
Improve your team
Telemetry that explains why, not just what.
Every team gets expert-level instrumentation. Engineers stay in control.
Useful coverage without unnecessary telemetry.
Spans/secfrom 14 to 8
I reduced the span rate from 14 spans/sec to 8 spans/sec, lowering telemetry volume.

Rob Chapman
Founder / Observability Consultant
Juraci gave me a demo of Rose yesterday. I left the call excited. Wired it up to my repo, ran it on a project I suspected had issues, and was gobsmacked. It found a real instrumentation problem on the first pass, it then raised a perfect PR to fix it.
I want to be embarrassed about my own instrumentation.
I am not though. I am excited for the possibilities, even if that means I need a new career.
Rob Chapman, Founder / Observability Consultant
Testimonial 1 of 3: Rob Chapman, Founder / Observability Consultant
We care about security
Works with any observability backend. We don’t replace your observability backend.
Tuned for Go, Java, JavaScript/TypeScript and Python, and runs on other languages too.
Every run happens in an environment created for that run and destroyed when it ends.
Every change arrives as a pull request your team reviews and controls.
The sandbox is torn down with everything in it when the run finishes.
EU-only processing and zero data retention with AI providers are available as add-ons.
Get Started
All plans include the full codebase scan, the instrumentation dashboard, and access to the REST API (e.g. via OllyGarden CLI). Open Source access is granted upon review.
No credit card required
Contact us to start
Access granted upon request
Common questions about what Rose does, how it treats your code, and how it fits your observability stack.
For repositories with no instrumentation, Rose creates an OpenTelemetry baseline, combining zero-code instrumentation with the business context needed to investigate problems, and delivers it as a pull request.
No. Rose works on its own. With Insights, Rose also uses findings from your production telemetry.
Rose is tuned for Go, Java, JavaScript/TypeScript and Python, and runs on other languages too.
No. Rose never merges or writes to your default branch. Every change arrives as a pull request your team reviews.
Each run happens in an isolated, credential-free sandbox that is destroyed when the run ends. Rose never stores a copy of your repository.
No. Rose works with any observability backend and improves the telemetry you send to it.
What is telemetry quality?Compare Insights and Rose pricingRead the FAQ
Start with the right instrumentation. Improve what you already have.