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

Bug: Orion 8.5.1 SP3

The bug exists with the new All Nodes - Tree (AJAX) resource. I am grouping nodes on 2 levels with the second level being a custom property. If that custom property is blank for a node in the All Node - Tree resource, the node appears ungrouped at the bottom of the list. In the new All Nodes - Tree (AJAX) resource an Unknown group is created but when expanded there are no nodes that appear in that group.

Other than that little bug, the new All Nodes - Tree (AJAX) resource is great! It has reduced the load time of 30-60 seconds to 3 seconds for the Network Summary page.

Find more posts tagged with

Accepted answers

All comments

tdanner

Good catch! The new node tree correctly handles blank values (that is, the empty string), but loses track of NULL values. The standard properties (Contact, Vendor, etc.) default to blank, but custom properties you add default to NULL - leading to the problem you are seeing.

I have attached a fixed version of \Inetpub\Solarwinds\App_Code\NodeTree.cs. Replace that file and let me know how it works for you. This version will treat null values the same as blank ones.

Is the specific treatment of blank custom properties (display ungrouped at the bottom of the list) important to you?

NodeTree.zip

SamuelB

I have attached a fixed version of \Inetpub\Solarwinds\App_Code\NodeTree.cs. Replace that file and let me know how it works for you. This version will tree null values the same as blank ones.

That works! Replacing the file fixes the issue.

Is the specific treatment of blank custom properties (display ungrouped at the bottom of the list) important to you?

No, it is fine if the nodes that have NULL values are grouped into an Unknown group, I just don't want them to not appear at all in the list. As long as they appear somewhere in that list, grouped or un-grouped, it is a reminder that someone forgot to fill in the custom property and that is all I need.

FormerMember

No, it is fine if the nodes that have NULL values are grouped into an Unknown group, I just don't want them to not appear at all in the list.

Me too. I want the Unknown group back that disappeared in 8.5.1 in default All Nodes view. I don't want to see nodes without custom properties defined showing up in the root list. Only want to see groups listed.

vhcato

I have attached a fixed version of \Inetpub\Solarwinds\App_Code\NodeTree.cs. Replace that file and let me know how it works for you. This version will treat null values the same as blank ones.

Tim, is this something that will find its way into SP3, or should people grab it here?

tdanner

Right now there is no plan to rebuild SP3, so this is it.

JasonKV

I have applied the fix that you sent. Very nice work. One thing I have noticed is that you have to click on "Get Next 100 Nodes" at the bottom of the list if you have more then 100 nodes in a certain grouping. I would rather not have this feature and just have all the nodes in a certain group show up all at once. I was able to mess with the code and get the number up to 350. 500, 999, and 100000 all error out and do not work.

What is the largest number possible to put in this field? Can this be taken out of the code entirely? Thank you in advance.

aliendan

I have applied the fix that you sent. Very nice work. One thing I have noticed is that you have to click on "Get Next 100 Nodes" at the bottom of the list if you have more then 100 nodes in a certain grouping. I would rather not have this feature and just have all the nodes in a certain group show up all at once. I was able to mess with the code and get the number up to 350. 500, 999, and 100000 all error out and do not work.
What is the largest number possible to put in this field? Can this be taken out of the code entirely? Thank you in advance.

I think that 100 at a time is good. In our environment the drop downs would not load in a timely manor if all the nodes in a group were allowed to display.

tdanner

The ajax node tree uses the asp.net javascript web service client to transfer chunks of the tree. This web service client puts a hard limit on the size (in bytes) of the payload that can be returned. You found that this limit seems to correspond to about 350 nodes. It would vary somewhat depending on things like the length of the node names and whether you are using the Toolset Integration feature.

So we can't really make this limitation go away entirely. What might be possible would be to have the browser-side code automatically fetch the next 100 nodes (and the next 100 nodes, etc., until done). It would be as if you had clicked the "Get Next 100 Nodes" links the very moment they appeared. How would that work for you?

JasonKV

I think this would be a great alternative. If we have 600 nodes its a pain to have to click 6 times to get to the bottom of the list. I would like further information on how to change the code to what you described. Thank you.

aLTeReGo

tdanner, I'm running 8.5.1 SP3 and applied the hotfix you posted here for the Ajax'd version of the All Nodes resource but it doesn't fix my problem. The problem I'm seeing is that all of my nodes are showing up under custom groupings, even ones that don't belong. For example, I have an all servers resource that groups servers by machine type. I have groups like "Windows 2000 Server", "Windows 2003 Server", etc. The trouble is that my Windows 2000 Servers are showing up in the "Windows 2003 Server" group and vis-versa. This is not the case with the classic all nodes resource. Any suggestions?

Here is a screenshot. All the groups show "yellow" because I have one Windows 2003 server down right now, but this server shows up under every grouping and shouldn't

allnodes.jpg

tdanner

The trouble is that my Windows 2000 Servers are showing up in the "Windows 2003 Server" group and vis-versa. This is not the case with the classic all nodes resource. Any suggestions?

That's weird. Are you using a SQL Filter with this resource? What about account/view limitations? Those should work, but with their infinite variations there might be something interacting badly.

amm_orion

This is somewhat related, but not a bug per-se.. Is there a way to change the font that is displayed in the All Nodes - Tree screen? Since upgrading to 8.5.1 SP3 the font is a lot larger than it was in previous versions..

Thanks!

tdanner

I attached a version of AjaxNodeTree.js that performs this auto-continue function. Just replace this file in \Inetpub\Solarwinds\Orion\NetPerfMon\Resources\NodeSummary and it should kick in.

I can't promise this feature will be in the next release, but if you are familiar with javascript it should be easy to see how it works.

AjaxNodeTree.zip

jkennedy

I have been running it an issue with the new Ajax node tree. I have my nodes groups by 3 levels of custom properties and I'm getting an error when trying to expand one of them.

JasonKV

I have been running it an issue with the new Ajax node tree. I have my nodes groups by 3 levels of custom properties and I'm getting an error when trying to expand one of them.

I dont know if this will help but, this was the same error that I was getting when I had the counter on number of nodes to load at once above 300ish. Did you mess with the code that was given at all? I have not had time yet to implement the revised code that was posted before your post, so I can not say for sure if it the same problem.

jkennedy

I haven't tweaked the code but I ran a test with the SQL against the database and I don't get an error. I have 77 distinct groups on that level that won't expand.

jkennedy

I found the cause of the error we were encountering with the all nodes ajax resource. If you try to group your nodes by a custom property where one of the values contains an apostrophe, it will give you an error.

tdanner

The attached zip file contains an update for the ajax node tree that addresses two issues reported in this thread:

Custom SQL filters that use "OR" cause nodes to appear in multiple groups.
Custom property values that contain an apostrophe (or a couple of other special characters) break the tree.

There are two files in the zip:

NetPerfMonWeb.dll - goes in \Inetpub\Solarwinds\bin
NodeTree.cs - goes in \Inetpub\Solarwinds\App_Code

As a bonus, it is now possible to switch how nodes with null values for custom properties are handled with a simple code edit. Near the top of NodeTree.cs, you can change "GroupNodesWithNullPropertiesAsUnknown" between true (use an "Unknown" group for null values) and false (promote nodes with null values to the next highest level.

AjaxNodeTreeUpdate.zip

SamuelB

I ran into the "OR" problem the other day and this fix worked flawlessly. With the changes that have been made, this is my new favorite resource. I hope these changes are in the next version of Orion.

vhcato

Finally tried it out. Very nice work, Tim. This is a real solution to something that's been a problem since we first installed Orion in 2005. No longer does one have to suffer through the lag time associated with loading a large device list. Hopefully we can look forward to other performance enhancing solutions like this in upcoming releases...

The only thing I've noticed is that it doesn't seem to honor view limitations with respect to the color of the status icons. The status of objects that match the grouping designation, but do not match the view filter will still influence the color of the status icons. Applying a filter to the resource individually takes care of it, but it doesn't scale well when dealing with a large nuber of views.