| 1 |
Rules-Requires-Root: no |
| 2 |
Standards-Version: 4.5.1 |
| 3 |
Build-Depends: debhelper-compat (= 12), dh-sequence-python3, python3-all, python3-aiohttp (>= 3.7.2), python3-setuptools |
| 4 |
Testsuite: autopkgtest-pkg-python |
| 5 |
Source: aiozipkin |
| 6 |
Priority: optional |
| 7 |
Section: python |
| 8 |
Maintainer: Jelmer Vernooij <[email protected]> |
| 9 |
Vcs-Git: https://salsa.debian.org/jelmer/aiozipkin.git |
| 10 |
Vcs-Browser: https://salsa.debian.org/jelmer/aiozipkin |
| 11 |
|
| 12 |
Package: python3-aiozipkin |
| 13 |
Depends: ${python3:Depends}, ${misc:Depends} |
| 14 |
Architecture: all |
| 15 |
Description: Distributed tracing instrumentation for asyncio application with zipkin |
| 16 |
aiozipkin is a Python module that adds distributed tracing |
| 17 |
capabilities from asyncio applications with zipkin (http://zipkin.io) |
| 18 |
server instrumentation. |
| 19 |
. |
| 20 |
zipkin is a distributed tracing system. It helps gather timing data |
| 21 |
needed to troubleshoot latency problems in microservice architectures. |
| 22 |
It manages both the collection and lookup of this data. Zipkin’s |
| 23 |
design is based on the Google Dapper paper. |
| 24 |
. |
| 25 |
Applications are instrumented with aiozipkin report timing data to |
| 26 |
zipkin. The Zipkin UI also presents a Dependency diagram showing how |
| 27 |
many traced requests went through each application. If you are |
| 28 |
troubleshooting latency problems or errors, you can filter or sort all |
| 29 |
traces based on the application, length of trace, annotation, or |
| 30 |
timestamp. |