Expose advanced metrics #124
Comments
kuritka
added a commit
that referenced
this issue
Jan 14, 2021
This is first of PR - move Dig to utils - move prettyPrint to utils and rename to `ToJSON()` - cover `ToJSON()` by tests - move environment variable `POD_NAMESPACE` to `depresolver` - extend depresolver tests - extend depresolver validators for namespace validator - Extract Prometheus metrics into standalone module - Extend prometheus metrics - Fix controller tests - remove dead registry/k3s.yaml file (pushed by mistake) TODO: - dnsupdate refactor to provider pattern in next PR - fianally, some of utils will go into [gopkg](https://github.com/AbsaOSS/gopkg) - IMetrics introduction (#124)
kuritka
added a commit
that referenced
this issue
Jan 14, 2021
This is first of PR - move Dig to utils - move prettyPrint to utils and rename to `ToJSON()` - cover `ToJSON()` by tests - move environment variable `POD_NAMESPACE` to `depresolver` - extend depresolver tests - extend depresolver validators for namespace validator - Extract Prometheus metrics into standalone module - Extend prometheus metrics - Fix controller tests - remove dead registry/k3s.yaml file (pushed by mistake) TODO: - dnsupdate refactor to provider pattern in next PR - fianally, some of utils will go into [gopkg](https://github.com/AbsaOSS/gopkg) - IMetrics introduction (#124)
kuritka
added a commit
that referenced
this issue
Jan 14, 2021
This is first of PR - move Dig to utils - move prettyPrint to utils and rename to `ToJSON()` - cover `ToJSON()` by tests - move environment variable `POD_NAMESPACE` to `depresolver` - extend depresolver tests - extend depresolver validators for namespace validator - Extract Prometheus metrics into standalone module - Extend prometheus metrics - Fix controller tests - remove dead registry/k3s.yaml file (pushed by mistake) TODO: - dnsupdate refactor to provider pattern in next PR - fianally, some of utils will go into [gopkg](https://github.com/AbsaOSS/gopkg) - IMetrics introduction (#124)
kuritka
added a commit
that referenced
this issue
Jan 15, 2021
This is first of PR - move Dig to utils - move prettyPrint to utils and rename to `ToJSON()` - cover `ToJSON()` by tests - move environment variable `POD_NAMESPACE` to `depresolver` - extend depresolver tests - extend depresolver validators for namespace validator - Extract Prometheus metrics into standalone module - Extend prometheus metrics - Fix controller tests - remove dead registry/k3s.yaml file (pushed by mistake) TODO: - dnsupdate refactor to provider pattern in next PR - fianally, some of utils will go into [gopkg](https://github.com/AbsaOSS/gopkg) - IMetrics introduction (#124)
kuritka
added a commit
that referenced
this issue
Jan 15, 2021
This is first of PR - move environment variable `POD_NAMESPACE` to `depresolver` - extend depresolver tests - extend depresolver validators for namespace validator - Extract Prometheus metrics into standalone module - Extend prometheus metrics - Fix controller tests - remove dead registry/k3s.yaml file (pushed by mistake) TODO: - dnsupdate refactor to provider pattern in next PR - fianally, some of utils will go into [gopkg](https://github.com/AbsaOSS/gopkg) - IMetrics introduction (#124)
kuritka
added a commit
that referenced
this issue
Jan 15, 2021
This is first of PR - move environment variable `POD_NAMESPACE` to `depresolver` - extend depresolver tests - extend depresolver validators for namespace validator - Extract Prometheus metrics into standalone module - Extend prometheus metrics - Fix controller tests - remove dead registry/k3s.yaml file (pushed by mistake) TODO: - dnsupdate refactor to provider pattern in next PR - fianally, some of utils will go into [gopkg](https://github.com/AbsaOSS/gopkg) - IMetrics introduction (#124)
|
ℹ️ note : Consider implementing against the type IMetrics interface {
Register() error
Unregister() error
UpdateIngressHostsPerStatusMetric(gslb *k8gbv1beta1.Gslb, serviceHealth map[string]string)
UpdateHealthyRecordsMetric(gslb *k8gbv1beta1.Gslb, healthyRecords map[string][]string)
ConcreteMetricA() (data, err)
ConcreteMetricB() (data, err)
ConcreteMetricC() (data, err)
...
} |
kuritka
added a commit
that referenced
this issue
Jun 15, 2021
ted to #124 I created a PrometheusMetrics structure with one field - Port. The default port value is 9090 and defines where Prometheus metrics endpoint is listening. PrometheusMetrics structure can return metrics local address via `GetAddress()` function. At the moment I don’t expect we will expose metrics on other than “0.0.0.0” host, that’s why I hardcoded host value for now. (see: https://docs.openshift.com/container-platform/4.1/applications/operator_sdk/osdk-monitoring-prometheus.html#osdk-monitoring-prometheus-metrics-helper_osdk-monitoring-prometheus) I also removed flag.StringVar `"metrics-addr", ":8080”,` from `main.go` as moving inputs into depresolver (following PR will remove flags completely).
kuritka
added a commit
that referenced
this issue
Jun 15, 2021
ted to #124 I created a PrometheusMetrics structure with one field - Port. The default port value is 9090 and defines where Prometheus metrics endpoint is listening. PrometheusMetrics structure can return metrics local address via `GetAddress()` function. At the moment I don’t expect we will expose metrics on other than “0.0.0.0” host, that’s why I hardcoded host value for now. (see: https://docs.openshift.com/container-platform/4.1/applications/operator_sdk/osdk-monitoring-prometheus.html#osdk-monitoring-prometheus-metrics-helper_osdk-monitoring-prometheus) I also removed flag.StringVar `"metrics-addr", ":8080”,` from `main.go` as moving inputs into depresolver (following PR will remove flags completely). Signed-off-by: kuritka <kuritka@gmail.com>
kuritka
added a commit
that referenced
this issue
Jun 15, 2021
Related to #124 I created a PrometheusMetrics structure with one field - Port. The default port value is 9090 and defines where Prometheus metrics endpoint is listening. PrometheusMetrics structure can return metrics local address via `GetAddress()` function. At the moment I don’t expect we will expose metrics on other than “0.0.0.0” host, that’s why I hardcoded host value for now. (see: https://docs.openshift.com/container-platform/4.1/applications/operator_sdk/osdk-monitoring-prometheus.html#osdk-monitoring-prometheus-metrics-helper_osdk-monitoring-prometheus) I also removed flag.StringVar `"metrics-addr", ":8080”,` from `main.go` as moving inputs into depresolver (following PR will remove flags completely). Signed-off-by: kuritka <kuritka@gmail.com>
kuritka
added a commit
that referenced
this issue
Jun 15, 2021
Related to #124 I created a PrometheusMetrics structure with one field - Port. The default port value is 9090 and defines where Prometheus metrics endpoint is listening. PrometheusMetrics structure can return metrics local address via `GetAddress()` function. At the moment I don’t expect we will expose metrics on other than “0.0.0.0” host, that’s why I hardcoded host value for now. (see: https://docs.openshift.com/container-platform/4.1/applications/operator_sdk/osdk-monitoring-prometheus.html#osdk-monitoring-prometheus-metrics-helper_osdk-monitoring-prometheus) I also removed flag.StringVar `"metrics-addr", ":8080”,` from `main.go` as moving inputs into depresolver (following PR will remove flags completely). Signed-off-by: kuritka <kuritka@gmail.com>
kuritka
added a commit
that referenced
this issue
Jun 15, 2021
Related to #124 I created a PrometheusMetrics structure with one field - Port. The default port value is 9090 and defines where Prometheus metrics endpoint is listening. PrometheusMetrics structure can return metrics local address via `GetAddress()` function. At the moment I don’t expect we will expose metrics on other than “0.0.0.0” host, that’s why I hardcoded host value for now. (see: https://docs.openshift.com/container-platform/4.1/applications/operator_sdk/osdk-monitoring-prometheus.html#osdk-monitoring-prometheus-metrics-helper_osdk-monitoring-prometheus) I also removed flag.StringVar `"metrics-addr", ":8080”,` from `main.go` as moving inputs into depresolver (following PR will remove flags completely). Signed-off-by: kuritka <kuritka@gmail.com>
kuritka
added a commit
that referenced
this issue
Jun 15, 2021
Related to #124 I created a PrometheusMetrics structure with one field - Port. The default port value is 9090 and defines where Prometheus metrics endpoint is listening. PrometheusMetrics structure can return metrics local address via `GetAddress()` function. At the moment I don’t expect we will expose metrics on other than “0.0.0.0” host, that’s why I hardcoded host value for now. (see: https://docs.openshift.com/container-platform/4.1/applications/operator_sdk/osdk-monitoring-prometheus.html#osdk-monitoring-prometheus-metrics-helper_osdk-monitoring-prometheus) I also removed flag.StringVar `"metrics-addr", ":8080”,` from `main.go` as moving inputs into depresolver (following PR will remove flags completely). Signed-off-by: kuritka <kuritka@gmail.com>
kuritka
added a commit
that referenced
this issue
Jun 15, 2021
Related to #124 I created a MetricsAddress field. The default port value is “0.0.0.0:8080" and defines where Prometheus metrics endpoint is listening. (see: https://docs.openshift.com/container-platform/4.1/applications/operator_sdk/osdk-monitoring-prometheus.html#osdk-monitoring-prometheus-metrics-helper_osdk-monitoring-prometheus) I also removed flag.StringVar `"metrics-addr", ":8080”,` from `main.go` as moving inputs into depresolver (following PR will remove flags completely). Signed-off-by: kuritka <kuritka@gmail.com>
kuritka
added a commit
that referenced
this issue
Jun 15, 2021
Related to #124 I created a MetricsAddress field. The default port value is “0.0.0.0:8080" and defines where Prometheus metrics endpoint is listening. (see: https://docs.openshift.com/container-platform/4.1/applications/operator_sdk/osdk-monitoring-prometheus.html#osdk-monitoring-prometheus-metrics-helper_osdk-monitoring-prometheus) I also removed flag.StringVar `"metrics-addr", ":8080”,` from `main.go` as moving inputs into depresolver and also, removed enableLeaderElection and overall flags completely. Signed-off-by: kuritka <kuritka@gmail.com>
kuritka
added a commit
that referenced
this issue
Jun 15, 2021
Related to #124 I created a MetricsAddress field. The default port value is “0.0.0.0:8080" and defines where Prometheus metrics endpoint is listening. (see: https://docs.openshift.com/container-platform/4.1/applications/operator_sdk/osdk-monitoring-prometheus.html#osdk-monitoring-prometheus-metrics-helper_osdk-monitoring-prometheus) I also removed flag.StringVar `"metrics-addr", ":8080”,` from `main.go` as moving inputs into depresolver and also, removed enableLeaderElection and overall flags completely. Signed-off-by: kuritka <kuritka@gmail.com>
kuritka
added a commit
that referenced
this issue
Jun 15, 2021
Related to #124 I created a MetricsAddress field. The default port value is “0.0.0.0:8080" and defines where Prometheus metrics endpoint is listening. (see: https://docs.openshift.com/container-platform/4.1/applications/operator_sdk/osdk-monitoring-prometheus.html#osdk-monitoring-prometheus-metrics-helper_osdk-monitoring-prometheus) I also removed flag.StringVar `"metrics-addr", ":8080”,` from `main.go` as moving inputs into depresolver and also, removed enableLeaderElection and overall flags completely. Signed-off-by: kuritka <kuritka@gmail.com>
kuritka
added a commit
that referenced
this issue
Jun 16, 2021
Related to #124 I created a MetricsAddress field. The default port value is “0.0.0.0:8080" and defines where Prometheus metrics endpoint is listening. (see: https://docs.openshift.com/container-platform/4.1/applications/operator_sdk/osdk-monitoring-prometheus.html#osdk-monitoring-prometheus-metrics-helper_osdk-monitoring-prometheus) I also removed flag.StringVar `"metrics-addr", ":8080”,` from `main.go` as moving inputs into depresolver and also, removed enableLeaderElection and overall flags completely. Signed-off-by: kuritka <kuritka@gmail.com>
kuritka
added a commit
that referenced
this issue
Jun 16, 2021
Related to #124 I created a MetricsAddress field. The default port value is “0.0.0.0:8080" and defines where Prometheus metrics endpoint is listening. (see: https://docs.openshift.com/container-platform/4.1/applications/operator_sdk/osdk-monitoring-prometheus.html#osdk-monitoring-prometheus-metrics-helper_osdk-monitoring-prometheus) I also removed flag.StringVar `"metrics-addr", ":8080”,` from `main.go` as moving inputs into depresolver and also, removed enableLeaderElection and overall flags completely. Signed-off-by: kuritka <kuritka@gmail.com>
kuritka
added a commit
that referenced
this issue
Jun 18, 2021
related to #124 I want to see the metrics that will be implemented. That's why I'm adding the option to install prometheus on both clusters with `make deploy-prometheus`. Such deployed prometheus can scrapes metrics of k8gb operator and is accessible directly from the browser: - http://127.0.0.1:8080 - test-gslb1 - http://127.0.0.1:8081 - test-gslb2
kuritka
added a commit
that referenced
this issue
Jun 18, 2021
related to #124 I want to check metrics that will be implemented. That's why I'm adding the option to install prometheus on both clusters with `make deploy-prometheus`. Such deployed prometheus scrapes metrics of k8gb operator and is accessible directly from the browser: - http://127.0.0.1:8080 - test-gslb1 - http://127.0.0.1:8081 - test-gslb2
kuritka
added a commit
that referenced
this issue
Jun 18, 2021
related to #124 I want to check metrics that will be implemented. That's why I'm adding the option to install prometheus on both clusters with `make deploy-prometheus`. Such deployed prometheus scrapes metrics of k8gb operator and is accessible directly from the browser: - http://127.0.0.1:8080 - test-gslb1 - http://127.0.0.1:8081 - test-gslb2
kuritka
added a commit
that referenced
this issue
Jul 22, 2021
related to #124 In this pull request I implemented the metrics system in k8gb. I added one metric - counter incrementing the number of successful reconciliation loops. Adding specific metrics is part of the next PR. Like the logger, the metrics are accessed through a single singleton object and like the logger it is initialized. ```go var log = logging.Logger() var m = metrics.Metrics() ``` then anywhere in the code we can use this: ``` // increase the number of successful reconciliations m.ReconciliationIncrement() ``` The singleton is initialized in the `main()` function using the `metrics.Init(*config)` function. In case the singleton is not initialized, it will be set to the default value and all metrics will start with the prefix `k8gb_default` otherwise they will start with the prefix from the env variable `K8GB_NAMESPACE`. In addition to the singleton, I have changed the original metrics and added tests at the package level. In addition to the singleton, I significantly refactored the original metrics and added tests at the package level. The prometheus metrics implementation uses reflection. In short, I read the collectors structure during the runtime: ```go type collectors struct { HealthyRecords *prometheus.GaugeVec IngressHostsPerStatus *prometheus.GaugeVec ZoneUpdateTotal prometheus.Counter ReconciliationTotal prometheus.Counter } ``` Now I know all the types and names. From this I generate the map <name>: <instance>. I will then use the map for Register(), Unregister() and Get(). <name> is the name of the metric and is generated from the name of the structure in `collectors`. ReconciliationTotal => for example: `k8gb_gslb_healthy_records` (k8gb is `K8GB_NAMESPACE`) `Get()` is only for testing purposes - and is public only because controller_tests use metrics. I'll consider deleting tests from controller_tests and leaving only terratests and unit_tests at the package level (96% coverage now). But that will come in the next PR. Signed-off-by: kuritka <kuritka@gmail.com>
Closed
kuritka
added a commit
that referenced
this issue
Jul 22, 2021
related to #124 In this pull request I implemented the metrics system in k8gb. I added one metric - counter incrementing the number of successful reconciliation loops. Adding specific metrics is part of the next PR. Like the logger, the metrics are accessed through a single singleton object and like the logger it is initialized. ```go var log = logging.Logger() var m = metrics.Metrics() ``` then anywhere in the code we can use this: ``` // increase the number of successful reconciliations m.ReconciliationIncrement() ``` The singleton is initialized in the `main()` function using the `metrics.Init(*config)` function. In case the singleton is not initialized, it will be set to the default value and all metrics will start with the prefix `k8gb_default` otherwise they will start with the prefix from the env variable `K8GB_NAMESPACE`. In addition to the singleton, I have changed the original metrics and added tests at the package level. In addition to the singleton, I significantly refactored the original metrics and added tests at the package level. The prometheus metrics implementation uses reflection. In short, I read the collectors structure during the runtime: ```go type collectors struct { HealthyRecords *prometheus.GaugeVec IngressHostsPerStatus *prometheus.GaugeVec ZoneUpdateTotal prometheus.Counter ReconciliationTotal prometheus.Counter } ``` Now I know all the types and names. From this I generate the map <name>: <instance>. I will then use the map for Register(), Unregister() and Get(). <name> is the name of the metric and is generated from the name of the structure in `collectors`. ReconciliationTotal => for example: `k8gb_gslb_healthy_records` (k8gb is `K8GB_NAMESPACE`) `Get()` is only for testing purposes - and is public only because controller_tests use metrics. I'll consider deleting tests from controller_tests and leaving only terratests and unit_tests at the package level (96% coverage now). But that will come in the next PR. Signed-off-by: kuritka <kuritka@gmail.com>
kuritka
added a commit
that referenced
this issue
Jul 22, 2021
related to #124 In this pull request I implemented the metrics system in k8gb. I added one metric - counter incrementing the number of successful reconciliation loops. Adding specific metrics is part of the next PR. Like the logger, the metrics are accessed through a single singleton object and like the logger it is initialized. ```go var log = logging.Logger() var m = metrics.Metrics() ``` then anywhere in the code we can use this: ``` // increase the number of successful reconciliations m.ReconciliationIncrement() ``` The singleton is initialized in the `main()` function using the `metrics.Init(*config)` function. In case the singleton is not initialized, it will be set to the default value and all metrics will start with the prefix `k8gb_default` otherwise they will start with the prefix from the env variable `K8GB_NAMESPACE`. In addition to the singleton, I have changed the original metrics and added tests at the package level. In addition to the singleton, I significantly refactored the original metrics and added tests at the package level. The prometheus metrics implementation uses reflection. In short, I read the collectors structure during the runtime: ```go type collectors struct { HealthyRecords *prometheus.GaugeVec IngressHostsPerStatus *prometheus.GaugeVec ZoneUpdateTotal prometheus.Counter ReconciliationTotal prometheus.Counter } ``` Now I know all the types and names. From this I generate the map <name>: <instance>. I will then use the map for Register(), Unregister() and Get(). <name> is the name of the metric and is generated from the name of the structure in `collectors`. ReconciliationTotal => for example: `k8gb_gslb_healthy_records` (k8gb is `K8GB_NAMESPACE`) `Get()` is only for testing purposes - and is public only because controller_tests use metrics. I'll consider deleting tests from controller_tests and leaving only terratests and unit_tests at the package level (96% coverage now). But that will come in the next PR. Signed-off-by: kuritka <kuritka@gmail.com>
kuritka
added a commit
that referenced
this issue
Jul 22, 2021
related to #124 In this pull request I implemented the metrics system in k8gb. I added one metric - counter incrementing the number of successful reconciliation loops. Adding specific metrics is part of the next PR. Like the logger, the metrics are accessed through a single singleton object and like the logger it is initialized. ```go var log = logging.Logger() var m = metrics.Metrics() ``` then anywhere in the code we can use this: ``` // increase the number of successful reconciliations m.ReconciliationIncrement() ``` The singleton is initialized in the `main()` function using the `metrics.Init(*config)` function. In case the singleton is not initialized, it will be set to the default value and all metrics will start with the prefix `k8gb_default` otherwise they will start with the prefix from the env variable `K8GB_NAMESPACE`. In addition to the singleton, I have changed the original metrics and added tests at the package level. In addition to the singleton, I significantly refactored the original metrics and added tests at the package level. The prometheus metrics implementation uses reflection. In short, I read the collectors structure during the runtime: ```go type collectors struct { HealthyRecords *prometheus.GaugeVec IngressHostsPerStatus *prometheus.GaugeVec ZoneUpdateTotal prometheus.Counter ReconciliationTotal prometheus.Counter } ``` Now I know all the types and names. From this I generate the map <name>: <instance>. I will then use the map for Register(), Unregister() and Get(). <name> is the name of the metric and is generated from the name of the structure in `collectors`. ReconciliationTotal => for example: `k8gb_gslb_healthy_records` (k8gb is `K8GB_NAMESPACE`) `Get()` is only for testing purposes - and is public only because controller_tests use metrics. I'll consider deleting tests from controller_tests and leaving only terratests and unit_tests at the package level (96% coverage now). But that will come in the next PR. Signed-off-by: kuritka <kuritka@gmail.com>
kuritka
added a commit
that referenced
this issue
Jul 22, 2021
related to #124 In this pull request I implemented the metrics system in k8gb. I added one metric - counter incrementing the number of successful reconciliation loops. Adding specific metrics is part of the next PR. Like the logger, the metrics are accessed through a single singleton object and like the logger it is initialized. ```go var log = logging.Logger() var m = metrics.Metrics() ``` then anywhere in the code we can use this: ``` // increase the number of successful reconciliations m.ReconciliationIncrement() ``` The singleton is initialized in the `main()` function using the `metrics.Init(*config)` function. In case the singleton is not initialized, it will be set to the default value and all metrics will start with the prefix `k8gb_default` otherwise they will start with the prefix from the env variable `K8GB_NAMESPACE`. In addition to the singleton, I have changed the original metrics and added tests at the package level. In addition to the singleton, I significantly refactored the original metrics and added tests at the package level. The prometheus metrics implementation uses reflection. In short, I read the collectors structure during the runtime: ```go type collectors struct { HealthyRecords *prometheus.GaugeVec IngressHostsPerStatus *prometheus.GaugeVec ZoneUpdateTotal prometheus.Counter ReconciliationTotal prometheus.Counter } ``` Now I know all the types and names. From this I generate the map <name>: <instance>. I will then use the map for Register(), Unregister() and Get(). <name> is the name of the metric and is generated from the name of the structure in `collectors`. ReconciliationTotal => for example: `k8gb_gslb_healthy_records` (k8gb is `K8GB_NAMESPACE`) `Get()` is only for testing purposes - and is public only because controller_tests use metrics. I'll consider deleting tests from controller_tests and leaving only terratests and unit_tests at the package level (96% coverage now). But that will come in the next PR. Signed-off-by: kuritka <kuritka@gmail.com>
Merged
kuritka
added a commit
that referenced
this issue
Aug 10, 2021
related to #124 In this pull request I implemented the metrics system in k8gb. I added one metric - counter incrementing the number of successful reconciliation loops. Adding specific metrics is part of the next PR. Like the logger, the metrics are accessed through a single singleton object and like the logger it is initialized. ```go var log = logging.Logger() var m = metrics.Metrics() ``` then anywhere in the code we can use this: ``` // increase the number of successful reconciliations m.ReconciliationIncrement() ``` The singleton is initialized in the `main()` function using the `metrics.Init(*config)` function. In case the singleton is not initialized, it will be set to the default value and all metrics will start with the prefix `k8gb_default` otherwise they will start with the prefix from the env variable `K8GB_NAMESPACE`. In addition to the singleton, I have changed the original metrics and added tests at the package level. In addition to the singleton, I significantly refactored the original metrics and added tests at the package level. The prometheus metrics implementation uses reflection. In short, I read the collectors structure during the runtime: ```go type collectors struct { HealthyRecords *prometheus.GaugeVec IngressHostsPerStatus *prometheus.GaugeVec ZoneUpdateTotal prometheus.Counter ReconciliationTotal prometheus.Counter } ``` Now I know all the types and names. From this I generate the map <name>: <instance>. I will then use the map for Register(), Unregister() and Get(). <name> is the name of the metric and is generated from the name of the structure in `collectors`. ReconciliationTotal => for example: `k8gb_gslb_healthy_records` (k8gb is `K8GB_NAMESPACE`) `Get()` is only for testing purposes - and is public only because controller_tests use metrics. I'll consider deleting tests from controller_tests and leaving only terratests and unit_tests at the package level (96% coverage now). But that will come in the next PR. Signed-off-by: kuritka <kuritka@gmail.com>
kuritka
added a commit
that referenced
this issue
Aug 19, 2021
related to #124 This PR contains several specific metrics ```gaolang Health records *prometheus.GaugeVec StatusPerIngressHosts *prometheus.GaugeVec StatusFailover *prometheus.GaugeVec StatusRoundRobin *prometheus.GaugeVec StatusGeoIP *prometheus.GaugeVec ZoneUpdateTotal *prometheus.CounterVec ErrorTotal *prometheus.CounterVec ReconciliationTotal prometheus.Counter ``` Signed-off-by: kuritka <kuritka@gmail.com>
kuritka
added a commit
that referenced
this issue
Aug 19, 2021
related to #124 This PR contains several specific metrics ```gaolang Health records *prometheus.GaugeVec StatusPerIngressHosts *prometheus.GaugeVec StatusFailover *prometheus.GaugeVec StatusRoundRobin *prometheus.GaugeVec StatusGeoIP *prometheus.GaugeVec ZoneUpdateTotal *prometheus.CounterVec ErrorTotal *prometheus.CounterVec ReconciliationTotal prometheus.Counter ``` Signed-off-by: kuritka <kuritka@gmail.com>
kuritka
added a commit
that referenced
this issue
Aug 19, 2021
related to #124 This PR contains several specific metrics ```gaolang Health records *prometheus.GaugeVec StatusPerIngressHosts *prometheus.GaugeVec StatusFailover *prometheus.GaugeVec StatusRoundRobin *prometheus.GaugeVec StatusGeoIP *prometheus.GaugeVec ZoneUpdateTotal *prometheus.CounterVec ErrorTotal *prometheus.CounterVec ReconciliationTotal prometheus.Counter ``` Signed-off-by: kuritka <kuritka@gmail.com>
kuritka
added a commit
that referenced
this issue
Aug 19, 2021
related to #124 This PR contains several specific metrics ```gaolang Health records *prometheus.GaugeVec StatusPerIngressHosts *prometheus.GaugeVec StatusFailover *prometheus.GaugeVec StatusRoundRobin *prometheus.GaugeVec StatusGeoIP *prometheus.GaugeVec ZoneUpdateTotal *prometheus.CounterVec ErrorTotal *prometheus.CounterVec ReconciliationTotal prometheus.Counter ``` ```shell make destroy-full-local-setup deploy-full-local-setup upgrade-candidate deploy-prometheus make stop-test-app make start-test-app ```         Signed-off-by: kuritka <kuritka@gmail.com>
kuritka
added a commit
that referenced
this issue
Aug 19, 2021
related to #124 This PR contains several specific metrics ```gaolang Health records *prometheus.GaugeVec StatusPerIngressHosts *prometheus.GaugeVec StatusFailover *prometheus.GaugeVec StatusRoundRobin *prometheus.GaugeVec StatusGeoIP *prometheus.GaugeVec ZoneUpdateTotal *prometheus.CounterVec ErrorTotal *prometheus.CounterVec ReconciliationTotal prometheus.Counter ``` ```shell make destroy-full-local-setup deploy-full-local-setup upgrade-candidate deploy-prometheus make stop-test-app make start-test-app ```         Signed-off-by: kuritka <kuritka@gmail.com>
Closed
kuritka
added a commit
that referenced
this issue
Aug 23, 2021
related to #124 This PR contains several specific metrics ```gaolang Health records *prometheus.GaugeVec StatusPerIngressHosts *prometheus.GaugeVec StatusFailover *prometheus.GaugeVec StatusRoundRobin *prometheus.GaugeVec StatusGeoIP *prometheus.GaugeVec ZoneUpdateTotal *prometheus.CounterVec ErrorTotal *prometheus.CounterVec ReconciliationTotal prometheus.Counter ``` ```shell make destroy-full-local-setup deploy-full-local-setup upgrade-candidate deploy-prometheus make stop-test-app make start-test-app ```         Signed-off-by: kuritka <kuritka@gmail.com>
kuritka
added a commit
that referenced
this issue
Aug 23, 2021
related to #124 This PR contains several specific metrics ```gaolang Health records *prometheus.GaugeVec StatusPerIngressHosts *prometheus.GaugeVec StatusFailover *prometheus.GaugeVec StatusRoundRobin *prometheus.GaugeVec StatusGeoIP *prometheus.GaugeVec ZoneUpdateTotal *prometheus.CounterVec ErrorTotal *prometheus.CounterVec ReconciliationTotal prometheus.Counter ``` ```shell make destroy-full-local-setup deploy-full-local-setup upgrade-candidate deploy-prometheus make stop-test-app make start-test-app ```         Signed-off-by: kuritka <kuritka@gmail.com>
Merged
kuritka
added a commit
that referenced
this issue
Aug 23, 2021
related to #124 This PR contains several specific metrics ```gaolang Health records *prometheus.GaugeVec StatusPerIngressHosts *prometheus.GaugeVec StatusFailover *prometheus.GaugeVec StatusRoundRobin *prometheus.GaugeVec StatusGeoIP *prometheus.GaugeVec ZoneUpdateTotal *prometheus.CounterVec ErrorTotal *prometheus.CounterVec ReconciliationTotal prometheus.Counter ``` ```shell make destroy-full-local-setup deploy-full-local-setup upgrade-candidate deploy-prometheus make stop-test-app make start-test-app ```         Signed-off-by: kuritka <kuritka@gmail.com>
kuritka
added a commit
that referenced
this issue
Aug 24, 2021
related to #124 This PR contains several specific metrics ```gaolang Health records *prometheus.GaugeVec StatusPerIngressHosts *prometheus.GaugeVec StatusFailover *prometheus.GaugeVec StatusRoundRobin *prometheus.GaugeVec StatusGeoIP *prometheus.GaugeVec ZoneUpdateTotal *prometheus.CounterVec ErrorTotal *prometheus.CounterVec ReconciliationTotal prometheus.Counter ``` ```shell make destroy-full-local-setup deploy-full-local-setup upgrade-candidate deploy-prometheus make stop-test-app make start-test-app ```         Signed-off-by: kuritka <kuritka@gmail.com>
kuritka
added a commit
that referenced
this issue
Aug 24, 2021
related to #124 This PR contains several specific metrics ```gaolang Health records *prometheus.GaugeVec StatusPerIngressHosts *prometheus.GaugeVec StatusFailover *prometheus.GaugeVec StatusRoundRobin *prometheus.GaugeVec StatusGeoIP *prometheus.GaugeVec ZoneUpdateTotal *prometheus.CounterVec ErrorTotal *prometheus.CounterVec ReconciliationTotal prometheus.Counter ``` ```shell make destroy-full-local-setup deploy-full-local-setup upgrade-candidate deploy-prometheus make stop-test-app make start-test-app ```         Another metrics are: - k8gb_infoblox_heartbeats_total - k8gb_infoblox_heartbeat_errors_total - k8gb_infoblox_zone_updates_total - k8gb_infoblox_zone_update_errors_total Signed-off-by: kuritka <kuritka@gmail.com>
kuritka
added a commit
that referenced
this issue
Aug 24, 2021
related to #124 This PR contains several specific metrics ```gaolang Health records *prometheus.GaugeVec StatusPerIngressHosts *prometheus.GaugeVec StatusFailover *prometheus.GaugeVec StatusRoundRobin *prometheus.GaugeVec StatusGeoIP *prometheus.GaugeVec ZoneUpdateTotal *prometheus.CounterVec ErrorTotal *prometheus.CounterVec ReconciliationTotal prometheus.Counter ``` ```shell make destroy-full-local-setup deploy-full-local-setup upgrade-candidate deploy-prometheus make stop-test-app make start-test-app ```         Infoblox metrics are: - k8gb_infoblox_heartbeats_total - k8gb_infoblox_heartbeat_errors_total - k8gb_infoblox_zone_updates_total - k8gb_infoblox_zone_update_errors_total Signed-off-by: kuritka <kuritka@gmail.com>
kuritka
added a commit
that referenced
this issue
Aug 24, 2021
related to #124 This PR contains several specific metrics ```gaolang Health records *prometheus.GaugeVec StatusPerIngressHosts *prometheus.GaugeVec StatusFailover *prometheus.GaugeVec StatusRoundRobin *prometheus.GaugeVec StatusGeoIP *prometheus.GaugeVec ZoneUpdateTotal *prometheus.CounterVec ErrorTotal *prometheus.CounterVec ReconciliationTotal prometheus.Counter ``` ```shell make destroy-full-local-setup deploy-full-local-setup upgrade-candidate deploy-prometheus make stop-test-app make start-test-app ```         Infoblox metrics are: - k8gb_infoblox_heartbeats_total - k8gb_infoblox_heartbeat_errors_total - k8gb_infoblox_zone_updates_total - k8gb_infoblox_zone_update_errors_total Signed-off-by: kuritka <kuritka@gmail.com>
kuritka
added a commit
that referenced
this issue
Aug 24, 2021
related to #124 This PR contains several specific metrics ```gaolang Health records *prometheus.GaugeVec StatusPerIngressHosts *prometheus.GaugeVec StatusFailover *prometheus.GaugeVec StatusRoundRobin *prometheus.GaugeVec StatusGeoIP *prometheus.GaugeVec ZoneUpdateTotal *prometheus.CounterVec ErrorTotal *prometheus.CounterVec ReconciliationTotal prometheus.Counter ``` ```shell make destroy-full-local-setup deploy-full-local-setup upgrade-candidate deploy-prometheus make stop-test-app make start-test-app ```         Infoblox metrics are: - k8gb_infoblox_heartbeats_total - k8gb_infoblox_heartbeat_errors_total - k8gb_infoblox_zone_updates_total - k8gb_infoblox_zone_update_errors_total Signed-off-by: kuritka <kuritka@gmail.com>
kuritka
added a commit
that referenced
this issue
Aug 24, 2021
related to #124 This PR contains several specific metrics ```gaolang Health records *prometheus.GaugeVec StatusPerIngressHosts *prometheus.GaugeVec StatusFailover *prometheus.GaugeVec StatusRoundRobin *prometheus.GaugeVec StatusGeoIP *prometheus.GaugeVec ZoneUpdateTotal *prometheus.CounterVec ErrorTotal *prometheus.CounterVec ReconciliationTotal prometheus.Counter ``` ```shell make destroy-full-local-setup deploy-full-local-setup upgrade-candidate deploy-prometheus make stop-test-app make start-test-app ```         Infoblox metrics are: - k8gb_infoblox_heartbeats_total - k8gb_infoblox_heartbeat_errors_total - k8gb_infoblox_zone_updates_total - k8gb_infoblox_zone_update_errors_total Signed-off-by: kuritka <kuritka@gmail.com>
kuritka
added a commit
that referenced
this issue
Aug 25, 2021
related to #124 This PR contains several specific metrics ```gaolang Health records *prometheus.GaugeVec StatusPerIngressHosts *prometheus.GaugeVec StatusFailover *prometheus.GaugeVec StatusRoundRobin *prometheus.GaugeVec StatusGeoIP *prometheus.GaugeVec ZoneUpdateTotal *prometheus.CounterVec ErrorTotal *prometheus.CounterVec ReconciliationTotal prometheus.Counter ``` ```shell make destroy-full-local-setup deploy-full-local-setup upgrade-candidate deploy-prometheus make stop-test-app make start-test-app ```         Infoblox metrics are: - k8gb_infoblox_heartbeats_total - k8gb_infoblox_heartbeat_errors_total - k8gb_infoblox_zone_updates_total - k8gb_infoblox_zone_update_errors_total Signed-off-by: kuritka <kuritka@gmail.com>
kuritka
added a commit
that referenced
this issue
Aug 25, 2021
related to #124 This PR contains several specific metrics ```gaolang Health records *prometheus.GaugeVec StatusPerIngressHosts *prometheus.GaugeVec StatusFailover *prometheus.GaugeVec StatusRoundRobin *prometheus.GaugeVec StatusGeoIP *prometheus.GaugeVec ZoneUpdateTotal *prometheus.CounterVec ErrorTotal *prometheus.CounterVec ReconciliationTotal prometheus.Counter ``` ```shell make destroy-full-local-setup deploy-full-local-setup upgrade-candidate deploy-prometheus make stop-test-app make start-test-app ```         Infoblox metrics are: - k8gb_infoblox_heartbeats_total - k8gb_infoblox_heartbeat_errors_total - k8gb_infoblox_zone_updates_total - k8gb_infoblox_zone_update_errors_total Signed-off-by: kuritka <kuritka@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue is a spin off from #47
Implement relevant metrics that provide insight into:
#97 can be used as reference implementation
The text was updated successfully, but these errors were encountered: