Following our NTA 4.1.2 upgrade, I have noticed intermittent slow downs of the web console. Sometimes resource throw errors (Cannot load resource ID x), load continuously or don't load at all. Most of the time it can be fixed with a refresh of the page. I went through OrionWeb.log and noticed this entry many times. Are you able to tell what it is doing? Is there a way to clean this up? We are running 11.5.2. I have no idea why an NTA upgrade from 4.1.1 to 4.1.2 would cause these issues.
Did you do a migration? Did you upgrade the netflow storage before upgrading the application?
No, we performed the migration from SQL to the Flow Storage DB last August. Yes, I ran the upgrade on the Flow Database first and then updated the Primary Poller and the APEs.
Ok, when was the last time maintenance on the nta storage was completed?
It runs daily and has run every day since the upgrade.
I have had a similar issue recently. For me it turned out that the daily maintenance wasn't enough and I had to have our DBA rebuild the index (based on support's recommendation). It has been performing better since then and the indexes aren't out of control yet. I currently planning on doing that 1-2 times a year.
Is this on the Orion DB or the Flow Database?
The flow database. I would also check the orion database as the website files are located there.
I was working to add a new alert rule this morning and I randomly am getting "Cannot Load Trigger Condition". I refresh a few times and then it works. Any ideas?
bharris check the indexed on the orion database.
jkrenzien any update on the orion database?
jamesatloop1 - after i rebuilt my indexes with sql scripts I found here on thwack, SolarWind's YouTube and some research trying to verify that I wouldn't kill my database with those scripts my performance increase and has become much more stable.
jamesatloop1 - We had maintenance on our SQL Servers last night and after they came back up the slowdowns and error messages in resources are gone. I wonder if there was something hosed up on the SQL server and a restart of the services fixed it.
Your database was probably heavily fragmented id say. Having resource errors on the website is usually database or under resourcing.