Autonomously review and improveOpenTelemetry instrumentation.
Rose analyzes your code for instrumentation issues, highlights what needs attention, and prepares targeted fixes in pull requests.
o11y: add OpenTelemetry instrumentation to user service
23 func GetUserHandler(w http.ResponseWriter, r *http.Request) {24 userID := r.PathValue("id")25 tracer := otel.Tracer("user-service")26 ctx, span := tracer.Start(r.Context(), "GET /users/"+userID)27 defer span.End()2829 user, err := db.FindUserByID(ctx, userID)30 // ...31 }
Instrumentation isn't easy
Good instrumentation is the foundation of effective observability. But getting it right presents real challenges that impact your systems as they scale.
Data Explosion and Scalability
Complexity and Inconsistencies
Time Investment
Meet OllyGarden Rose
Rose autonomously reviews OpenTelemetry instrumentation in code, highlights what needs attention, and prepares targeted fixes in pull requests.
Free for up to 3 repositories
Agentic Instrumentation
Analyze entire codebases and automatically apply purposeful instrumentation
Complete Codebase Assessment
Comprehensive instrumentation quality analysis across all services with actionable recommendations
Autonomous Instrumentation Setup
Zero-config instrumentation bootstrapping following OpenTelemetry best practices
Built for Developer Productivity
Rose is designed to make OpenTelemetry instrumentation easy, letting you focus on building features while having confidence in your instrumentation.
Context-Aware Analysis
Rose understands your entire codebase, not just the diff. It connects patterns across service boundaries, OllyGarden expertise, and official OTel standards.
42-span.setAttribute('user.id', userId)43+span.setAttribute('user.type', userType)
user.id as an attribute can cause cost spikes due to high cardinality.- span.setAttribute('user.id', userId)+ span.setAttribute('user.type', userType)
Catch Issues Early
Identify instrumentation problems during code review before they reach production.
Save Time
Automated reviews reduce manual instrumentation efforts, freeing engineers to focus on their business tasks
Learn from OTel Expertise
Review comments include explanations and examples to help your team understand OpenTelemetry best practices
- setAttribute('user.email', email)// ⚠️ PII Leak Risk- setAttribute('session.token', token)// ⚠️ High Cardinality (500K+ values)Instrumentation You Can Trust
Prevent high-cardinality cost spikes and sensitive data leaks already during development.
Think you know OpenTelemetry?
Rose has prepared 10 questions to test your OTel knowledge. No sign-up required.
Take the QuizReady to ship better instrumentation?
Get started with Rose for free and let Rose review your code for OpenTelemetry instrumentation issues.
- Review your code for OpenTelemetry instrumentation issues and highlight what needs attention
- Prepare targeted fixes in pull requests for your team to review and merge
- Free for up to 3 repositories