You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there is no way to distinguish Datadog metrics for e.g. GET &
POST requests for the same endpoint within a single Apisix route,
although their performance characteristics are likely to be quite
different.
With these changes, if `include_method` is set to true, HTTP method is
included as a metric tag with the `method:` key, enabling such requests
to be differentiated.
| prefer_name | boolean | False | true |[true,false]| When set to `false`, uses Route/Service ID instead of name (default) with metric tags. |
47
+
| include_path | boolean | False | false |[true,false]| When set to `true`, includes the path pattern in metric tags. |
48
+
| include_method | boolean | False | false |[true,false]| When set to `true`, includes the HTTP method in metric tags. |
48
49
49
50
This Plugin supports using batch processors to aggregate and process entries (logs/data) in a batch. This avoids the need for frequently submitting the data. The batch processor submits data every `5` seconds or when the data in the queue reaches `1000`. See [Batch Processor](../batch-processor.md#configuration) for more information or setting your custom configuration.
50
51
@@ -117,6 +118,7 @@ The metrics will be sent to the DogStatsD agent with the following tags:
117
118
-`response_status`: HTTP response status code.
118
119
-`scheme`: Request scheme such as HTTP, gRPC, and gRPCs.
119
120
-`path`: The HTTP path pattern. Only available if the attribute `include_path` is set to true.
121
+
-`method`: The HTTP method. Only available if the attribute `include_method` is set to true.
0 commit comments