Piye carane sampeyan ngrancang logging lan monitoring ing production Node?

Question

Accepted Answer

**Logging** nyathet apa sing ditindakake aplikasi sampeyan; **monitoring** nglacak kesehatan lan performa. Bebarengan-barengan, padha menehi **observability** — kemampuan kanggo ngerti lan debug sistem production sing lagi mlaku. `console.log` ora cukup kanggo iki; sampeyan butuh structured logs, metrics, lan alerting.

## Structured logging (dudu console.log)

```js
import pino from "pino";
const logger = pino();

// ✅ structured JSON logs — machine-parseable, searchable, with context
logger.info({ userId: 123, action: "login", ip: req.ip }, "user logged in");
logger.error({ err, requestId }, "failed to process order");
```

Gunakake structured logger (pino/winston) sing ngasilake **JSON** karo fields sing konsisten. JSON logs bisa dienggal lan disaring ing log aggregation tools, ora kaya string `console.log` sing bebas. Kalebu context (user id, request id) ing saben log.

## Log levels lan apa sing kudu dilog

```text
Levels: error > warn > info > debug (configure threshold per environment)
Log:    requests, errors with stack traces, key business events, slow operations
DON'T log: passwords, tokens, PII, full payloads with secrets (security/privacy)
```

## Correlation IDs nglacak request saebaning services

```js
// attach a unique id per request, include it in EVERY log for that request
app.use((req, res, next) => {
  req.id = crypto.randomUUID();
  res.setHeader("X-Request-Id", req.id);
  next();
});
// now you can filter all logs for one request — vital in microservices
```

**Correlation/request ID** nglilani sampeyan mbalekake cerita lengkap siji request, sanajan saebaning services — kudu banget kanggo debug distributed systems.

## Pusatke logs

```text
Ship logs to a central platform (ELK/Elasticsearch, Datadog, Grafana Loki, CloudWatch)
→ search/aggregate across all instances; don't grep files on individual servers.
```

## Monitoring: metrics, alerts, tracing

```text
Metrics:  request rate, error rate, latency (p50/p95/p99), CPU/memory, event-loop lag
          (often via Prometheus + Grafana, or an APM like Datadog/New Relic)
Health:   /health & /ready endpoints for load balancers and orchestrators
Alerting: notify (PagerDuty/Slack) when error rate spikes or latency degrades
Tracing:  distributed tracing (OpenTelemetry) to follow requests across services
Errors:   error tracking (Sentry) for aggregated exceptions with stack traces & context
```

Metrics kunci sing kudu diwatani yaiku **"golden signals"**: latency, traffic, errors, lan saturation. Alerting ing iki nyekel masalah sadurunge users nglaporke.

## Kagunaan

Ing production sampeyan ora bisa nggandhengke debugger — **observability liwat logging lan monitoring yaiku carane sampeyan ngerti, debug, lan ngatur** sistem sing lagi mlaku.

Structured JSON logs karo correlation IDs nggawe incidents diagnosable (luwih-luwih saebaning microservices); centralized aggregation nggawe logs bisa digunakake ing skala gede; lan monitoring karo metrics, health checks, distributed tracing, lan alerting nlilani sampeyan mendeteksi lan meresponse masalah kanthi proaktif tinimbang sawise users ngluh.

Nggawe iki (dudu dol wanci sawise outage) yaiku praktik yang mbedakake layanan Node production sing bisa dipercaya.