gorgeous-beach-23305
06/07/2023, 1:39 PM<http://prometheus.io/scrape|prometheus.io/scrape>
, <http://prometheus.io/port|prometheus.io/port>
, <http://prometheus.io/path|prometheus.io/path>
being applied automatically. Also, we can find any config setting to enable this. Should this be happening automatically on deploy or we need to change some config setting. Also, found this where port number is mentioned, but the flyte-binary pod only exposes 8088, 8089 and 9443, not 10254, should that be exposed somehow as well?freezing-boots-56761
freezing-boots-56761
gorgeous-beach-23305
06/07/2023, 4:03 PMfreezing-boots-56761
containerPort
?gorgeous-beach-23305
06/07/2023, 4:06 PMgorgeous-beach-23305
06/07/2023, 4:06 PMfreezing-boots-56761
gorgeous-beach-23305
06/07/2023, 5:26 PMgorgeous-beach-23305
06/08/2023, 1:11 PMflyte:propeller:all:free_workers_count
flyte:propeller:all:round:abort_error[5m]
flyte:propeller:all:round:system_error_unlabeled[5m]
flyte:propeller:all:node:plugin:.*_failure_unlabeled
flyte:propeller:all:node:plugin:.*_success_unlabeled
flyte:propeller:all:round:raw_unlabeled_ms[5m]
flyte:propeller:all:round:raw_ms[5m]
flyte:propeller:all:round:panic_unlabeled[5m]
flyte:propeller:all:collector:flyteworkflow
flyte:propeller:all:metastore:cache_hit
flyte:propeller:all:metastore:cache_miss
flyte:propeller:all:metastore:head_failure_unlabeled
But on datadog, when I search metrics for "Propeller", I can only see these -
flyte_admin_admin_builder_flytepropeller_build_failures.count
flyte_admin_admin_builder_flytepropeller_build_successes.count
flyte_admin_admin_execution_manager_propeller_failures.count
1. Why aren't we seeing all the metrics for propeller? (for metastore, plugin etc) and
2. Why are the metrics names different, is there some aggregation happening somewhere?freezing-boots-56761
freezing-boots-56761
freezing-airport-6809
freezing-boots-56761
gorgeous-beach-23305
06/08/2023, 2:31 PMmillions-table-8574
08/09/2023, 8:34 AMmillions-table-8574
08/10/2023, 7:52 AMit needs to be explicitly added here@freezing-boots-56761 - we installed flyte-binary using helm in eks and utilising flyreorg’s repo. if this needs to be explicitly added, does that mean we’ll need to manage the chart on our own, since
ports
isn’t exposed via values.yaml
?freezing-boots-56761
millions-table-8574
08/10/2023, 9:17 AM# deployment.yaml
ports:
- name: http
containerPort: 8088
- name: grpc
containerPort: 8089
- name: webhook
containerPort: 9443
{{- if .Values.deployment.profilerPort }}
- name: profiler
containerPort: {{ .Values.deployment.profilerPort }}
{{- end }}
# values.yaml
deployment:
...
profilerPort: 10254
or just remove the if
and hardcode it like the other ports in deployment.yaml
freezing-boots-56761