golang-observability-opentelemetry
Modern Go applications require comprehensive observability through the three pillars: traces, metrics, and logs. OpenTelemetry provides vendor-neutral instrumentation for distributed tracing, Prometheus offers powerful metrics collection, and Go's slog package (1.21+) delivers structured logging with minimal overhead.
Works with
1
total installs
1
this week
29
GitHub stars
0
upvotes
Install Skill
Run in your terminal
1
installs
1
this week
29
stars
Installation Guide
How to use golang-observability-opentelemetry on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your machine
- ›Node.js 16+ with npm — verify with
node --version - ›Active project directory where you want to add
golang-observability-opentelemetry
Run the install command
Execute the skills CLI command in your project's root directory to begin installation:
Fetches golang-observability-opentelemetry from bobmatnyc/claude-mpm-skills and configures it for Cursor.
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate golang-observability-opentelemetry. Access via /golang-observability-opentelemetry in your agent's command palette.
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Documentation
Go Observability with OpenTelemetry
Overview
Modern Go applications require comprehensive observability through the three pillars: traces, metrics, and logs. OpenTelemetry provides vendor-neutral instrumentation for distributed tracing, Prometheus offers powerful metrics collection, and Go's slog package (1.21+) delivers structured logging with minimal overhead.
Key Features:
- 🔍 OpenTelemetry: Distributed tracing with context propagation
- 📊 Prometheus: Metrics collection with /metrics endpoint
- 📝 Structured Logging: slog with JSON formatting and correlation IDs
- 🎯 Auto-Instrumentation: HTTP/gRPC middleware patterns
- 💚 Health Checks: Kubernetes-ready readiness/liveness probes
- 🔄 Graceful Shutdown: Clean exporter shutdown and signal handling
When to Use This Skill
Activate this skill when:
- Instrumenting microservices for production observability
- Setting up distributed tracing across service boundaries
- Creating operational dashboards with Prometheus/Grafana
- Debugging production performance issues or bottlenecks
- Implementing SLOs and monitoring SLIs
- Adding observability to existing Go applications
- Correlating logs, traces, and metrics for debugging
Core Observability Principles
The Three Pillars
- Traces: Understand request flow across distributed systems
- Metrics: Measure system behavior and performance over time
- Logs: Record discrete events for debugging and audit
Correlation Strategy
All three pillars must share common identifiers:
- Trace ID: Links all operations in a request
- Span ID: Identifies specific operation within trace
- Request ID: Correlates logs with traces and metrics
OpenTelemetry Integration
Installation
go get go.opentelemetry.io/otel
go get go.opentelemetry.io/otel/sdk
go get go.opentelemetry.io/otel/exporters/jaeger
go get go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp
Basic Setup
package main
import (
"context"
"log"
"go.opentelemetry.io/otel"
"go.opentelemetry.io/otel/exporters/jaeger"
"go.opentelemetry.io/otel/sdk/resource"
sdktrace "go.opentelemetry.io/otel/sdk/trace"
semconv "go.opentelemetry.io/otel/semconv/v1.21.0"
)
func initTracer(serviceName string) (*sdktrace.TracerProvider, error) {
// Create Jaeger exporter
exporter, err := jaeger.New(jaeger.WithCollectorEndpoint(
jaeger.WithEndpoint("http://localhost:14268/api/traces"),
))
if err != nil {
return nil, err
}
// Create resource with service name
res, err := resource.Merge(
resource.Default(),
resource.NewWithAttributes(
semconv.SchemaURL,
semconv.ServiceName(serviceName),
semconv.ServiceVersion("1.0.0"),
),
)
if err != nil {
return nil, err
}
// Create tracer provider
tp := sdktrace.NewTracerProvider(
sdktrace.WithBatcher(exporter),
sdktrace.WithResource(res),
sdktrace.WithSampler(sdktrace.AlwaysSample()), // Use probability sampler in production
)
otel.SetTracerProvider(tp)
return tp, nil
}
func main() {
tp, err := initTracer("order-service")
if err != nil {
log.Fatal(err)
}
defer func() {
if err := tp.Shutdown(context.Background()); err != nil {
log.Printf("Error shutting down tracer: %v", err)
}
}()
// Application code...
}
Creating Spans
import (
"context"
"go.opentelemetry.io/otel"
"go.opentelemetry.io/otel/attribute"
"go.opentelemetry.io/otel/codes"
"go.opentelemetry.io/otel/trace"
)
func ProcessOrder(ctx context.Context, order Order) error {
tracer := otel.Tracer("order-service")
ctx, span := tracer.Start(ctx, "ProcessOrder")
defer span.End()
// Add attributes
span.SetAttributes(
attribute.String("order.id", order.ID),
attribute.Int("order.items", len(order.Items)),
attribute.Float64("order.total", order.Total),
)
// Validate order (creates child span)
if err := validateOrder(ctx, order); err != nil {
span.RecordError(err)
span.SetStatus(codes.Error, "validation failed")
return err
}
// Fulfill order
if err := fulfillOrder(ctx, order); err != nil {
span.RecordError(err)
span.SetStatus(codes.Error, "fulfillment failed")
return err
}
span.SetStatus(codes.Ok, "order processed successfully")
return nil
}
func validateOrder(ctx context.Context, order Order) error {
_, span := otel.Tracer("order-service").Start(ctx, "validateOrder")
defer span.End()
// Validation logic...
return nil
}
HTTP Middleware Instrumentation
import (
"net/http"
"go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp"
)
func main() {
// Wrap handler with automatic tracing
handler := http.HandlerFunc(orderHandler)
wrappedHandler := otelhttp.NewHandler(handler, "order-handler")
http.Handle("/orders", wrappedHandler)
http.ListenAndServe(":8080", nil)
}
// Manual instrumentation for more control
func orderHandler(w http.ResponseWriter, r *http.Request) {
ctx := r.List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
- 1Install skill using provided installation command
- 2Test with simple use case relevant to your work
- 3Evaluate output quality and relevance
- 4Iterate on prompts to improve results
- 5Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Related Skills
golang-testing
6samber/cc-skills-golang
golang-architect
6tomlord1122/tomtom-skill
typescript-best-practices
96jwynia/agent-skills
java-springboot
42github/awesome-copilot
google-search-console
41kostja94/marketing-skills
python-expert-best-practices-code-review
34wispbit-ai/skills
Reviews
- SShikha Mishra★★★★★Dec 28, 2024
Keeps context tight: golang-observability-opentelemetry is the kind of skill you can hand to a new teammate without a long onboarding doc.
- AAva Jackson★★★★★Dec 24, 2024
Registry listing for golang-observability-opentelemetry matched our evaluation — installs cleanly and behaves as described in the markdown.
- MMeera Brown★★★★★Dec 16, 2024
Useful defaults in golang-observability-opentelemetry — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- YYash Thakker★★★★★Nov 19, 2024
Registry listing for golang-observability-opentelemetry matched our evaluation — installs cleanly and behaves as described in the markdown.
- YYuki Okafor★★★★★Nov 15, 2024
Keeps context tight: golang-observability-opentelemetry is the kind of skill you can hand to a new teammate without a long onboarding doc.
- MMeera Jackson★★★★★Nov 7, 2024
golang-observability-opentelemetry has been reliable in day-to-day use. Documentation quality is above average for community skills.
- MMeera Park★★★★★Oct 26, 2024
Solid pick for teams standardizing on skills: golang-observability-opentelemetry is focused, and the summary matches what you get after install.
- DDhruvi Jain★★★★★Oct 10, 2024
golang-observability-opentelemetry reduced setup friction for our internal harness; good balance of opinion and flexibility.
- LLuis Bansal★★★★★Oct 6, 2024
golang-observability-opentelemetry is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- LLuis Haddad★★★★★Sep 25, 2024
golang-observability-opentelemetry fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 51
Discussion
Comments — not star reviews- No comments yet — start the thread.