Umut
Should I instrument my services with RED metrics or USE metrics first?
Start with RED on the API, model jobs as requests to run RED on the workers too, then layer USE onto both for queue depth and pool saturation.
All questions
Tag
#Observability
Metrics, logs and traces: reading what a system does from the outside. questions under this tag, answered directly.
7 answered questions carry this tag.
Cem
How should I carry a correlation ID from the HTTP request all the way into queued jobs?
Generate the ID as a W3C `traceparent`, carry it in an SQS message attribute rather than the body, and inject it with the OTel propagator on both sides.
Can
How do I set a clear rule for when to log at WARN versus ERROR?
Log at ERROR when the line would wake someone at 3am and at WARN when it would not, log a failure once at its boundary, and alert on the ERROR rate.
Emir
How do I design a self-healing deploy that auto-rolls back when the error rate spikes?
Hold the new version at a canary weight and check 5xx and latency against a threshold; on breach, roll back to the last stable release and alert the team.
Serkan
How do I prevent log storms and disk-full outages?
Collapse repeated errors into one counted line, back off retries, cap logrotate by size and count, and give `/var/log` a volume off the root disk.
Ece
How do I set up distributed tracing (OpenTelemetry) across microservices?
Standardize on W3C Trace Context, leave propagation to the OTel SDK, and put traceparent in the queue message header, since that is where the chain snaps.
Burak
Should I put a Kafka/Redis buffer between Fluent Bit and OpenSearch when shipping logs?
Turn on Fluent Bit's filesystem buffer first; move to Kafka once 40k/s is permanent, and keep a Redis list only for logs you can afford to lose.