内容简介:Getting insights into how your Python web services are doing can be easily done with a few lines of extra code.To demonstrateThat’s really it to get started! By adding an import and a line to initialize
Getting insights into how your Python web services are doing can be easily done with a few lines of extra code.
To demonstrate prometheus_flask_exporter with a minimal example:
from flask import Flask from prometheus_flask_exporter import PrometheusMetrics app = Flask(__name__) metrics = PrometheusMetrics(app) @app.route('/') def main(): return 'OK'
That’s really it to get started! By adding an import and a line to initialize PrometheusMetrics
you’ll get request duration metrics and request counters exposed on the /metrics
endpoint of the Flask application it’s registered on, along with all the default metrics you get from the underlying Prometheus client library .
You can find an easy-to-run example in the GitHub repo that spins up a Prometheus and aGrafanainstance along with a demo app to generate some metrics, which will look something like this:
You’ll also find the list of metrics in the README of the example that are displayed on the dashboard, along with the Prometheus queries which populate the panels.
Configuration
The library has lots of configuration options, have a look at the project README for examples of them with a brief explanation.
The basic configuration is as shown at the top. Simply create a PrometheusMetrics
instance, let’s call it metrics
, then use it do define additional metrics you want collected by decorating functions with:
@metrics.counter(..) @metrics.gauge(..) @metrics.summary(..) @metrics.histogram(..)
The counters count invocations, while the rest of them collect metrics based on the duration of those invocations. You can define labels for each of these, potentially using properties of the request or the response. For example:
from flask import Flask, request from prometheus_flask_exporter import PrometheusMetrics app = Flask(__name__) # group by endpoint rather than path metrics = PrometheusMetrics(app, group_by='endpoint') @app.route('/collection/:collection_id/item/:item_id') @metrics.counter( 'cnt_collection', 'Number of invocations per collection', labels={ 'collection': lambda: request.view_args['collection_id'], 'status': lambda resp: resp.status_code }) def get_item_from_collection(collection_id, item_id): pass
In the example above, hitting the endpoint /collection/10002/item/76
would increment a counter like cnt_collection{ collection="10002", status="200" }
, plus you would get the default metrics (per-endpoint in this example) from the library, by default:
-
flask_http_request_duration_seconds
- HTTP request duration in seconds for all Flask requests by method, path and status -
flask_http_request_total
- Total number of HTTP requests by method and status
There are options to skip tracking certain endpoints, registering more default metrics, or skipping the ones above, or applying the same custom metric to multiple endpoints. Check out the project README to see what’s available.
app = Flask(__name__) metrics = PrometheusMetrics(app) @app.route('/') def main(): pass # requests tracked by default @app.route('/skip') @metrics.do_not_track() def skip(): pass # default metrics are not collected # custom metric to be applied to multiple endpoints common_counter = metrics.counter( 'by_endpoint_counter', 'Request count by endpoints', labels={'endpoint': lambda: request.endpoint} ) @app.route('/common/one') @common_counter def endpoint_one(): pass # tracked by the custom and the default metrics @app.route('/common/two') @common_counter def endpoint_two(): pass # also tracked by the custom and the default metrics # register additional default metrics metrics.register_default( metrics.counter( 'by_path_counter', 'Request count by request paths', labels={'path': lambda: request.path} ) )
The library has some handy extensions for popular multiprocessing libraries, like uWSGI andGunicorn. You can also find small examples for targeted use-cases, including these multiprocessing ones.
Scraping metrics
As mentioned above, the library exposes a /metrics
endpoint on the Flask application by default, which can serve as a target for Prometheus scraping .
From the example with the dashboard above, you can point your Prometheus to a Flask app with the default settings with configuration like this:
scrape_configs: - job_name: 'example' dns_sd_configs: - names: ['app'] port: 5000 type: A refresh_interval: 5s
See the full example in the GitHub repository . This assumes, that Prometheus can target your Flask application instances on http://app:5000/metrics
, where the app
domain name can potentially resolve to multiple IP addresses, like when running in Kubernetes orDocker Swarm.
If exposing the metrics endpoint like this is not suitable for you, perhaps because you don’t want to allow external access to it, you can easily disable it by passing path=None
when creating the PrometheusMetrics
instance.
from flask import Flask, request from prometheus_flask_exporter import PrometheusMetrics app = Flask(__name__) metrics = PrometheusMetrics(app, path=None) ... metrics.start_http_server(5099)
You can then use start_http_server(port)
to expose this endpoint on a different HTTP port, 5099
in the example above. Alternatively, if you’re happy with the endpoint being on the same Flask app, but need to change its path away from /metrics
, you can either pass in a different URI as the path
parameter, or use register_endpoint(..)
to set it up later.
References
- rycus86/prometheus_flask_exporter - This Flask exporter for Prometheus
- prometheus-flask-exporter README - Usage, examples, and configuration options
- prometheus-flask-exporter examples - Examples for setting up Flask app monitoring in different ways
- prometheus-flask-exporter on PyPI - This project on PyPI
- prometheus/client_python - The official Prometheus client library for Python
If you give it a go, open a GitHub issue or leave a comment here with your feedback and suggestions! Thanks!
以上就是本文的全部内容,希望本文的内容对大家的学习或者工作能带来一定的帮助,也希望大家多多支持 码农网
猜你喜欢:本站部分资源来源于网络,本站转载出于传递更多信息之目的,版权归原作者或者来源机构所有,如转载稿涉及版权问题,请联系我们。
C程序设计(第四版)
谭浩强 / 清华大学出版社 / 2010-6-1 / 33.00元
由谭浩强教授著、清华大学出版社出版的《C程序设计》是一本公认的学习C语言程序设计的经典教材。根据C语言的发展和计算机教学的需要,作者在《C程序设计(第三版)》的基础上进行了修订。 《C程序设计(第4版)》按照C语言的新标准C99进行介绍,所有程序都符合C99的规定,使编写程序更加规范;对C语言和程序设计的基本概念和要点讲解透彻,全面而深入;按照作者提出的“提出问题―解决问题―归纳分析”三部曲......一起来看看 《C程序设计(第四版)》 这本书的介绍吧!