| Commit message (Collapse) | Author | Age | Lines |
|---|
| | |
|
| |\
| |
| | |
Set Client ports description to "None configured" if no configured client ports
|
| | |
| |
| | |
This fixes a bug where "Client ports" value could be "0 / NaN" if no client ports were configured.
|
| | | |
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Mainly moving graphs around
|
| |
|
|
|
|
|
| |
Click a field in a switch summary and the health map will use it as a
legend, assuming it isn't already showing information.
And remember what panel was used last when browsing switches.
|
| | |
|
| |
|
|
|
|
|
|
| |
....
Oplog: Don't send empty oplog entries.
When viewing a switch, don't include oplog entries that have a blank
system association.
|
| |
|
|
| |
Displays a sorted list of what needs attention.
|
| | |
|
| | |
|
| |
|
|
|
| |
The latter allows you to set 'disable' as community and the front end (!)
will not be as critical about the results.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes #93
Fixes #92
Fixes #91
The hash logic with FreezeThaw wasn't consistent, which broke a lot of
optimizations. This might be slower (?) but it's consistent which means
we'll make up for it by better cache utilization.
To utilize this I also added delayed JSON parsing (#91) with a big
description of why we want it. This also means that #90 and #89 is a lot
less important. One issue right now is that "time" isn't part of the ETag.
This is both a blessing and a curse. If we are going through time we will
actually use in-app cache (not browser cache - the URL changes). This
makes for nice CPU savings, but ultimately means we can't tell that the
data for two distinct times is identical because we only see one. Oh
well...
On the simpler side, I fixed/improved the clearBox logic to fix the
artifacts. Might need to tune this. I also added some optimizations to
avoid redrawing identical text. This is what pointed out to me that the
hash was broken too: The resizeEvent was triggering all the time, forcing
redraws all the time. This happened because nmsData.switches "updated"
frequently which should only happen if someone adds/moves/removes a switch
or linknet - regardless of time travel. This was caused by the inconsistent
hash causing a false cache miss.
Anyway, if you are still reading this, you almost got a patch with "kjell
magne bondevik uten mellomnavn" as a literal text string... TOO BAD.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
As a result of testing with TG16-data, I was able to find and fix a few
outstanding issues and tune the health map to make more sense.
Also introduced both temperature and dhcp into the health map and info box.
Removed the switchInfo text on the health map unless the score is above a
threshold.
Still more tuning needed. After introducing dhcpInfo it's become even more
important to address #88
|
| |
|
|
| |
Makes it more snug and look the same all over
|
| |
|
|
|
|
|
| |
- Time in oplog is now localtime and properly padded (00:10, not 0:10)
- Health map instead of combo/aggregated
- Tweak the menu slightly
- Rotate and resize the random switch in guess_placement
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
testTree() will make it easier to avoid try-catch'ing because instead of
if (nmsData == undefined || nmsData.snmp == undefined || nmsData.snmp.snmp
== undefined || nmsData.snmp.snmp[sw] == undefined ||
nmsData.snmp.snmp[sw].misc ...)
you can do
if (!testRoot(nmsData,['snmp','snmp',sw,'misc')) { ...
Which is at least slightly less annoying.
|
| |
|
|
| |
Knocking stuff off the top of the cpu hogs from a tiny bit of profiling.
|
| |
|
|
|
|
|
| |
Specially bad was the foo == bar == undef thing which broke completely.
Also, this makes sure that we don't cap out at 200 if the ping reply is
1000ms...
|
| |
|
|
| |
Management IP up top seems sensible.
|
| |
|
|
| |
That was supposed to be a debug thing...
|
| |
|
|
| |
Also does ipv6 now.
|
| |
|
|
|
|
|
|
|
|
| |
Fixes #80
I should go to bed.
Also: Fixes a tiny little issue where we didn't take into account the
nature if the OPing timeout? Or has it changed? Either way, no longer do we
store thousands of ping replies - per second.
|
| |
|
|
|
|
|
|
| |
Fixes #2
Also, since I didn't bother splitting the commits, this tweaks the
information provided from the snmp handler and management handler. Notably
treating IPv4 and IPv6 management addresses as equals.
|
| |
|
|
| |
Ooops...
|
| |
|
|
|
|
|
|
|
|
| |
handlerInfo is getting slightly extensive, but it might be worth it.
This also introduces a "map" handler that .... doesn't handle the map.
If/when namespaces are introduced properly in nms-map-handlers.js, we
should also rename it to nms-data-logic.js or something else that signifies
that this is what makes data useful one way or an other.
|
| |
|
|
|
|
| |
Also gets rid of color_from_latency() (?) as it was basically worthless by
now, and adds switch info to the combo-map so you can quickly identify why
a switch is colored a certain way without clicking on it.
|
| | |
|
| |
|
|
|
|
|
|
| |
Fixes #15
Still lots of things that _should_ be done, but this is the groundwork
needed for a combined map. Theoretically, all map handlers should just
expose getInfo somehow now.
|
| |
|
|
|
|
| |
Should get rid of the get_gradient_from_latency entirely.
PS: jocke, you read too many commit logs.
|
| |
|
|
|
|
|
|
|
|
| |
Only combines SNMP and ping for now, but the "API" it establishes should do
what we need.
References #15
Before I consider this done we need to add the infomration in the info-box,
and also remove the manual information present there.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
- Shadow for map title text (color matches background, so only visible when
background interferes with readability)
- SNMP map is private too
- Remove 'map' from a bunch of titles
- Fix z-index and position for map title (z-index is lower than the input
canvas, but higher than everything else).
|
|
|
Fetched from tgmanage.
|
