sematext-otellisted

# Sematext OTel onboarding Use this skill to wire a service that emits OpenTelemetry data into Sematext Cloud. It is parameter-driven; work through these in order: 1. **Triage**: ask the six questions below to fix region, Apps, flow, protocol, language/env, and instrumentation style. 2. **Assemble**: build the env-var block from Flow A (managed OTLP) or Flow B (Sematext Agent), placeholders intact. 3. **Point**: send the user to the matching reference example in this repo. 4. **Verify**: confirm data lands within 60s, looping through Troubleshooting until it does. ## Agent constraints Two hard rules when running this skill: **Never handle real token values.** Do not ask the user to paste an App token, and do not accept one if offered. Every env-var block you produce keeps the literal placeholders (`<tracing-app-token>`, etc.); the user substitutes real values themselves, outside the conversation. A token that appears in chat is in conversation history and agent context for good, and must be rotated in Sematext Cloud. If a user pastes one anyway, tell them to rotate it and continue with placeholders. **Never run the privileged commands.** The `sudo st-agent otel enable` commands in Flow B are for the user to run in their own shell. Print them for the user to copy; do not execute them, and do not offer to. ## Triage Ask the user, in order: 1. **Which Sematext region?** US or EU. 2. **Which App types are you wiring up?** Tracing, Logs, Monitoring — any combination. Each