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
Store

NPM event anomaly since upgrading to 9.5.1

This is interesting.... kind of. Thought I would post it on Thwack and see where we go before opening a ticket....

I recently noticed that when using the Outage resource by tdanner on my 9.5.1 server not all of my down nodes showed up. I thought is was a glitch and put it aside for a few days. Well, I had time to look into it today and what I am seeing is not an apparent issue with the Outage resource but what appears to be missing data out of my events table.

I took the SQL statement out of the Outage resource and put it into Studio so I could see what it would return. I only had one node come back. Currently I have 4 nodes down. Perplexed I started to drop off some of the where conditions until I should be able to see any down device. Still not.

So digging further I saw that the SQL statement is trying to match data based upon NodeID between the nodes and events table. I then did a distinct query to see if any of my down nodes ID's where in the Events table. They were not - hence the lack of them displaying.

Now the question here is how can I have down devices and no corresponding information in the events table?

I just checked my events table and am collecting recent outage information.

Any thoughts, ideas?

Find more posts tagged with

Accepted answers

tdanner

By default, Events get purged after 30 days (you can increase this in the Settings). So it might just be that these nodes have been down longer than that. A better version of the Outages resource could do an outer join to the Events table instead of an inner join. Then it could list all of the down nodes and only include "how long" information for nodes that are still whose "node has gone down" event is still in the Events table.

All comments

MarieB

Howdy Sotherls--

I'll make sure the PMs sees this--they can shed light on it. If it becomes time critical, open a support ticket.

Thanks,

bshopp

How long have those nodes that are down, but you cannot see in the view been down?

FormerMember

Looking at one of the nodes it has been down since 11/9/09.

I show it down but when I look at the Events table in the database using this query

select * from events where networknode = 1357

and nothing returns yet it is down.

tdanner

FormerMember

Tim,

Do you or your experts have a good way of me synchronizing my old events table with my new one? I am running parallel until I get the chance to go live on 9.5. I know this is database work and am familar enough with it. I tried to do a straight update from the old events to the new events but it balked.

Not knowing how the work flow is when an event happens I am not sure if doing a straight push to the events table would work - maybe have to use a stored procedure or a view.

Thoughts?