/streamz help
Streamz Root:
Streamz ManuallySampledMetrics set:
Root name: <default> [(+) labels] [(+) collection] [(+) largest exported metrics]
Search:
/stubs/message_supplier/suppliers_created (cumulative): long = 193
Number of MessageSupplier instances created. When MessageSupplier is used, typically one instance of MessageSupplier will be created for each request that is being sent through an Extensible Stubs pipe of behaviors: the caller (sending the request to Extensible Stubs) will typically provide an `output` instance, in which it will eventually consume the response. MessageSupplier implements an optimization where in the vast majority of cases we can avoid having to copy response payloads (by carefully passing instances around and keeping track of ownership). This implementation is expected to reduce the CPU costs of using Extensible Stubs with servers that return large response payloads. If this counter is zero, that means that your process (or job) is not using MessageSupplier (which may be perfectly fine: it may be just that it doesn't need this optimization). We expect that the most common user of MessageSupplier will be the internal (to Extensible Stubs) class StubsClientChannel (through CreateGenericRequestFromRPC).
defined at production/rpc/stubs/base/message_supplier.cc:21 with annotations: CUMULATIVE=true