cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post
Highlighted
Level 12

Re: NPM 11.5 RC2 Now Available

We take into account the time when the Capacity Forecast was calculated

e.g.

ndays = DATEDIFF(day, <datetime when the Capacity Forecast was calculated>, CurrentDateTime)

DaysToRichThreshold = Floor((Capacitythreshold - Aavg) / Bavg - ndays)

The only one day difference in both calculations means you can get different number of months,

e.g. 215 days = 7 months

216 days = 8 months

0 Kudos
Highlighted
Level 12

Re: NPM 11.5 RC2 Now Available

Any docs on theGeolocation SNMP Location field used the Worldwide Maps? What needs to be there to make it work?



Thanks,

Don

Highlighted

Re: NPM 11.5 RC2 Now Available

Ditto, I can't find anything on how to make this work.   I thought maybe the existing nodes I had manually added were interfering, so I removed them, no luck .  Tried turning the setting off and on in the Web Console settings, nothing.  Added new nodes, nothing. 

So, what is the magic to get this stuff working?   Does the SNMP location field need to be in a specific format, and if so, what is that format?  Are there variations allowed?

Personally I'd like to be able to use my SNMP location field for multiple things, such as grouping nodes in a node tree.    That means if I had to specify the SNMP location field as something like "1 main street, albuquerque, nm" instead of "NM, Albuquerque, 1 Main Street", that everything would be scattered about based on the street address number, rather than grouped by State or City...

Any documentation on this?   This has been out for some time with no real comment on how to use it.  I'm really hoping that you don't have to use lat/long, that would be a royal pain!!

0 Kudos
Highlighted
Level 17

Re: NPM 11.5 RC2 Now Available

We call out to a MapQuest web service to perform the lookup. As long as MapQuest understands the format, we are good. "Paris" may resolve to either "Paris, TX" or "Paris, France" so we just need to be specific enough to avoid ambiguity.

0 Kudos
Highlighted

Re: NPM 11.5 RC2 Now Available

So, how do we diagnose this?    I have it set to auto-place items on the map, but new items I've recently added aren't getting added.   I've double checked the address format against mapquest and it should work.   Should they get added to the map immediately?  After a period of time?  Trying to figure the ins and outs of how this feature works.

Also, as I said before, how about allowing us to "transform" the address format before sending it to Mapquest.   I like to have node-tree's display things by location, which works if you have a list something like:

NM, Albuquerque - 1 main street

NM, Albuquerque - 909 Montgomery Ave

NM, Las Cruces - 505 2nd street

TX, Dallas - 293 Fourth Ave

But if you have to have it in a format that Mapquest supports, you would end up with a list that looks more like:

1 main street, Albuquerque, NM

293 Fourth Ave, Dallas, TX

505 2nd Street, Las Cruces, NM

909 Montgomery Ave, Albuquerque, NM

I would think some sort of regular expression-like ability to transform the SNMP-location in the format I want it to a format that works for Mapquest would be a great feature!!

0 Kudos
Level 17

Re: NPM 11.5 RC2 Now Available

We do populate Lat/Long tables as lookups are performed. Support ticket is likely the best path forward if we're not seeing nodes populated: http://www.solarwinds.com/support/

0 Kudos
Highlighted

Re: NPM 11.5 RC2 Now Available

I guess that would bring up another question, if Lat/Long tables are populated as it find the nodes (I'm guessing), I'm hoping it keeps track of if there is a change in the SNMP-location field and does another lookup?

Of course ideally I would like to see in the future, if this is how its done, the ability to override and enter the lat/long coordinate directly in a way that so if you change the SNMP-location field it doesn't change these coordinates also.   Maybe a "lock-coordinates" checkbox along-side the manually editable lat/long field in the "Edit Nodes" page?

I did notice there was no comment on the suggestion for address transformations too, should that be put in as a feature request?   Should the suggestion wait for the actual release of the software with the feature in it to be submitted?

0 Kudos
Highlighted
Level 17

Re: NPM 11.5 RC2 Now Available

Yes, address transforms would be a FR. When we were to implement geolocation via CP, this may be a workaround.

0 Kudos
Highlighted
Level 7

Re: NPM 11.5 RC2 Now Available

This should really come with a 'do not upgrade' directive if you use any other major integration such as Web Performance Monitor.  It's alerts dissappear until its upgraded to a beta release.

0 Kudos
Highlighted
Level 12

Re: NPM 11.5 RC2 Now Available

One of my favorite less talked about features is volume thresholds.  Yay!  No more custom properties.  However, custom properties are still more useful because, unless I'm missing something, there isn't an easy way to bulk edit the Volume Thresholds.  For example, lets say I have a large group of servers that I want to set the C:\ Drive thresholds to 95% and the D:\ Drive Thresholds to 97%.  Right now I can't go into Manage Nodes and choose to edit only Volumes like I can with Interfaces, so that means I have to expand each server that I want to edit, select the C:\ drive, then click edit properties.  Then rinse and repeat for the D:\ drive.  Not a big deal if I just have a few, but lets say I have 20 or 30 or 100 or even 500 volumes, that's a lot of clicking and hunting and pecking just to select all of my volumes.  We really need a way to search, sort, and Group by so that we can bulk edit these like we can with interfaces.

(While you are at it, please expand the Manage Nodes screens capabilities to let us Sort, filter AND Group By all at the same time.  You can only Sort and search OR sort and Group by, you can't do both.  Plus, there really isn't any filtering at all.  The Manage Nodes screen should have the same sorting, filtering, grouping, and searching abilities that the Manage Custom Properties screen does.  The Manage Nodes screen also needs to allow us to Group by Node OR Interface properties when editing Interfaces instead of only letting us Group by Node properties (and Node OR Volumes if you add a Volume drop down box as I've suggested).  As long as I'm on a tangent, we need to be able to Group by Node properties in the Custom Property editor when editing Interfaces, Volumes, or Applications.  Its funny that when editing Interfaces in Manage Nodes I can ONLY group by Node properties and when editing Interfaces in Manage Custom Properties I can ONLY Group by Interface properties.  We need BOTH  ).

Seriously though, amazing features in this release, and minor gripes aside, I'm really blown away by all the new stuff you guys packed in.  If only one or two of the new features would have been added I would have been happy.  Keep up the good work, and make the Manage Nodes screen and Manage Custom Properties screen just as amazing as all of your new stuff!!