[09:07:23] <jynus>	 there seems to be packet loss for alert1001- I checked it independently of the probe
[09:36:55] <vgutierrez>	 iface looks good though: https://librenms.wikimedia.org/device/device=162/tab=port/port=14829/
[09:37:29] <vgutierrez>	 well.. not that good actually :)
[09:37:44] <Emperor>	 going to say, a few errors lurking there :)
[09:38:28] <vgutierrez>	 just one coffee so far, ok? ;P
[09:39:00] <Emperor>	 I think I was confused by the interface errors graph anyhow /o\
[09:43:34] <jynus>	 it seems to be only for that host in the rack
[09:45:38] <vgutierrez>	 hmmm
[09:45:51] <vgutierrez>	 the spike of traffic on alert1001 oddly matches the start of certspotter there?
[09:46:04] <vgutierrez>	 Mar 10 15:42:19 alert1001 systemd[1]: Started Run certspotter periodically to monitor for issuance of certificates
[09:49:16] <vgutierrez>	 traffic dropped on alert1001 after stopping certspotter: https://grafana.wikimedia.org/d/000000377/host-overview?orgId=1&var-server=alert1001&var-datasource=thanos&var-cluster=alerting&viewPanel=8&from=now-1h&to=now
[09:50:30] <vgutierrez>	 and back to normal
[09:54:51] <jynus>	 does your team handle that, or should I create a task?
[09:55:26] <vgutierrez>	 I'm submitting a CR to disable it temporarily
[09:55:34] <vgutierrez>	 and opening a task for s.ukhe 
[09:55:40] <vgutierrez>	 he is taking care of that nowadays
[09:55:49] <jynus>	 ok, will let you handle it, then, thank you a lot!
[09:56:00] <vgutierrez>	 thanks for spotting the issue
[09:56:20] <jynus>	 the alert host is not a great host to have network errors :-(
[10:04:50] <vgutierrez>	 jynus: indeed
[10:27:52] <vgutierrez>	 jynus: issue mitigated and documented
[10:28:10] <vgutierrez>	 I'll wait for s.ukhe to dig into that
[10:28:36] <jynus>	 thank you, I replayed to the root email so other people are aware of that
[10:31:52] <vgutierrez>	 yep, it's also on the SAL and I assume that we won't get another alert from smokeping
[17:05:21] <jbond>	 hi all,  get asked a lot about rspec so i thought i would try to create a simple example directory.  https://github.com/wikimedia/puppet/tree/production/examples/spec/classes.  currently in here there are two files 
[17:06:05] <jbond>	 basic_class_spec.rb which is the ,most basic rspec file you can add to a class.  it esurse that the class compiles which in many cases is enough to catch 80% of the errors 
[17:06:26] <jbond>	 commented_class_spec.rb is a bunch of simple useages of rspce with comments
[17:07:01] <jbond>	 i honestly did the basic one as something for me to cp to new projects and thught id create the commented one as it may be usefull
[17:07:33] <jbond>	 if it is feel free to create a taksk or email me and i can add some addtional context and examples
[17:08:39] <jbond>	 also _joe_ akosiaris and anyone else familure with rspec post review would be usefull 
[17:09:17] <_joe_>	 jbond: I've seen more subtle declarations of hate.
[17:09:28] <_joe_>	 :D
[17:09:29] <jbond>	 lol :D
[17:09:31] <_joe_>	 but sure
[17:09:45] <_joe_>	 rspec is actually a nice BDD DSL
[17:09:55] <_joe_>	 puppet manages to make it clunky and weird
[17:10:33] <jbond>	 yes espceicaly with the historic tendency to use mocker
[17:11:41] <jbond>	 fyi i have tried to keep this very simple to not overload readers and i dont intend to try and document anything complex like facts, provideres or types for now
[17:12:04] <jbond>	 (as in testing facts, provideres and types)
[17:12:33] <_joe_>	 uhh yeah, no
[17:12:39] <_joe_>	 classes and defines should be enough
[17:12:44] <jbond>	 exactly
[17:12:57] <btullis>	 jbond: Thanks, that looks excellent. I will try writing some tests for my code. 👍
[17:13:00] <jbond>	 if you are mad enough to write your own provider yuo have allready dugg your own grave ;)
[17:14:44] <sukhe>	 very helpful indeed. personally, whether I intend to go down the road of misery with this remains to be seen, but at least we have some simple examples to start with :)