How do SAS SWO/launched pods know to communicate with deployed Prometheus Pushgateway?

[EyalGonen]

Hi experts,

When I deploy the viya4-monitoring-kubernetes  tools on OCP, it deploys the Prometheus Pushgateway in the SAS Viya namespace.

I am puzzled as I do not see anywhere how does SAS Viya "know" to communicate with this newly deployed gateway.

I mean, where do I define to SAS Viya the name of the Pushgateway service and port number so it can push SWO or launched job metrics to this gateway?

[gwootton · Accepted solution]

The default URL is coded into Workload Orchestrator, though as of 2024.09 you can customize this URL with $deploy/sas-bases/examples/sas-workload-orchestrator/configure/sas-workload-orchestrator-prometheus-pushgateway-url.yaml A README.md in the same path describes its usage.

[EyalGonen]

Hi @gwootton 

If I disable SWO using the 

- sas-bases/overlays/sas-workload-orchestrator/enable-disable/sas-workload-orchestrator-disable-patch-transformer.yaml transformer - will the launched pods still report their metrics to prometheus-gateway or not?

[gwootton]

If you were to disable SAS Workload Orchestrator, the "SAS Launched Jobs" dashboards would not function. The pushgateway is used by SWO and not the individual jobs. You'd still get metrics on the pods just as you do for non-job pods in the environment through the other dashboards.

Dashboards that Require a License or Enablement:
https://go.documentation.sas.com/doc/en/obsrvcdc/v_003/obsrvdply/n1sg9bc44ow616n1sw7l3dlsbmgz.htm#p0...