Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

AppInsight SQL Up Events

solaradmin

Every few hours my event summary displays this

3-12-2014 10-28-38 AM.png

I can never find why or when the monitors weren't up. Is it just reminding me that I have these monitors?

and most (98%) are always back at the same time.

3-12-2014 10-30-52 AM.png

Find more posts tagged with

Accepted answers

All comments

Petr.Vilem

Was not some of SolarWinds services restarted (e.g. crashed & restarted automatically) that time?

solaradmin

not that I am aware of. I have been using it all morning.

Maybe they just constantly go into warning?

I guess if there was a way to not log these as events that would solve my issue.

Petr.Vilem

Is it possible that Warning & Critical events are generated only for application level, but Up events are generated for both (application & component)? How does history of events look like for come of these components?

solaradmin

I think you may be onto it. Because the "Component Total Size Change 24 Hours" would never go into a warning state because there is no bad vs good. Yet in the event view it shows it as coming back up for every database on one of my appinsight sql servers.

So next question would be if anyone else has this issue?

solaradmin

Thanks for the report. At least I know now what components I should adjust the baseline
3-13-2014 11-38-50 AM.png

Petr.Vilem

And did it help you to confirm that "Total Size Change 24 Hours" (or any other) component has only "UP" events without corresponding opposite events? If so, I would recommend opening support ticket as aLTeReGo suggested.