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

Deleted application monitor still tied to the node

I have an application monitor assigned to some nodes, but for non-production, not really necessary anymore. Delete them from the nodes and in Manage Assigned Application Monitors, they are gone. But alerts are generated. When I look at the nodes for where they were removed, the application status is Unknown and the icon is grey and unknown status. The Application Details has a message: "You currently have not configured monitors. To display data, add monitors to an application template and assign the template to a node."

I've done some looking around, trying to reach it a different way through the interface but I'm not finding a means to complete the removal of the monitor.

Any thoughts?

Thanks.

Find more posts tagged with

Accepted answers

All comments

hpstech

I've experienced this many times. Especially when deleting more than 50+ monitors at a time.

A service reboot may help, and some patience. Sometimes I've seen these self heal and go away with a day or two.

mmcc0912

Patience for sure, guess I can try a services restart. Just 4 for me and it's at 11 days.

Thanks...

rschroeder

This sounds much like the dreaded "Object reference not set to an instance of an object."

The non-intuitive error in this case is cased by a monitor applied to a node that has been removed. The recommended solution is to remove custom monitors from nodes before deleting the nodes.

IMHO, the right solution would be for SW products to be smart enough to know that a monitor or a custom UnDP applied to a deleted node should be disassociated from the node upon node deletion.

But, maybe it's like me pulling the boat out of the garage while it's still attached to the battery charger cable hanging down from the ceiling. The boat or the battery charger (or I) should be smart enough to disconnect before towing the boat out.

mmcc0912

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 didn't go away from the nodes. So the alert thinks they are down.

rschroeder

I recommending collecting the diagnostics off the poller(s) and opening a support case with Solarwinds to clear this up most efficiently.

mmcc0912

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.

mmcc0912

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 [dbo].[APM_Application]

--DELETE FROM [dbo].[APM_Application]

where nodeid = '248'

--and id in ('200')

Then:

--SELECT * FROM [dbo].[APM_Application]

DELETE FROM [dbo].[APM_Application]

where nodeid = '248'

and id in ('200')

gjp1971

If you are like me, I have 16000 entries under some of the properties. I had to remove close to 675 after some servers had some services removed for resource purposes. I also had several after updates that were not linked. I wanted to have a way to see all the devices that became unknown as well as add them to a ticlet. I found the quickest way to remove them all without having to check each box through pages and pages of entries is to do it directly from the SQL DB. I think it goes without saying that you should always back up your SQL DB in the event you make a mistake. Here are the steps I took to remove Application monitors from several that were showing unknown, yet when I looked in the assigned monitors did not see them.

First, I rand the following in SQL Query on the SQL Server. I know someone with better SQL knowledge could probably help with the query to have it remove them all from a query. But at least this way, I have a record of what came out.

(Note 0 = Unknown)

SELECT [dbo].APM_Application.ID, [dbo].APM_Application.Name, [dbo].APM_Application.NodeId, [dbo].NodesData.Caption, [dbo].APM_Application.TemplateID, [dbo].APM_CurrentApplicationStatus.Availability

FROM APM_[dbo].Application

INNER JOIN [dbo].APM_CurrentApplicationStatus on [dbo].APM_CurrentApplicationStatus.ApplicationID = [dbo].APM_Application.ID

INNER JOIN [dbo].NodesData ON [dbo].APM_Application.NodeID = [dbo].NodesData.NodeID

WHERE [dbo].APM_CurrentApplicationStatus.Availability='0'

If you are already in the DB , you can omit the database name [dbo]

This gave me back results in the format

1973 | WSVC SNMP | 233 | W12V-SVR | 294 | 0

When all of the results came back, I saved them in Excel format. This gives the ability to update all at once or at my own pace.

In the last column, I updated with : (Note by each cell variable is set up as ' " & A1 & " ' and the last one has ' " & C1 & " ' ; "

="DELETE FROM APM_Application WHERE ID = '"&A1&"' AND NodeID = "'&C1&"';"

this way, the result is

DELETE FROM APM_Application WHERE ID = '1973' AND NodeID = '233';

Copy the line to all the cells beneath. This will auto-fill all the line below.

Paste the line or lines in to a SQL Query and it will remove all these items from the application monitor.

tech2734

Every time I turn around I run into one of these weird issues with SolarWinds.

jrouviere

I wanted to reply as I had a shade of this similar issue which this post was able to help jog my memory. There is a way you can potentially find these and fix them in the UI if you're squeamish about going into the database or have a few (we had four instead of hundreds):

I found these applications by checking the Unknown Applications resource and found that none of the application monitors actually had components associated (not sure how it got into this state really, so that's a different thing).

What I was able to do was find the None application template to remove them, but still some would show in the count, but not in the UI to be deleted.

I was able to add a component to the application monitor by using the URL from the Unknown Applications resource (any will do, but I used File Age Monitor) and then see it in the None category under Assigned Application Monitors and delete it.

Again, if you've got many of them you will probably want to follow the SQL pieces above, but using it this way allowed us to avoid taking the fix through a lengthier review process so I wanted to share.