logging

To enforce structured logging across a monorepo, configure a centralized base formatter that outputs JSON-serializable logs and mandates contextual fields like requestId and userId for all services and packages.

The best way to add contextual data for observability is injecting fields like requestId, userId, and sessionId into a centralized base formatter, ensuring every log entry contains end-to-end trace context for reliable querying.

Yes, you can standardize log levels and sensitive data masking across multiple services by applying a shared logging baseline with a centralized formatter that includes guidance for masking contextual fields.

Structured logging works with OpenTelemetry integration by including trace context in every JSON-serializable log entry, providing end-to-end visibility and cross-service correlation across apps and packages in the monorepo.

You need JSON-serializable logs for troubleshooting because they enable reliable querying and cross-service correlation, allowing you to filter and analyze contextual data like request IDs across distributed systems efficiently.