Thanks for the update @AjmalFarzam
I can see details (& blogs of course) on the new ways logs & metrics are available in Viya4. My question is really on the continuation of the MAS metrics currently available in Viya3.5, rather than the generic JVM type ones that are generated. I've already been using a tweaked version of this for instance to monitor multiple Viya3.5 microservices.
These MAS metrics are in addition to those that come out of the other microservices:
# HELP mas_module_execution_seconds
# TYPE mas_module_execution_seconds summary
mas_module_execution_seconds_count{module="echo",tenant="provider",} 6.0
mas_module_execution_seconds_sum{module="echo",tenant="provider",} 0.066334917
# HELP mas_module_execution_seconds_max
# TYPE mas_module_execution_seconds_max gauge
mas_module_execution_seconds_max{module="echo",tenant="provider",} 0.0
# HELP mas_module_score_max describes how scores are distributed
# TYPE mas_module_score_max gauge
mas_module_score_max{module="echo",tenant="provider",} 0.0
# HELP mas_module_score_max decribes how scores are distributed
# TYPE mas_module_score_max gauge
mas_module_score_max{module="echo",tenant="provider",} 0.0
# HELP mas_module_score decribes how scores are distributed
# TYPE mas_module_score summary
mas_module_score_count{module="echo",tenant="provider",} 2.0
mas_module_score_sum{module="echo",tenant="provider",} 300.0
# HELP mas_module_availability
# TYPE mas_module_availability gauge
mas_module_availability{module="lmedt22s6fzaztjs5unrc2ryfzq",tenant="provider",}
1.0
mas_module_availability{module="hmeq_value",tenant="provider",} 1.0
mas_module_availability{module="dcm_treatments_
c2eca78a_2624_4744_9ffd_e238eec02ec2",tenant="provider",} 1.0
mas_module_availability{module="logistic_regression_
06e7bffb_89f3_4775_8bd8_029793970f91",tenant="provider",} 1.0
mas_module_availability{module="sql_executer",tenant="provider",} 1.0
mas_module_availability{module="echo",tenant="provider",} 1.0
# HELP mas_modules_availability
# TYPE mas_modules_availability gauge
mas_modules_availability{tenant="provider",} 1.0
# HELP mas_core_memoryused
# TYPE mas_core_memoryused gauge
mas_core_memoryused 8.33036288E8
These are invaluable in creating dashboards to show how MAS is performing real-time - are these continued into Viya4? They have gone from the online docs as far as I can tell.
Regards
Alan
... View more