using vmagent to collect victoriametrics stats

-

 vmagent is part of victoriametrics, and is a lightweight prometheus scraper.

create a basic prometheus.yml file that defines a host to scrape, in this example it's using SSL and basic auth



global:
  scrape_interval:     15s
  evaluation_interval: 15s

scrape_configs:
  - job_name: vmetrics
    static_configs:
      - targets:
         - host.to.scrape:443
    scheme: https
    basic_auth:
          username: user1
          password: password1

then run vmagent to use this and send to a victoriametrics node to store the metrics it scrapes



./vmagent-prod -httpListenAddr 127.0.0.1:8240 -remoteWrite.basicAuth.username user2
  -remoteWrite.basicAuth.password 'password2' 
  -remoteWrite.url=https://host.to.send.to:443/api/v1/write 
  -promscrape.config=prometheus.dsch.yml

if using the cluster version, the url in the command line might be



-remoteWrite.url=https://host.to.send.to:443/insert/0/prometheus/api/v1/write

Comments

Post a Comment

Popular posts from this blog

using t1n1wall, opnsense or pfsense on Google Compute Engine GCE

-
I have been doing some work in GCP recently, both appengine , and GCE.  We wanted to make sure all our instances were on private ips and only the LBs had internet ips. This gave us the problem of how to allow our instances reach the internet for updates or for api calls outside. In AWS you had a NAT gateway, but in GCP this doesn't exist. So I set about looking at the easiest way to do NAT from a private IP subnet to a Public address.  I am very familiar with m0n0wall and t1n1wall and a tiny bit with pfsense and less with opnsense. The tl;dr is that all these distributions ship an image which within the distribution there is a disk image.  Taking this internal image, renaming it and re-compressing it is all you need to do to get it working in GCE. you can configure it via the serial port using these instructions  There are guides out there around doing things with Linux and stuff, but you can skip that step. I took the latest version ...
Read more

nginx decode base64 url for use with imgproxy

-
 i've been testing imgproxy, to handle our image serving needs, and it looks good. our existing servers are php based, and we sign and encode our urls for images.  To test out imgproxy , I wanted to simply drop it in as a replacement for our servers by sending a % of traffic.  There are many ways to do this, varnish was one, with custom code, but nginx is our go-to web server, so I had to find a way to have nginx sit in front of imgproxy and rewrite the decoded url. I settled on using njs, the cut down version of javascript that plugs into nginx as a loadable module.  Then use proxy_pass to pass the uri to javascript that will return the imgproxy compatable url, and proxy to it. a sample url would be http://foo.bar/images/c2lnbmF0dXJlZm9vaHR0cDovL3MzLWV1LXdlc3QtMS5hbWF6b25hd3MuY29tL215YnVja2V0b2ZwaG90b3MvcGhvdG9fb2ZfYV9jYXQ1fHx8MTIwMHgxMjAwfHx8fHx8fHw==.jpeg it has a sig, a bucket url, and parameters like image size. Getting nginx setup nginx.conf load_module modu...
Read more

Resol VBUS success

-
at last, the kind folks in Resol sent me the protocol specification for vbus with openwrt and rrdcollect and rrdcgi, I can now graph the pumps and temperature information of my solar water system. There is a bash script that collects from the serial port, decodes it , and then outputs the values to a file that rrdcollect parses. All good, some holes in the graphs, probably a bad awk in my script, to be investigated. Once it's working reliably with no holes, I will try to post graphs here, somehow EDIT: Now there is a google group http://groups.google.com/group/resol-vbus EDIT: I wrote a utility to parse the data, seems to have gotten lost in the group, it's here  https://code.google.com/p/vbusdecode/
Read more