Unknown status reporting as unavailable

Question

Hello,

Is there any way for the unknown status (that is caused by problems with Orion engine and not by unavailability of the nodes) not to count for the availability metric?

We've got groups with 100% weekly availability but when we generate a weekly availability report it says 99,8% or 99,7% for example.

Here is an example of this situation, state changes and impact on the availability of the last 24h

Thanks all

mesverrum · Answer

I know a few people I was talking to brought it up to some of the SW PM's I was speaking with a few months ago and they seemed surprised, felt like some product teams thought it would work one way and the other team thought the reverse.  We definitely leaned on them that it was very important for the product to do this calculation consistently across all modules but we didn't get anything like a firm plan to sort it out at the time.

swptout · Answer

Just to put it out there, I've got an answer from support regarding this and they have explained that this is by design, Solarwinds counts the unknown state as Down status for an element of the group, which means that when I stop Solarwinds for some maintenance reason and restart it 5 minutes later then all groups will have a 5 minute downtime in their availability report.

Putting aside that this makes absolutly no sense at all, has anyone been able to build an availability report that ignores this unknown states? We haven't been able to do it and it makes all group availability reports useless...

Thanks