skills/docker-openserve/SKILL.md
Docker deployment with OpenTelemetry and OpenObserve observability
npx skillsauth add MileniumTick/skills docker-openserveInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
# Build stage
FROM oven/bun:1-alpine AS builder
WORKDIR /app
COPY package.json packages/*/package.json ./
COPY . .
RUN bun install --frozen-lockfile
RUN bun run build
# Production stage
FROM oven/bun:1-alpine AS runner
WORKDIR /app
COPY --from=builder /app/dist ./dist
COPY --from=builder /app/node_modules ./node_modules
ENV NODE_ENV=production
EXPOSE 3000
CMD ["bun", "dist/index.js"]
# compose.yaml
services:
backend:
build: ./apps/backend
ports:
- "3000:3000"
environment:
- DATABASE_URL=postgresql://user:pass@db:5432/app
- REDIS_URL=redis://cache:6379
depends_on:
- db
- cache
db:
image: postgres:16-alpine
volumes:
- pgdata:/var/lib/postgresql/data
cache:
image: redis:7-alpine
otel-collector:
image: otel/opentelemetry-collector-contrib
config: ./otel-collector.yaml
openobserve:
image: openobserve/openobserve
ports:
- "5080:5080"
volumes:
pgdata:
// plugins/telemetry.ts
import { Elysia } from 'elysia'
import { trace, SpanStatusCode } from '@opentelemetry/api'
const tracer = trace.getTracer('backend')
export const telemetryPlugin = new Elysia()
.onRequest(({ path }) => {
const span = tracer.startSpan(path)
return ({ response, path }) => {
span.setAttribute('http.status_code', response.status)
span.setStatus(
response.status < 400
? SpanStatusCode.OK
: SpanStatusCode.ERROR
)
span.end()
}
})
// lib/backend.ts (Eden client)
import { trace } from '@opentelemetry/api'
// Add traceparent to requests
const withTrace = (req: Request) => {
const span = trace.getActiveSpan()
if (span) {
req.headers.set('traceparent', span.spanContext().toString())
}
return req
}
# otel-collector.yaml
receivers:
otlp:
protocols:
grpc:
endpoint: 0.0.0.0:4317
http:
endpoint: 0.0.0.0:4318
processors:
batch:
timeout: 5s
send_batch_size: 1000
memory_limiter:
check_interval: 1s
limit_mib: 400
exporters:
otlp:
endpoint: http://openobserve:5080
tls:
insecure: true
logging:
loglevel: debug
service:
pipelines:
traces:
receivers: [otlp]
processors: [batch, memory_limiter]
exporters: [otlp]
logs:
receivers: [otlp]
processors: [batch]
exporters: [otlp]
development
Writes, reviews, and debugs idiomatic Rust code with memory safety and zero-cost abstractions. Implements ownership patterns, manages lifetimes, designs trait hierarchies, builds async applications with tokio, and structures error handling with Result/Option. Use when building Rust applications, solving ownership or borrowing issues, designing trait-based APIs, implementing async/await concurrency, creating FFI bindings, or optimizing for performance and memory safety. Invoke for Rust, Cargo, ownership, borrowing, lifetimes, async Rust, tokio, zero-cost abstractions, memory safety, systems programming.
development
Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook. Use this skill when: (1) writing new Rust code or functions, (2) reviewing or refactoring existing Rust code, (3) deciding between borrowing vs cloning or ownership patterns, (4) implementing error handling with Result types, (5) optimizing Rust code for performance, (6) writing tests or documentation for Rust projects.
development
Master Rust async programming with Tokio, async traits, error handling, and concurrent patterns. Use when building async Rust applications, implementing concurrent systems, or debugging async code.
tools
When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see email-sequence. For pricing decisions, see pricing-strategy.