Take the community feedback survey now.
Take the community feedback survey now.
Hello ,
The Dowtime is correct as you attached in the screenshot , number of site down per minute .
Now as you mentioned that you are exposing your site to specific customer not to all.
here is the catch is happeing as per me , that other user's traffic is also coming to your site and then they see 403 or 500 over there , which also get added into the count and that is why it shows that number to you.
my best suggetion would be if you have specifc people to visit the site make it limited to them and just show them some login screen like SSO login page or somthing
so that instead 404 or 500 they land to a page which is working and it will improve the score.
I think they are using either Pingdom or Application Insights availability tests for that number.
Sometimes one container go down and I recall we've seen that it's not picked up by Pingdom so load balancing and which instance the check ends up on is also a factor.
A sticky session on a failing container will think your site is down but sessions ending up on other instances are happy at the same time.
Hey all, we're running a DXC site and have been for a long time now, very happy.
Recently though we've seen some instances of this Availability number on the DXC dashboard being lower than somewhere above 99.8% It has caused concern in our leadership with HOW MUCH downtime our site users might be seeing.
We see that the defintion of availability is below and it talks about minutes, BUT we're hearing from Opti support that HTTP resposne codes like 403 or 500 might ALSO contriubute to down minutes.
403 is a problem because we block a lot of IPs and ASNs from access to our site. They get 403s back from us because we don't want their traffic. Our site is NOT DOWN, it's up for the cusotmers we want.
So, what is the DEFINTION of downtime? What type of check is being run here to determine these numbers?
We thought before that it was a simple client request to our homepage and if there was ANY HTTP response that was UP and if there was no resposne from the host that was DOWN.
But now we're thinking that maybe it's more complicated than that.