Comments
-
I ran that in SQL Studio and it was successful but returned no results. I know I have one on purpose so that I can find how to query or even a report. That's my main goal. Adding the who is not for us but will be for others.
-
Ah ha. Scheduled seems to have a different ID for me. My action was to choose mute now, not scheduled. That has ID of 93 but see the same ID of 100 in your list and the verbiage is even different. What I'm trying to find is currently in mute state. I'll do some digging, trying to find where that is held. Seems I hit wrong…
-
First time for me, not that I've deleted a lot of them but some for sure. Solarwinds Case 00186111.
-
I'm new to this product and I'm trying like mad to do this as well. What I can say, if I put in my bash profile to find root logged in from orion server, then it would run: shopt -u -o history This works and ssh debug doesn't show any errors but it still continues. I'm with you dennyj and I will continue to work on this.…
-
I thought about adding that statement in the last post. Not too versed in SW, do I just open a case, post something out, etc. I'm with ya. Thanks for talking it through. Take care.
-
I have been putting the CentOS agent for my OEL 6 and they are working fine.
-
Yes, started with that. There is also a report for activity that was created, extended that time range as well to try and find. That's where I got into finding the DB table for Auditing, figured go right to the source but no luck there. Other than now looking for the table of application monitors, I guess that would verify…
-
Well, tried poller switch but read it in more details. This is lingering monitors that after being deleted are still attached to the node. The node itself is fine. That is the production ones that still remain, but this is the monitors view of what it should be. The grey-ed out ones are the ones that were deleted but…
-
Patience for sure, guess I can try a services restart. Just 4 for me and it's at 11 days. Thanks...
-
I see that field in the Nodes table. I don't use the UnManaged, glad to have the mute option so I can still have collected data. You should be able to do a query there and find what you're looking for.
-
I'm surprised this has no comments, crazy not to have a value to set in the alert and have the 'go find it yourself'.
-
Good session with support. Yes, remove it from the DB. From the URL, get the Node ID (N:xxx) and from the inactive Application, it's ID (AA:xxx). Was easiest from the assigned monitors to navigate and go back to collect them. From SMSS or the DB utility, toggled between query to visualize/validate and delete. SELECT * FROM…