Skip to main content
security Cybersecurity

sovdev-logger

Application telemetry often flows to foreign cloud providers, exposing operational patterns and sensitive metadata. sovdev-logger works with self-hosted backends like Grafana and Loki, keeping your observability data under your control and jurisdiction.

Active Started January 2025
Summary

One log call — automatic logs, metrics, traces, and service maps. 95% less instrumentation code.

You write code for yourself during development. But you write logs for the operations engineer staring at a screen at 7 PM on Friday. Good logging is the difference between a 3-hour debugging session and a 5-minute fix.

error_outline The Problem

Traditional observability requires 20+ lines per operation — separate logger calls, metric counters, trace spans, manual correlation.

The Solution

One call gives you logs, metrics, traces, and correlation — automatically.

TypeScript — sovdev_log
sovdev_log(INFO, FUNCTIONNAME, 'Payment processed', PEER_SERVICES.PAYMENT_GATEWAY, input, output);

What You Get Automatically

description Outputs

Structured Logs
Metrics
Distributed Traces
Service Maps
File Logs

cloud Azure Production

Azure Log Analytics
Azure Monitor
Application Insights

computer Local / On-Prem

Console + JSON files
Grafana / Prometheus
Tempo

sync_alt No Vendor Lock-in

Built on OpenTelemetry — Microsoft's recommended standard. Same code works with Azure Monitor in production and Grafana locally.

Supported Languages

Works with any OpenTelemetry-compatible backend:

code TypeScript (Available)
schedule Go (Planned)
schedule Python (Planned)
schedule C# (Planned)

Quick Start

download
Install

npm install @sovdev/logger

code
One line of code

sovdev_log(INFO, FUNCTIONNAME, "Payment processed", PEER_SERVICES.PAYMENT_GATEWAY, input, output)

check_circle
Zero config needed

Logs to console and ./logs/ directory out of the box. No configuration for local development.