| Commit message (Collapse) | Author | Age | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Added support to calculate uptime in days
|
| | |
|
|\ \
| |/
|/| |
InfluxDB, charting and a few fixes to Ansible
|
| | |
|
| | |
|
| | |
|
|/ |
|
|
|
|
| |
1 (green) and multiple (blue) hits
|
|\ |
|
| | |
|
| | |
|
|/ |
|
|
|
|
| |
s3 is currently disabled as it's bugged.
|
| |
|
|
|
|
|
|
|
|
| |
Fixes #151
While there are certainly more things that can be done - such as reading
the list of templates dynamically, it wouldn't be horrible to go into
production with the GUI the way it is right now.
|
| |
|
|
|
|
|
|
| |
Still leaves a lot to be desired, but is a good start.
References #151
|
|
|
|
| |
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.
|