From 2df7c56eaae156a27a30fa8247a11168082e9ef1 Mon Sep 17 00:00:00 2001 From: bstrzele Date: Thu, 2 Jan 2025 13:38:55 +0000 Subject: [PATCH] documentation --- docs/metrics.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/metrics.md b/docs/metrics.md index 99bcc10c5c..8a6e2b3b04 100644 --- a/docs/metrics.md +++ b/docs/metrics.md @@ -241,6 +241,7 @@ For [MediaPipe Graphs](./mediapipe.md) execution there are 4 generic metrics whi | counter | ovms_responses | Useful to track number of packets generated by MediaPipe graph. Keep in mind that single request may trigger production of multiple (or zero) packets, therefore tracking number of responses is complementary to tracking accepted requests. For example tracking streaming partial responses of LLM text generation graphs. | | gauge | ovms_current_graphs | Number of graphs currently in-process. For unary communication it is equal to number of currently processing requests (each request initializes separate MediaPipe graph). For streaming communication it is equal to number of active client connections. Each connection is able to reuse the graph and decide when to delete it when the connection is closed. | | counter | ovms_graph_error | Counts errors in MediaPipe graph execution phase. For example V3 LLM text generation fails in LLMCalculator due to missing prompt - calculator returns an error and graph cancels. | +| histogram | ovms_graph_processing_time_us | Time for which mediapipe graph was opened. | Exposing custom metrics in calculator implementations (MediaPipe graph nodes) is not supported yet.