1. When an event occurs "Application unknown state"?
2. How to simulate Application status unknown for testing Alert triger condition (for example MS SQL) ?
Lots of different things can cause unknown statuses for monitors. A few that come to mind:
Insufficient licenses for assigned components.
Ephemeral Port Exhaustion on a poller.
Polling timeouts.
Script timeouts or failure to return statistics.
I'm sure there are more, but those are just some that I run into on the regular or have run into in the past.
To simulate one, if you're testing with a script you could easily make it unknown by returning something SAM doesn't expect or causing the script to fail. For example, if you're expecting "Statistic: 1" to return and it instead returns "Statistic: One" (a word/string) then that should cause the monitor to go into an unknown state.
1. Do you mean:
- What does the "unknown" status mean? (A: the test failed to complete)
or
- What causes the "Application Unknown State" event? (A: an application's status changed to unknown, see above)
Something else?
2. Usually a non-configured Appinsight monitor ends up as Unknown. I'd be surprised if there wasnt a few in the environment anyway. Perhaps apply a SNMP monitor to a WMI node.
