MOnitoring OKTA URLS
Posted: Wed Oct 10, 2018 11:26 am
Currently we have basic url checks for our java applications like so
http://xxx.xxx.xxx.xxx:8080/app or http://xxx.xxx.xxx.xxx:8080/healthcheck
We are able to monitor each JVM directly, so that if any app behind the load balancer is down
We know immediately. We also monitor the load balanced url.
HOWEVER
Once we have integrated the app with OKTA, we get redirected back okta like so
http://xxx.xxx.xxxx.xxx:800/app okta server (authentication) load balanced url.
We need a way to monitor a specific instance of an okta integrated app.
I’m sure this is a well know and well solved problem, but I have not come across anything.
Please advise.
http://xxx.xxx.xxx.xxx:8080/app or http://xxx.xxx.xxx.xxx:8080/healthcheck
We are able to monitor each JVM directly, so that if any app behind the load balancer is down
We know immediately. We also monitor the load balanced url.
HOWEVER
Once we have integrated the app with OKTA, we get redirected back okta like so
http://xxx.xxx.xxxx.xxx:800/app okta server (authentication) load balanced url.
We need a way to monitor a specific instance of an okta integrated app.
I’m sure this is a well know and well solved problem, but I have not come across anything.
Please advise.