The link with 1.91(ms) is ever so slightly a different shade of green compared to the 1ms ones. It's most obvious at the midway point of the link arrow.
As for the flipping, it's done by the INOVERLIBGRAPH and OUTOVERLIBGRAPH lines. It will show you a different graph depending on which end of the link you are hovering on. In my example, one graph is id 3877 and the other is 3778 (but I did just notice that I made a typo on "a_end" where it should say otherrouter... Meh.).
In my deployment, I make it so that the graph displayed is relative to that closest port to the hover, plus I also flip the diplayed description.
Michael
On 10 Dec 2020, at 3:13 pm, Shekhar Basnet sbasnet@deerwalk.com wrote:
Hi, Michael, thanks. I squinted real hard but could not differentiate the color difference. :) By the way, in the config, which line is doing the flipping? I could not achieve it . Many thanks, Shekhar
On Thu, Dec 10, 2020 at 3:45 AM Michael via observium <observium@observium.org mailto:observium@observium.org> wrote: Hi Darren,
(Attached)
I haven't got any prod links that are pushing their sla thresholds right now, so here's a pre-prod one that is most likely just the control plane having a slow moment running the sla test (the link is otherwise idle and a local patch within the dc).
If you squint hard enough, you can see the colour difference as it transitions towards orange/red. We use gradual colours in the scales, not hard steps.
Cheers,
Michael
On December 10, 2020 8:28:11 AM GMT+11:00, "Storer, Darren" <darren.storer@gmail.com mailto:darren.storer@gmail.com> wrote:
Hi Michael,
Showing IP SLA sounds interesting - would it be possible to share an example of what it looks like via PHP Weathermap?
Many thanks
Darren
On Wed, 9 Dec 2020 at 20:49, Michael via observium <observium@observium.org mailto:observium@observium.org> wrote:
I wouldn't say we've got many complex weathermaps. At my former
employer,
we had developed a few of them into more complex ones (with a network focus, not a device/server focus).
I've extracted an example of what I'm doing with templates and
included it
below.
I change the text on the hovergraph to present the device and
interface
info, plus I flip the graph rrd to be the one relevant to that
interface
(so yes, the in/out flip based on which end of the link you are
looking
at). We also track IP SLA metrics on the weathermap with a narrow
link that
runs next to the data link. We apply different scales for local
(within a
datacentre), interstate and cross-country so that the relevant
changes in
latency can be correspondingly coloured.
It might give people some ideas. I'll see if I can dig up some
sanitised
versions out of my former workplace...
Cheers,
Michael
NODE ROUTER ICON 130 60 round LABELOUTLINECOLOR none USESCALE STATUS TARGET gauge:../../rrd/{node:this:label}/status.rrd:status:- INFOURL https://observium/device/device=%7Bnode:this:label%7D https://observium/device/device=%7Bnode:this:label%7D
LINK DEFAULT ARROWSTYLE compact BWLABEL bits BANDWIDTH 100G BWLABELPOS 70 30 COMMENTFONT 10 COMMENTSTYLE center COMMENTFONTCOLOR contrast INOVERLIBGRAPH
/graph.php?height=100&width=512&id={link:this:b_graph_id}&type=port_bits&legend=no&from=-21600
OUTOVERLIBGRAPH/graph.php?height=100&width=512&id={link:this:a_graph_id}&type=port_bits&legend=no&from=-21600
ININFOURL /graphs/type=port_bits/id={link:this:b_graph_id}/ OUTINFOURL /graphs/type=port_bits/id={link:this:a_graph_id}/ TARGET../../rrd/{link:this:a_end}/{link:this:a_rrd}:INOCTETS:OUTOCTETS INOVERLIBCAPTION {link:this:b_end} {link:this:b_int} OUTOVERLIBCAPTION {link:this:a_end} {link:this:a_int}
LINK SLA WIDTH 2 BANDWIDTH 100G BWLABELPOS 60 40 OVERLIBGRAPH
/graph.php?height=100&width=512&id={link:this:sla_id}&type=sla_echo&legend=no&from=-21600
INFOURL /graphs/type=sla_echo/id={link:this:sla_id}/ TARGETgauge:../../rrd/{link:this:a_end}/{link:this:a_rrd}:rtt:-
gauge:../../rrd/{link:this:b_end}/{link:this:b_rrd}:-:rtt INOVERLIBCAPTION {link:this:b_end} {link:this:b_int} OUTOVERLIBCAPTION {link:this:a_end} {link:this:a_int} USESCALE LOCAL absolute
################################ #### NODES #### ################################ NODE hy_myrouter TEMPLATE ROUTER LABEL myrouter POSITION hy_otherrouter 240 0
################################ #### DIRECT LINKS #### ################################ NK data_hy_otherrouter_myrouter TEMPLATE NATIVE SET a_graph_id 3877 SET a_end myrouter SET a_int Hu0/0/2/0 SET a_rrd port-122.rrd SET b_graph_id 3778 SET b_end myrouter SET b_int Hu0/0/2/0 SET b_rrd port-98.rrd NODES hy_otherrouter:60:0 hy_myrouter:-60:0
################################ #### SLA LINKS #### ################################ LINK sla_hy_otherrouter_hy_myrouter TEMPLATE SLA SET sla_id 82 SET a_end otherrouter SET a_int Hu0/0/2/0 SET a_rrd sla-cisco-rttmon-mib-2.rrd SET b_end myrouter SET b_int Hu0/0/2/0 SET b_rrd sla-cisco-rttmon-mib-1.rrd NODES hy_otherrouter:60:-5 hy_myrouter:-60:-5
On 10 Dec 2020, at 4:49 am, Adam Armstrong via observium < observium@observium.org mailto:observium@observium.org> wrote:
Hi Guys,
For those of you using PHP Weathermap, how many of you are using template/include features?
How complex after the weathermaps you’re making?
Thanks, Adam. _______________________________________________ observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
DISCLAIMER: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized use or disclosure is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. IRS CIRCULAR 230 DISCLOSURE: Any U.S. tax advice contained in this communication (including any attachments) is not intended or written to be used, and cannot be used, for the purpose of (i) avoiding penalties under the Internal Revenue Code or (ii) promoting, marketing or recommending to another party any transaction or matter addressed herein.(FR08-i203d)