Observability: logs, metrics and traces

FintechBy: Mahdi Mansour Samaei2 min readSource: CNCF
Observability: logs, metrics and traces

1Introduction

Observability rests on logs, metrics and distributed traces.

2Discussion

In microservices one request crosses many services; tracing (e.g. OpenTelemetry) finds the slow or failing one.

Use the four golden signals — latency, traffic, errors, saturation — and alert on user impact.

3Conclusion

Good observability cuts time to detect and fix issues and guides capacity decisions.

Share:TelegramWhatsAppLinkedIn

Sources

  1. CNCF ↗
  2. NIST ↗
همفکران فناوری شریفThis article summarises the official sources cited, prepared by the Hamfekran Fanavari Sharif team for finance leaders.
Want to see these solutions in your organisation?Book a free demo

Related articles

FintechThreat hunting: finding attackers who triggered no alertHunting assumes compromise and actively searches for evidence instead of waiting for alerts.FintechSecrets management: where should passwords live?A database password in code will eventually reach the wrong hands.FintechAutomated bank reconciliation: ending manual finance workMatching bank statements to books is one of finance’s most time-consuming tasks — and ideal for automation.FintechDigital strategy for executives: where to startDigital transformation starts with a clear business question, not a software purchase.