<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Exporter on qone.io</title><link>http://qone.io/tags/exporter/</link><description>Recent content in Exporter on qone.io</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 28 Aug 2016 00:00:00 +0000</lastBuildDate><atom:link href="http://qone.io/tags/exporter/index.xml" rel="self" type="application/rss+xml"/><item><title>simple prometheus exporter in python</title><link>http://qone.io/posts/docker-prometheus-exporter-python/</link><pubDate>Sun, 28 Aug 2016 00:00:00 +0000</pubDate><guid>http://qone.io/posts/docker-prometheus-exporter-python/</guid><description>&lt;p&gt;writing a simple prometheus exporter to collect metrics from a external system that needs monitoring. I will use the python official &lt;code&gt;prometheus_client&lt;/code&gt; package for python and &lt;code&gt;falcon&lt;/code&gt; to serve the exporter.&lt;/p&gt;
&lt;p&gt;notise the following example is written with the assumtion that you are collection metrics from some other systems when multiple services is written in the same framwork and have a generic set of metrics. That is why there is a service label included. Normaly you should get the service name, from your service discovery.&lt;/p&gt;</description></item></channel></rss>