Comments
-
It should be out now, I have a RC copy.
-
What is the update on this issue? Can SolarWinds monitor Openshift Containers in the most current version?
-
I would love if I could restart a group of Application Pools based off a wildcard.
-
Same for me as @itbrian. I did this too early.
-
I think this will be a feature in the beta version of NPM. I remember where you could determine the size or resources on a screen.
-
Definitely sounds fun, I'm excited!
-
You could do it that way, I choose to alert when the SQL service that is currently running on that physical node would stop. This would mean that the service(instance) would have moved to a passive node. It would just be an alert saying that SQL service (instance name) has stopped on (physical node). This would signal a…
-
Fred where at in the settings did you go to make this change? I'm running to the same issue and would like to resolve it as well.
-
You will have to create a custom monitor that is just monitoring the SQL service on the physical node. When the instance moves to another physical node, an alert will fire because the SQL service will not be on that physical node anymore. I would send you some screenshots of what I did, but I just started my new position…
-
To resolve it, I rolled back to the backup of the database I ran before the upgrade, and I went back to 11.0.1. The business layer had some problems which was causing the services to become unstable. Support had to fix some tables in the database , fix the business layer and this took roughly about 10 hours. I did this on…
-
I'm having the same issue. Ready to Join Captain!!
-
So I need to install the Profiler and run it with SRM? Can these two run at the same time?
-
I have done the upgrade and I have been happy with the results. I don't run into any storage issues any more, so for me the upgrade resolved the issue.
-
I don't have a script to clear the events, so I just ended up monitoring the SQL instance on the physical node and fired an alert when it moved to one of the physical nodes. It worked in the environment I was in because the instance was always sitting on the node with the most resources on it.
-
After some baking the numbers are coming down. I think the new version is working.
-
It was one one of my custom properties. It was a true/false custom property based on the type of Node.
-
Well the closest thing I found to a work around is pulling the data from the AlertDefinitionsView from each database and do a quick comparison in excel. Hope this helps someone.
-
Thanks, I totally forgot about this. This should work.
-
I'm a little lost can you explain a little further?
-
I don't think you can run monthly reports out of alert central. Also the weekly reports aren't as detailed as I would like them to be.
-
Did this view or metric get transfered into SRM?
-
Yes I agree with rob.hock. You should create a custom property to catagorize the devices. Then, create a group using the custom properties. Then set the View Limitation to either the custom property or the group. That way your new node will be added to that individual view. Lester Grant Loop 1 Systems www.loop1systems.com
-
Not sure but I will let you know next week. I'm upgrading to the latest version this Saturday night.
-
No worries, I didn't look at the query correctly, figured it out.
-
zackm I have a question. Is there a way to make a similar resource but it shows all historical alerts that email? I like to use this for Audit purposes.
-
What is the object the custom property is based on? Could you display a screenshot?
-
was you able to find an answer that gave you the results you wanted?
-
Hey Zack, I ended using this to find what I needed. I changed the SWQL query above to the following. SELECT Nodes.Caption AS [Name], AlertDefinitions.AlertName AS [Alert Name], AlertStatus.TriggerTimeStamp AS [Alert Time], AlertStatus.AcknowledgedTime AS [Acknowledged Time], AlertStatus.AcknowledgedBy AS [Acknowledged By],…
-
d09h I think I would still need this in a group because I would need to use this group or set of devices as part of an alert to NOT alert off of. Basically have an alert setup but not fire on these devices because they are troublesome. Also this group or set of devices can't be visible to everyone for security reasons.…
-
There is a new version in beta right now.