| Commit message (Collapse) | Author | Age | Lines |
|
|
|
| |
Fixes #126
|
| |
|
|
|
|
|
| |
There really should be a way to make it obey cache-control instead of
this rubbish.
|
| |
|
|
|
|
|
|
|
| |
Tweaks background colors on graphs.
Adds a funky "ticker" to the navbar that may or may not break small
screens. Graphs average latency and total bandwidth for all equipment.
|
|
|
|
| |
Needs to match with the drill-down graphs so the colors match up.
|
|
|
|
|
|
|
| |
Perhaps not the most intuitive name, but it'll have to do for now or until
someone complains.
Fixes #124
|
|
|
|
|
|
|
|
| |
It doesn't do any good in its current implementation.
If it were to make sense, we'd need to drastically enrich it.
Closes #128
|
|
|
|
|
|
| |
It was identical to settings/edit.
Fixes #123
|
| |
|
|
|
|
|
|
|
| |
♥ SVG
I don't have to figure out the exact pixel count on the width to make it
fit well :D
|
|
|
|
|
|
|
|
| |
I'd do the same thing on all graphs as on the summary, but I have no idea
how to trigger an update on the ports pane right now.
Lets you cycle between pre-set time windows of 60 minutes, 6 hours, 24
hours and 7 days.
|
|
|
|
|
|
|
|
|
| |
- Upgrade to 0.9.15 (that was a lot more work than the commit reveals)
- Numerous color tweaks to make it prettier
- Use SVG instead of PNG
- Use correct perSecond() provided in 0.9.14 instead of derivative()
Still more to come I suppose
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Nightmode
- Aliases for sensible legends
- Two layers of collapse on ports
- Toggle/expand all feature to show graphs for all ports
- Show human readable variant of very large numbers in port drill-down
in addition to raw value (e.g.: 4800000000 (4.8G))
Still to do:
- Ability to click on a stat to get graphs for it
- Upgrade to graphite 0.9.15. Most of the following depends on that:
- Use perSecond() instead of derivative() for traffic
- Use SVG instead of PNG
- Get rid of extra )'s in legends
- Evaluate using SVG + CSS to get nightmode. Not sure if that'll work at
all, as it depends on whether the SVG context is isolated or not from the
DOM at large (e.g.: is #nightmode visible)
- Consider generalizing graphs
|
|
|
|
|
|
|
|
|
|
|
| |
The "traffic" thing should be integrated in the snmp/ports overview.
All that's missing is a two-step drill-down per port. E.g.: Click a port
and you get graphs, click the next drill down and get full snmp-data.
When that's done, all we need is an "expand all" button.
And a pony.
|
|
|
|
|
|
|
|
|
|
|
| |
- Adds latency graphs everywhere, even where they shouldn't be. For PoC.
- Fixes a frontend leakage of handlers
- Adds a nasty way of getting latency-data into graphite (needs to be
improved)
- Adds working graphite integration in varnish
- Adds config for graphite
Lots of things broken here, but it's a half-decent start.
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
Tooltips vil være litt browseravhengig.
Fikser også noen nightmode issues her og der.
|
| |
|
|
|
|
|
|
|
|
| |
....
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.
|
|
|
|
| |
No longer updates SNMP view when you're looking at it.
|
| |
|
| |
|
|
|
|
|
| |
The latter allows you to set 'disable' as community and the front end (!)
will not be as critical about the results.
|
| |
|
|
|
|
| |
Firefox....
|
| |
|
|
|
|
|
|
|
|
|
| |
The HTML/detail should probably be tweaked, but I think we need a way to
show that Gondul is still alive now that we are hiding the time stamp by
default.
Feel free to throw the HTML/CSS away in favor of some other subtle but
noticeable "animation".
|
|\ |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|
|
|
|
|
| |
- Don't overload the logbook overlay
- Neater date formatting (ugh, I hate that we need to do this)
- Caption for the logbook in the info box
|
|
|
|
| |
Makes it more snug and look the same all over
|
|
|
|
|
|
|
| |
I can never get it all in a single commit.
But I compensate by some times putting multiple unrelated things in the
same commit.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes #69 #11 #5
Introduces nmsTime which unifies the time travel code a bit. It still needs
some work, but this is much better.
All conversion is now done by native JavaScript methods, freeing us from
the hell that is parsing it ourself.
One thing should be added: The backend should discard any now=values that
are not 5-minute intervals. We don't want to kill the cache and the
database by extension.
Still need to re-implement the "replay event" shorthand, but that ties in
to #54
|
|
|
|
|
|
|
| |
- 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
|
| |
|
|
|
|
|
|
| |
Fixes #84
It's really stupid simple, but it will work.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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...
|
|
|
|
|
|
| |
Fixes broken class list when the description was stuff like "worst:
management info" (where the "info" would end up as a class and change the
look).
|
|
|
|
| |
Management IP up top seems sensible.
|