Tracing Analysis

Allows developers to quickly diagnose and analyze application performance bottlenecks and root causes in distributed architecture frameworks.

With trace mapping, request counting, trace discovery, application dependency analysis and more tools dedicated for distributed applications, Tracing Analysis allows developers to identify the performance bottlenecks quickly, and significantly improve the development and diagnosis efficiency in the framework of micro-services. Tracing Analysis is available for free, and you only need to pay for Log Service on which it depends.

Why Tracing Analysis

Step-by-step Tracing
Making it easier to troubleshoot distributed applications. No need to log on to the machine and check logs.
Complete trace analysis
Provides application and request analysis for each interface.
Fully compatible with open-source products
Setting tracking points with open-source SDKs such as Zipkin or OpenTracing
Cost-efficient
Tracing Analysis is free to use. Only data storage costs apply. Save up to 80% compared to DIY.

Features

Querying and diagnosing distributed invocation traces

Tracking all user requests for micro-services in the distributed architecture, and combining them into distributed invocation traces.

RPC tracing

Tracking HTTP, Dubbo, HSF, and more interfaces of microservice programs.

PaaS tracing

Tracking database, NoSQL, MQ, and more PaaS invocation traces.

Summarizing application performance in real time

Summarizing the single services and resources that make up of the application by tracking the user requests in the whole application.

Diverse dimensions

Aggregating on application, service, and more levels.

Real-time computing

Calculating aggregation results in real time, with a delay of less than one minute.

Discover distributed topology

Collecting the distributed invocation information from your distributed microservice applications and PaaS products.

Dynamic and accurate

Reflecting what's going on with real-time topology based on reported trace information.

Supporting multiple programming languages

Based on OpenTracing standard, fully compatible with open-source community, such as Jaeger and Zipkin.

Direct reporting

Reporting invocation data by integrating the multi-language client SDK of Tracing Analysis.

Indirect reporting

Reporting to independent Agent through multi-language client SDK, and then reporting to Tracing Analysis collectively by Agent.

Diverse possibilities of integration with other products

Using the collected trace information directly for log analysis or integrating with downstream analysis products such as MaxCompute.

Alarm integration

Supporting integration with CloudMonitor for alarms based on monitoring data.

Big data analytics

Supporting integration with MaxCompute for data mining.

Use Cases

Full trace monitoring

Full trace monitoring

Microservice trace monitoring and diagnosis based on distributed architecture under heterogeneous frameworks

Although the distributed application architecture under micro-service architecture can meet the application scale-out requirements, performing distributed application diagnosis remains a challenge.

Tracing Analysis can handle:

  • Difficulty in interface diagnosis

    How to quickly identify faulty microservice interfaces

  • Complexity of application performance diagnosis

    How to find the problematic nodes in a distributed architecture

  • Complexity of architecture analysis

    It's time consuming to get the whole picture of the architecture

  • Integration with programs of different languages

    How to integrate with programs of different languages with one set of standards

  • Offline analysis of invocation

    How to make the most out of application traces

Works Best With