Monitor's for Application Health Overview after upgrade came in as "Sample" on all of our displays and also the Components aren't coming in. Does anyone know of this issue and a fix?
Did the Configuration Wizard complete without error? If you have any additional pollers or additional web servers in your environment, ensure these have also been upgraded with SAM 6.0.
We have a simple setup. no additonal pollers or web servers. The wizard
completed without error.
We are getting the alerts from any of the components.. but the
"Application Health Overview" for our views is saying "SAMPLE".
Alice Round
IS Operations
419-629-2311 ext. 3439
It also seems to be this way only on "custom views" for like Unix Admin's
login and Intel Admin login's. They don't have admin rights to the site.
I can login with my account and it looks okay and I have admin rights...
Just passing on this information..
I've logged out the Unix Admin account and back in to see if that changes
anything and it doesn't
From: Alice Round/IS/NBO
To: jive-1295214232-3bnm-2-4kri@solarwinds.hosted.jivesoftware.com,
Date: 09/24/2013 01:25 PM
Subject: Re: - I upgraded from
SAM v5.0 to v6.0
The Application Health Overview resource respects view limitations and account restrictions. Meaning if the user or view the resource is located on has no associated applications this resource defaults to the "Sample" that you are seeing. If you believe you are seeing this in error, such as a view where the All Applications tree resource clearly shows applications, and in that same view you also have the Application Health Overview resource showing the "Sample" graphic, then I would recommend you open a case with support.
Are you sure you have assigned some SAM Templates to some of your nodes? It will show as SAMPLE until some Template are actually assigned to the nodes. SAM Settings--Manage Templates--Select the desired Template (Edit first and test it to make sure it will work with the Creds you will use)--Click on Assignto Node button
I would suspect limitations as most probable cause of this issue. Could you check whether you are using some group containing applications in your limitations? Such limitations were not properly applied in SAM 5.0 which is one of fixed bugs in 6.0.
