2019-12-28 04:01:34 UTC - Nima Mahmoudi: Thanks everyone for helping with this. Is there a step-by-step guide to enabling the monitoring and adding it to prometheus? I still don't know which route I should add to the prometheus I have running on the server.
I have come up with a very accurate performance model for serverless computing and tested it with AWS Lambda. I was hoping I could integrate it into openwhisk to enhance the performance through parameter optimization based on workload characteristics. Is anyone interested in helping me add this as a feature? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1577505694079300?thread_ts=1577300028.062300&cid=C3TPCAQG1 ---- 2019-12-28 04:11:20 UTC - chetanm: What type of deployment you are having. Is it bare metal using ansible or on k8s https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1577506280079600?thread_ts=1577300028.062300&cid=C3TPCAQG1 ---- 2019-12-28 16:40:10 UTC - Nima Mahmoudi: @chetanm It is bare metal using ansible. I have enabled prometheus in the configuration, but don't know which route to add to prometheus to be able to get the statistics. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1577551210079900?thread_ts=1577300028.062300&cid=C3TPCAQG1 ---- 2019-12-28 18:59:29 UTC - chetanm: You can connect to controller and invoker ip at /,metrics endpoint https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1577559569080300?thread_ts=1577300028.062300&cid=C3TPCAQG1 ---- 2019-12-28 21:53:39 UTC - Nima Mahmoudi: @chetanm Thanks a lot. Which port is that on? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1577570019080500?thread_ts=1577300028.062300&cid=C3TPCAQG1 ---- 2019-12-28 23:26:40 UTC - Nima Mahmoudi: For example, my invoker is on 172.17.0.23, I should be able to curl the 172.17.0.23:XXXX/metrics path, right? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1577575600080700?thread_ts=1577300028.062300&cid=C3TPCAQG1 ----
