Multi-Tenant B2B SaaS Logging Backend: Search Costs for Silent Imports
A scheduled catalog import that never starts produces no failure event. For a multi-tenant B2B SaaS app, use a logging backend to investigate work that ran and a heartbeat monitor to detect work that stayed silent. Then attribute log volume by tenant and import run before choosing where those events live. TL;DR: for an e-commerce B2B SaaS, keep tenant_id , user_id , request_id , trace_id ,…
We haven't written up this one. Dev.to has the full story — the link below goes straight to it.
