04:53:47 <neuroserve> barfield isn't node_exporter not enough for your needs?
05:20:46 <barfield> Thats a good question
05:20:52 <barfield> I
05:21:05 <barfield> I am assuming that is the underlying node module that the cmon-agent is using?
07:27:15 <neuroserve> barfield : nope - this one: https://github.com/prometheus/node_exporter
07:43:41 <gonzosysadm[m]> i keep getting this message "WARNING: terminal is not fully functional" (with less, man, etc) on the gz inside of tmux. TERM is set to tmux-256color, which something somewhere doesn't seem to recognize. if i set it to screen-256color it works as espected. what would be the proper way to fix this? (make it recognize tmux-256color, whatever "it" is here)
14:01:31 <barfield> neuroserve: I'm actually looking into this today. Thank you for the suggestion. 
15:05:32 <gonzosysadm[m]> what is admin_network in /usbkey/config? it's empty
15:06:50 <gonzosysadm[m]> and how to correctly set the prefixlen in admin_ip6 ? add it to the ipv6, or is there an admin_netmask6 or something
15:44:50 <bahamat> gonzosysadm[m]: admin_network is the network number of your admin interface. The admin interface is the primary IP of the global zone.
15:46:22 <gonzosysadm[m]> network number? as in vlan?
15:48:27 <bahamat> No, the prefix
15:48:46 <bahamat> like if your IP is 10.1.1.10/24, then the network number is 10.1.1.0
15:50:03 <bahamat> But you don't need it really. It works just fine if you don't have it in your config.
15:50:43 <bahamat> to set the prefix length for ipv6 do admin_ip6=2001:db8::f00/64
15:53:42 <gonzosysadm[m]> ah
15:53:55 <gonzosysadm[m]> yes, i am creating an ansible template for it, and i noticed it's empty. i was wondering if it ought to be kept around
15:55:16 <bahamat> In that case it would be the same as ansible_facts.ansible_default_ipv4.network
15:55:51 <bahamat> So if you look that up in ansible facts on a running node you'll see what it's supposed to be.