Njengoba umphakeli we-backend abasebenza ne-microservices eminyakeni eminyakeni eminyakeni eminyakeni eminyakeni eminyakeni eminyakeni eminyakeni eminyakeni eminyakeni eminyakeni eminyakeni eminyakeni eminyakeni eminyakeni eminyakeni. Ngaba unezinsizakalo eziveza izinsizakalo, izikhathi ezingama-dozen. Umdlali utshintshe i-button ku-UI, futhi ama-microservices angama-15 zihlanganisa ekusebenzeni. Uma yini ingxube - noma engaphansi, nje ngempumelelo - ukuhlola lapho futhi ukuthi kungenxa amahora. Futhi uma usakhiwo noma ukugcinwa ama-microservices ku-2024, i-OpenTelemetry iyisixhobo esidinga ekupheleni lakho. Yintoni i-observability, ngokwenene? I-Observability kuyinto engaphezu kwama-logs kuphela. Kubalulekile ukucacisa ukuthi inqubo yakho isebenzise ngezindlela ezithile, futhi akuyona kuphela into esebenzayo. Kwi-core, sincoma ngezinyathelo ezintathu: Logs – Izinto Raw, ezisebenzayo yokubhalisa. I-Metrics – Izinombolo ezinokufundisa ngokushesha (isib. Inombolo ye-request, i-CPU). Traces – End-to-end imibuzo imibuzo nge-services (eyaziwa nangokuthi i-distributed "call stack"). Izinsiza zokulawula ezivamile zihlanganisa kwama-metric kanye ne-logs, kodwa ukucubungula kuyinto umdlalo enhle ye-microservices. Why We Khetha OpenTelemetry Thina usebenzise ezinye izikhwama ze-observability - Datadog, New Relic, Prometheus, Jaeger, Zipkin - kodwa bonke baye unemibuzo: noma baye abanikeze ama-vendor-locked noma ayikho ukuxhumana phakathi kwezilimi. I-OpenTelemetry (OTel) ivame zonke izikhwama zethu: Open-source, ngaphansi CNCF Ukusebenza ngezilimi (sebenzisa Node.js, Go, futhi Python) Supplier-neutral - ukuhweba ku Grafana, Jaeger, New Relic, njll Ukusekela wonke umkhakha (ngokuthi: AWS, GCP, Microsoft, njll) Ungasebenzisa kanjani i-OpenTelemetry ku-Node.js Microservices Qinisekisa ukuthi ngibhalisa kanjani i-instrumentation ye-services enhle. Sicela siphinde inkonzo elula ye-User eyenziwe ku-Node.js usebenzisa i-Express. Kuyathintela i-endpoint `/users` elithathwe idatha ye-users. Ngezantsi zihlanganisa izinyathelo. Step 1: Install Dependencies npm install @opentelemetry/api \
@opentelemetry/sdk-node \
@opentelemetry/auto-instrumentations-node \
@opentelemetry/exporter-trace-otlp-http
 Thola ukuhambisa izimpendulo ngokusebenzisa i-OTLP ku-Jaeger instance yendawo. Step 2: Create tracing.js to Initialize OpenTelemetry JavaScript: tracing.js const { NodeSDK } = require('@opentelemetry/sdk-node');
const { getNodeAutoInstrumentations } = require('@opentelemetry/auto-instrumentations-node');
const { OTLPTraceExporter } = require('@opentelemetry/exporter-trace-otlp-http');
const { SemanticResourceAttributes } = require('@opentelemetry/semantic-conventions');
const { Resource } = require('@opentelemetry/resources');
const traceExporter = new OTLPTraceExporter({
url: 'http://localhost:4318/v1/traces',
});

const sdk = new NodeSDK({
traceExporter,
instrumentations: [getNodeAutoInstrumentations()],
resource: new Resource({
[SemanticResourceAttributes.SERVICE_NAME]: 'user-service',})
});
sdk.start();
 Step 3: Add It to Your Entry File JavaScript: Index.js

require('./tracing'); // Always load this first

const express = require('express');
const app = express();

app.get('/users', (req, res) => {
 res.json([{ id: 1, name: "Alice" }, { id: 2, name: "Bob" }]);
});

app.listen(3000, () => console.log("User service running on port 3000"));
 Inkampani yethu isixazululo isitimela. Step 4: Spin Up Jaeger Locally (or Use Grafana Tempo) Ngiyavuza kanjani ku-locally: docker run -d --name jaeger \
 -e COLLECTOR_OTLP_ENABLED=true \
 -p 4318:4318 -p 16686:16686 \
 jaegertracing/all-in-one:latest
 Thola http://localhost:16686 ukuze ubone imiphumela yakho. Thola http://localhost:16686 ukuze ubone imiphumela yakho. Chaining Traces Ngaphandle Izinsizakalo Ngingumfana ukuthi unayo inkonzo eyodwa - order-service - okuyinto inikeza inkonzo ye-user-service. Uma amabili angama-OpenTelemetry, uzothola ingozi ephelele ye-user request eyenza phakathi kwabo. Futhi ingxenye engcono? I-OpenTelemetry ithatha ukuxhumana kwe-trace context ngokusebenzisa i-HTTP headers ngokushesha. Ungafuna ukuxhumana kwe-trace ID phakathi kwamasevisi. Ukongeza i-Custom Spans ye-Business Logic Ngamanye ama-auto-instrumentation akufanele. Ngokwesibonelo, uma ufuna ukucubungula isibuyekezo se-DB noma isibuyekezo se-API: const { trace } = require('@opentelemetry/api');
const tracer = trace.getTracer('user-service');

app.get('/users', async (req, res) => {
 const span = tracer.startSpan('fetch-user-data');
 try {
  const users = await fetchUsersFromDB();
  res.json(users);
 } catch (err) {
  span.recordException(err);
  throw err;
 } finally {
  span.end();
 }
});
 Kuyinto enhle lapho ufuna ukucubungula ukusebenza kwezobuchwepheshe ezithile zebhizinisi. Best Practices We've Learned the Hard Way 1.  Use Semantic Conventions Ngaphandle kokufunda ama-attribute names yakho, sicela uxhumane ne-OpenTelemetry semantic conventions. Lezi zenza i-track yakho kulula ukucacisa futhi iyahambisana nezixhobo ezifana neGrafana, Tempo, njll Umzekelo: JavaScript
span.setAttribute("http.method", req.method);
span.setAttribute("http.route", req.path);
 2. Sample Wisely Uma unamathela ngamunye isicelo, uhlelo lakho lihlala idatha. Usebenzisa isampula isampula (isib. 10%, noma kuphela imiphumela). Waze const sdk = new NodeSDK ({
 sampler: new TraceIdRatioBasedSampler (0.1), // 10% sampling
});
 3. Use OpenTelemetry Collector in Production Ungayithenga idatha ye-telemetry ngqo kusuka ku-services yakho ku-backend yakho. I-rout it nge-OpenTelemetry Collector - inikeza ukulungiswa kwe-buffering, i-batching, i-retries, ne-format conversion. 4. Don't Log PII in Spans Kuyinto enhle kakhulu. Qinisekisa ukuthi akuyona igama lomsebenzisi, i-imeyili, inombolo ye-credit card, njll ku-span atributes noma i-logs. Qiniseka ku-metadata kanye ne-ID. Kusukela lapho lithumela kakhulu I-Debugging Latency I-Problems: Ukubonisa izimpendulo ephelele kwama-microservices angama-microservices angasiza ukuhlola izimpendulo ezingenamaminithi. Ukuhlola ama-retry storms: Sikhona inkonzo enikezela enye ku-retries, okuyinto asikwazi ukufinyelela nge-logs. Ukulungiswa kwe-regression: Ukubalwa kwezimpendulo kusuka ku-version eyodwa kuya ku-version elilandelayo ibonise ukuthi kungcono ukuthi kungcono. Bonus: Ukuhlola ku-Multi-Language Stack I-OpenTelemetry yenza lula ukuzenzakaleka kanye nokuthumela idatha yonke indawo eyodwa - Jaeger ye-dev, i-Grafana Cloud ku-staging/prod. No vendor lock-in. No mismatch ku-trace formats. Just ukubukeka okuhlobene. Conclusion: If You're Building Microservices, Start with Observability I-microservices inikeza usayizi kanye nokugxila, kodwa inikeza futhi ukucindezeleka. Ngaphandle kwe-observability efanelekayo, ungenza umlilo. I-OpenTelemetry iye yakhelwe ingxenye yesisekelo se-architecture yethu, hhayi kuphela ukulungiselela, kodwa ukulungiselela ukusebenza, ukucindezeleka, futhi ekupheleni kwe-user experience. Uma umuntu akunakusebenzisa futhi, ngithembisa kakhulu ukunikezela. Ngaphandle kokufaka isakhiwo esisodwa nge-Jaeger kanye namasevisi amabili uzokufunda ukuthi ungayifumana kanjani ngihambe ngaphandle kwalokho.

Walkthroughs, tutorials, guides, and tips. This story will teach you how to do something new or how to do something better.

Lo msindo ukhiqizwa ngolimi lokuqala lwendaba!

I-Microservices Observability: Ukusetshenziswa kwe-OpenTelemetry ku-Real-World Systems ngu-Gajinder Sharma

About Author

IMIBONO

HANG TAGS

LESI SIHLOKO SETHULWE NGAPHAKATHI

Related Stories

Zulu Network: Moving The Bitcoin Economy Forward With a Two-Tiered Bitcoin Layer 2 Architecture

The Billionaires F*cked Up

Zulu Network: Moving The Bitcoin Economy Forward With a Two-Tiered Bitcoin Layer 2 Architecture

The Billionaires F*cked Up

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps