Inconsistent patterns
Different teams, frameworks and vendor SDKs lead to inconsistent instrumentation across your codebase
OllyGarden Rose
Your teams and their agents write the code.Rose gets the instrumentation right.
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
Why good instrumentation is so hard to get right
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.
Low-value telemetry
Telemetry without business context makes it harder to understand and resolve issues.
Missing instrumentation
New services and features often ship with little or no instrumentation.
Agent-generated mistakes
AI coding agents can introduce gaps, duplication or other poor instrumentation practices.
Meet Rose
What Rose does
Instrument
Adds missing instrumentation and expands coverage in already instrumented services with targeted business context.
Migrate
Moves vendor-specific or custom instrumentation to OpenTelemetry.
Review
Continuously reviews the whole codebase in the background as your code evolves.
Fix
Turns selected findings into pull requests your team reviews and controls.
How Rose Works
Instrumentation that improves with your code
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.
OllyGarden RoseAI instrumentation agent
2open pull request
Your service
13telemetry
Org context & skills
CollectorOpenTelemetry Collector
telemetryYour observability backend
telemetry
OllyGarden InsightsOptional
Review
Rose reviews your code using your org context and skills, plus Insights findings from your telemetry when available.
Fix
Rose opens a pull request to fix the instrumentation at the source.
Merge
Your team reviews and merges it, new telemetry is sent, and the loop starts over.
New in Rose
Minimum Viable Instrumentation
For repositories with no instrumentation, Rose creates an OpenTelemetry baseline, combining zero-code instrumentation with the business context needed to investigate problems.
Your repository
Point Rose at a repository with no instrumentation.
Rose adds MVI
One repository at a time, or many at once.
Pull request
Your team reviews it and decides what ships.
- POST /orders
- SELECT orders
- repository.saveAll
- Session.persist
- INSERT order_items
- Session.persist
- INSERT order_items
- Session.persist
- INSERT order_items
- Session.persist
- INSERT order_items
- POST payments-api
- publish order.created
... repeated for each item
- POST /orders
- checkout.submit
- SELECT orders
- order_items.persist_batch
- POST payments-api
- publish order.created
CHECKOUT CONTEXT: result / payment method / item count
Batch span / example attributes
records.attempted, records.written, outcome
Improve your team
What changes for your teams
Resolve incidents faster
Telemetry that explains why, not just what.
OpenTelemetry expertise for every team
Every team gets expert-level instrumentation. Engineers stay in control.
Pay for signal, not noise
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.
What teams say about Rose
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
Security and control
Run Rose your way
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.
- Run locally
- Self-host
- Bring your own key
Isolated, credential-free sandbox
Every run happens in an environment created for that run and destroyed when it ends
Never merges or writes to your default branch
Every change arrives as a pull request your team reviews and controls.
Never stores a copy of the repo
The sandbox is torn down with everything in it when the run finishes.
Enterprise
EU-only processing and zero data retention with AI providers are available as add-ons.
Get Started
Choose how you want to use Rose
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.
Free
No credit card required
- Up to 5 repositories included
- Weekly automatic instrumentation review
- Instrumentation dashboard
- REST API and CLI access
- Custom review instructions
- Additional repositories for $5/month each
Enterprise
Contact us to start
- Everything in Free
- On-demand instrumentation reviews
- Autonomous instrumentation improvements
- Agentic Instrumentation (MVI)
- Team integrations for Slack, Discord, and more
- Priority support with a dedicated channel
- Zero data retention with AI providers (add-on)
Open Source
Access granted upon request
- Everything in Free
- Unlimited public repositories
- Priority access for CNCF projects
Learn more
See Rose at work
- Case study · Digital healthA digital-health platform: the PII leak was a logger settingPersonal data in 1 in 6 services traced to one ORM logging setting, logs with no severity at all, one worker writing most of the logs, and auth tokens Rose found in a day.Read the Story
- BlogMeet Rose: OllyGarden's AI Instrumentation AgentImagine the perfect observability world: There is an incident, the on-call team gets paged in the middle of the night, wakes up and thanks to your telemetry, resolves it fast.Read Article
- BlogTeach Your Coding Agent OpenTelemetryWe’re releasing our Agent Skills for OpenTelemetry as a mature, open source set: 14 skills that give any coding agent accurate, current OpenTelemetry knowledge.Read Article
- BlogHow to Name Your SpansGood span names make traces readable. Learn the {verb} {object} pattern for naming OpenTelemetry spans and avoid the most common naming mistakes.Read Article
Frequently Asked Questions
Common questions about what Rose does, how it treats your code, and how it fits your observability stack.
What is Minimum Viable Instrumentation (MVI)?
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.
Do I need OllyGarden Insights to use Rose?
No. Rose works on its own. With Insights, Rose also uses findings from your production telemetry.
Which languages does Rose support?
Rose is tuned for Go, Java, JavaScript/TypeScript and Python, and runs on other languages too.
Will Rose change my code without approval?
No. Rose never merges or writes to your default branch. Every change arrives as a pull request your team reviews.
What happens to my code?
Each run happens in an isolated, credential-free sandbox that is destroyed when the run ends. Rose never stores a copy of your repository.
Does Rose replace my observability backend?
No. Rose works with any observability backend and improves the telemetry you send to it.
Telemetry your teams andtheir agents can trust
Start with the right instrumentation. Improve what you already have.