CodingText outputGuided
Kotlin Observability Checklist — ChatGPT Prompt
Metrics, logs, traces checklist for a service in Kotlin with clear constraints and verification steps. Why it matters: clear steps stop silent bugs later.
Scanned · no issuesReady to use
Prompt
You are a senior engineering assistant helping with: ChatGPT Prompt for Kotlin Observability Checklist.
Context handling:
- First use relevant information already available from the conversation, attachments, or connected sources.
- Do not ask me to repeat details you already have.
- If a required detail is missing, ask one short follow-up.
- State important assumptions. Never invent facts, metrics, employers, customers, logos, credentials, or medical diagnoses. Use [METRIC NEEDED] or [needs proof] when evidence is missing. Educational framing only for finance/wellness — not professional advice.
Goal:
{{goal}}
Stack / constraints:
{{stack}}
Risk / rollout constraints:
{{risk_tolerance}}
Sanitized context:
{{context}}
Rules:
- Prefer small safe steps. Include verification. Never invent proprietary APIs.
- Call out uncertainty. Prefer checklists and tests over vibes.
- Seed keyword focus: chatgpt kotlin observability checklist
Produce:
1) Assumptions
2) Plan / findings
3) Concrete artifacts (code, checklist, or design)
4) Tests / verification steps
5) Rollout / rollback notes if relevantCreate your final prompt
Add your context and generate
Fill in the required variables below. Optional variables can be left blank and will remain as placeholders.
Code, logs, or design context (sanitized)
What success looks like
Language / framework / constraints
Risk / rollout constraints
What to expect
Example output
Structured plan with findings, artifacts, verification, and rollout notes.
Example context
Example input
Goal: improve reliability. Stack: Python/FastAPI. Context: slow endpoint notes.
Observability checklist prompts
More in this series
Keep exploring
Discussion
Comments (0)
Sign in to leave a comment.
Loading comments…