Distributed Tracing

Distributed Tracing 


  • Cloud computing, microservices, open source tools, and container-based delivery have made applications more distributed across an increasingly complex landscape. As a result, distributed tracing has become crucial to responding quickly to issues.
  • Distributed tracing is a method of observing requests as they propagate through distributed cloud environments.
  • It follows an interaction and tags it with a unique identifier. This identifier stays with the transaction as it interacts with microservices, containers, and infrastructure. 
  • Distributed tracing helps teams understand more quickly how each microservice is performing. This understanding helps them resolve issues rapidly, increase customer satisfaction, ensure steady revenue, and preserve time for teams to innovate. This way, businesses can take full advantage of the benefits modern application environments offer while minimizing the challenges that their inherent complexity can also create.


Different Types of Distributed Logging


  1. Centralised Logging: 


  • Centralized logging is a method of recording activity wherein a team transports and stores the logs generated by a service or component in a single location. 
  • This enables teams to centrally track error reporting and related data. In a microservices environment, teams do this by aggregating the logs from multiple microservices into a central location so they can reference and analyze them more easily.
  • Centralized logging requires that systems transport logs from their origin to a single location. This practice can consume a considerable amount of network resources. As a result, this may sometimes lead to network performance issues that affect other applications and services.
  1. Distributed Logging: 

Distributed logging is a method of recording activity in logs that are located throughout the computing environment, often across multiple clouds.


  • Logs. Timestamped records of an event or events.
  • Metrics. Numeric representation of data measured over a set period.
  • Traces. A record of events that occur along the path of a single request.



Examples: 


Datadog agent APM 






Splunk 


Comments

Post a Comment

Popular posts from this blog

Reverse Proxy Vs API gateway Vs Load Balancer

Image
Reverse Proxy Vs API gateway Vs Load Balancer Reverse Proxy:   A reverse proxy is a server that sits in between the client devices and backend servers. It forwards the client requests to the appropriate   service and returns the server’s response to the client.   It protects the websites from the direct attacks like DDOS distributed denial of service.   It improves the performance by caching content.   It ensures the traffic is evenly distributed   across multiple servers to handle high volumes of requests efficiently.   Reverse Proxy provide features such as   Increased Security   Identity of backend servers Load distrubution SSL Termination Compression Caching It’s also useful with one web server.   API gateway:   An API Gateway is a server that acts as an entry point for managing, routing, and securing API requests to multiple backend services. API gateway offers features   Routing requests Authentication Authorization Monit...
Read more

Scalability

Image
Scalability As a system grows, the performance starts to degrade unless we adapt it to deal with that growth. Scalability is the property of a system to handle a growing amount of load by adding resources to the system. How can a System Grow? A system can grow in several dimensions.   1. Growth in User Base More users started using the system, leading to increased number of requests. Example: A social media platform experiencing a surge in new users. 2. Growth in Features More features were introduced to expand the system's capabilities. Example: An e-commerce website adding support for a new payment method. 3. Growth in Data Volume Growth in the amount of data the system stores and manages due to user activity or logging. Example: A video streaming platform like youtube storing more video content over time. 4. Growth in Complexity The system's architecture evolves to accommodate new features, scale, or integrations, resulting in additional components and dependencies. Example...
Read more