| Index | index by Group | index by Distribution | index by Vendor | index by creation date | index by Name | Mirrors | Help |
The search service can find package by either name (apache), provides(webserver), absolute file names (/usr/bin/apache), binaries (gprof) or shared libraries (libXm.so.2) in standard path. It does not support multiple arguments yet...
The System and Arch are optional added filters, for example System could be "redhat", "redhat-7.2", "mandrake" or "gnome", Arch could be "i386" or "src", etc. depending on your system.
OTObserver can be used to watch the span events like StartSpan(), SetOperationName(), SetTag() and Finish(). A need for observers arose when information (metrics) more than just the latency information was required for the spans, in the distributed tracers. But, there can be a lot of metrics in different domains and adding such metrics to any one (client) tracer breaks cross-platform compatibility. There are various ways to avoid such issues, however, an observer pattern is cleaner and provides loose coupling between the packages exporting metrics (on span events) and the tracer. This information can be in the form of hardware metrics, RPC metrics, useful metrics exported out of the kernel or other metrics, profiled for a span. These additional metrics can help us in getting better Root-cause analysis. With that being said, its not just for calculation of metrics, it can be used for anything which needs watching the span events. This package contains the source code needed for building packages that reference the following Go import paths: – github.com/opentracing-contrib/go-observer
Generated by rpm2html 1.6