内容标题5

<i id='OyS1Gz'></i>

_{<blockquote id='OyS1Gz'><q id='OyS1Gz'><noscript id='OyS1Gz'></noscript><dt id='OyS1Gz'></dt></q></blockquote><noframes id='OyS1Gz'><i id='OyS1Gz'></i>}

Why Choose Kindling

RootCause Tiriage

With RPC trace，the user can identify the root-cause direction quickly, like if the issue is caused by network issue, code issue, storage issue, mutex Lock issue, the out-banding call issue. The first version can only identify request sending issue, code issue, downloading issue. The other issue identification is under active developing, will coming soon.

Network Flow Visualization

The service map can be viewed and many network metric can be monitored like，re-transmit，DNS，round-trip time. And golden metric like traffic，latency, error rate can be also viewed.

Prometheus Integration For Full Stack Monitoring

cAdvisor/MetricServer/Node Exporter/NPD, and Prometheus has been integrated and enriched with Kindling metric for full stack monitoring. The pod and node status metric can be viewed when the user found the response time is slow, and all the data are correlated. Standard version has this feature.

Open Source

Kindling will be open-sourced with two version. One is light version can be integrated into Prometheus server and metric can be viewed with Grafana plugin. Another version is the standard version, which has much detailed information and integrated with Prometheus for full stack monitoring.

Who Choose Kindling