| Key | Value |
|---|---|
| FileName | ./usr/share/doc/python-osprofiler-doc/html/_static/comment.png |
| FileSize | 3445 |
| MD5 | 9CB155BA51E4A3F3DD0084963ACFE52F |
| SHA-1 | 03CC5F01F7962B4083255A3FBDC58F9BA6F04C79 |
| SHA-256 | 4903305657C3FBAFAF8E9358CBF83F9168A0739B95542E7B1C23E7AF6B871483 |
| SSDEEP | 96:kZ/I09Da01l+gmkyTt6Hk8nT+SdiVkhzHc:kS0tKg9E05T+SdiVkJc |
| TLSH | T101618EAE97A0909FF99E72110D8C0282D358121C5D5B2B7889D1D0CE106ED46FB635B8 |
| hashlookup:parent-total | 1 |
| hashlookup:trust | 55 |
The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:
| Key | Value |
|---|---|
| FileSize | 33974 |
| MD5 | 1D06991721A5BA3089934EBA39452052 |
| PackageDescription | OpenStack Profiler Library - doc OpenStack consists of multiple projects. Each project, in turn, is composed of multiple services. To process some request, e.g. to boot a virtual machine, OpenStack uses multiple services from different projects. In the case somethin works too slowly, it's extremely complicated to understand what exactly goes wrong and to locate the bottleneck. . To resolve this issue, a tiny but powerful library, osprofiler, has been interoduced, and can be used by all OpenStack projects and their Python clients. To be able to generate one trace per request, that goes through all involved services, and builds a tree of calls (see an example http://pavlovic.me/rally/profiler/). . This package contains the documentation. |
| PackageMaintainer | PKG OpenStack <openstack-devel@lists.alioth.debian.org> |
| PackageName | python-osprofiler-doc |
| PackageSection | doc |
| PackageVersion | 1.4.0-2 |
| SHA-1 | F25A9580F792104128A2CDDDA4E24C0FDE2B57FC |
| SHA-256 | 364A1B7F3B9BAAD442A547D5D396EBA8F3134E3980C94F824E89BEF01F0D1321 |