|
2047 | 2047 | This metric tracks the runtime of phase2 of an Agency sync. Phase2 calculates |
2048 | 2048 | what actions to execute given the difference of the local and target state. |
2049 | 2049 |
|
| 2050 | +- name: arangodb_network_connectivity_failures_coordinators_total |
| 2051 | + introducedIn: "3.11.4" |
| 2052 | + help: | |
| 2053 | + Number of failed connectivity check requests sent to Coordinators. |
| 2054 | + unit: number |
| 2055 | + type: counter |
| 2056 | + category: Network |
| 2057 | + complexity: simple |
| 2058 | + exposedBy: |
| 2059 | + - coordinator |
| 2060 | + - dbserver |
| 2061 | + description: | |
| 2062 | + Number of failed connectivity check requests sent by this instance |
| 2063 | + to Coordinators. |
| 2064 | + The metric will be increased if a cluster-internal connection to a |
| 2065 | + Coordinator cannot be established within 10 seconds. In this case the |
| 2066 | + instance will also log a warning. |
| 2067 | + Connectivity checks run with a configurable frequency, adjustable via |
| 2068 | + the `--cluster.connectivity-check-interval` startup option. |
| 2069 | + |
| 2070 | + troubleshoot: | |
| 2071 | + If this metric keeps increasing permanently or for longer periods, there |
| 2072 | + are likely network connectivity issues or misconfigurations, which can |
| 2073 | + prevent the instance from connecting to every Coordinator in the cluster |
| 2074 | + (potentially connecting to itself). In this case it is advised to check |
| 2075 | + the connectivity manually, and ensure that the instance can make connections |
| 2076 | + to all Coordinators, potentially including itself. |
| 2077 | + |
| 2078 | + If there are temporary network glitches or instance restarts, this metric |
| 2079 | + can also increase. But increases should stop once the network has stabilized |
| 2080 | + and/or instances have restarted successfully. |
| 2081 | +
|
| 2082 | +- name: arangodb_network_connectivity_failures_dbservers_total |
| 2083 | + introducedIn: "3.11.4" |
| 2084 | + help: | |
| 2085 | + Number of failed connectivity check requests sent to DB-Servers. |
| 2086 | + unit: number |
| 2087 | + type: counter |
| 2088 | + category: Network |
| 2089 | + complexity: simple |
| 2090 | + exposedBy: |
| 2091 | + - coordinator |
| 2092 | + - dbserver |
| 2093 | + description: | |
| 2094 | + Number of failed connectivity check requests sent by this instance |
| 2095 | + to DB-Server. |
| 2096 | + The metric will be increased if a cluster-internal connection to a |
| 2097 | + DB-Server cannot be established within 10 seconds. In this case the |
| 2098 | + instance will also log a warning. |
| 2099 | + Connectivity checks run with a configurable frequency, adjustable via |
| 2100 | + the `--cluster.connectivity-check-interval` startup option. |
| 2101 | + |
| 2102 | + troubleshoot: | |
| 2103 | + If this metric keeps increasing permanently or for longer periods, there |
| 2104 | + are likely network connectivity issues or misconfigurations, which can |
| 2105 | + prevent the instance from connecting to every DB-Server in the cluster |
| 2106 | + (potentially connecting to itself). In this case it is advised to check |
| 2107 | + the connectivity manually, and ensure that the instance can make connections |
| 2108 | + to all DB-Servers, potentially including itself. |
| 2109 | + |
| 2110 | + If there are temporary network glitches or instance restarts, this metric |
| 2111 | + can also increase. But increases should stop once the network has stabilized |
| 2112 | + and/or instances have restarted successfully. |
| 2113 | +
|
2050 | 2114 | - name: arangodb_network_dequeue_duration |
2051 | 2115 | introducedIn: "3.10.6" |
2052 | 2116 | help: | |
|
0 commit comments