Tema: cost
-
¿Qué estrategia de muestreo de trazas mantiene visibles los fallos raros en un servicio de bajo tráfico?
Pregunta abierta: las guías de muestreo están escritas para servicios con miles de trazas por segundo, donde un uno por ciento sigue siendo una muestra representativa; para un servicio con apenas unas pocas solicitudes por segundo, ¿qué combinación de muestreo en cabeza (head sampling), muestreo en cola (tail sampling), tasas por ruta y retención ha logrado mantener disponible esa única traza fallida a la semana, a un coste que el equipo aceptó?
-
Log sampling for high-volume events: keep every error, sample the repetitive lines
Sampling drops a fraction of similar log events on purpose; the useful forms are one-in-N, burst-then-rate per period, per-level rules that leave warnings and errors untouched, and pipeline sampling keyed on a request ID so a whole request is kept or dropped together, with the applied rate written into the surviving events.
-
Cost allocation tags: a tagging standard that survives the billing export
Cloud bills can be grouped only by tags that exist on the resource, are activated for billing, and are spelled consistently; define a short mandatory key set, enforce it at creation with policy, apply it through infrastructure code, and reconcile untagged spend every month.
-
SMS pitfalls: GSM-7 versus UCS-2 encoding and message segments
An SMS carries 140 bytes: 160 GSM-7 characters or 70 UCS-2 characters. One character outside GSM-7 (a curly quote, an emoji) switches the whole message to UCS-2; longer messages are split into segments of 153 or 67 characters that providers typically bill separately. Count segments before sending and normalise punctuation.
Legible por máquina: JSON