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
5. The `dependency_up` is a metric to register whether a specific dependency is up (1) or down (0). The label `name` registers the dependency name;
29
32
30
-
6. The `application_info` holds static info of an application, such as it's semantic version number;
33
+
6. The `dependency_request_seconds_bucket` is a metric that defines the histogram of how many requests to a specific dependency are falling into the well defined buckets represented by the label le;
34
+
35
+
7. The `dependency_request_seconds_count` is a counter that counts the overall number of requests to a specific dependency;
36
+
37
+
8. The `dependency_request_seconds_sum` is a counter that counts the overall sum of how long requests to a specific dependency are taking;
38
+
39
+
9. The `application_info` holds static info of an application, such as it's semantic version number;
31
40
32
41
Labels:
33
42
@@ -43,6 +52,10 @@ Labels:
43
52
44
53
6.`isError` lets us know if the status code reported is an error or not;
> The dependency checkers will run on a new thread, to prevent memory leak, make sure to call the method ``MonitorMetrics.INSTANCE.cancelAllDependencyCheckers()`` on undeploying/terminating the web app.
223
236
237
+
You also can monitore a dependency event. Just call `addDependencyEvent` and pass the right params.
0 commit comments