o QDi@sddlZddlZddlZddlZddlmZddlmZddlmZzddl m Z Wne y9ddl m Z Ynwe eZdddZGd d d ejZdd d Zd dZddZdS)N)settings) HttpResponse) multiprocess) HTTPServercCs*tjddks Jdtj||ddS)aExports Prometheus metrics on an HTTPServer running in its own thread. The server runs on the given port and is by default listenning on all interfaces. This HTTPServer is fully independent of Django and its stack. This offers the advantage that even if Django becomes unable to respond, the HTTPServer will continue to function and export metrics. However, this also means that the features offered by Django (like middlewares or WSGI) can't be used. Now here's the really weird part. When Django runs with the auto-reloader enabled (which is the default, you can disable it with `manage.py runserver --noreload`), it forks and executes manage.py twice. That's wasteful but usually OK. It starts being a problem when you try to open a port, like we do. We can detect that we're running under an autoreloader through the presence of the RUN_MAIN environment variable, so we abort if we're trying to export under an autoreloader and trying to open a port. RUN_MAINtrueThe thread-based exporter can't be safely used when django's autoreloader is active. Use the URL exporter, or start django with --noreload. See documentation/exports.md.)addrN)osenvirongetprometheus_clientstart_http_server)portr rR/var/www/Datamplify/venv/lib/python3.10/site-packages/django_prometheus/exports.pySetupPrometheusEndpointOnPortsrcs(eZdZdZfddZddZZS)PrometheusEndpointServerz?A thread class that holds an http and makes it serve_forever().cs||_tj|i|dSN)httpdsuper__init__)selfrargskwargs __class__rrr3sz!PrometheusEndpointServer.__init__cCs|jdSr)r serve_forever)rrrrrun7szPrometheusEndpointServer.run)__name__ __module__ __qualname____doc__rr __classcell__rrrrr0s rc Cstjddks Jd|D],}z t||ftj}Wn ty#Yqwt|}d|_| t d||St ddS)aLike SetupPrometheusEndpointOnPort, but tries several ports. This is useful when you're running Django as a WSGI application with multiple processes and you want Prometheus to discover all workers. Each worker will grab a port and you can use Prometheus to aggregate across workers. port_range may be any iterable object that contains a list of ports. Typically this would be a `range` of contiguous ports. As soon as one port is found that can serve, use this one and stop trying. Returns the port chosen (an `int`), or `None` if no port in the supplied range was available. The same caveats regarding autoreload apply. Do not use this when Django's autoreloader is active. rrr Tz'Exporting Prometheus /metrics/ on port zICannot export Prometheus /metrics/ - no available ports in supplied rangeN) r r r rrMetricsHandlerOSErrorrdaemonstartloggerinfowarning) port_ranger rrthreadrrr"SetupPrometheusEndpointOnPortRange;s   r.cCsLttdd}ttdd}ttdd}|rt||dS|r$t||dSdS)z/Exports metrics so Prometheus can collect them.PROMETHEUS_METRICS_EXPORT_PORTN$PROMETHEUS_METRICS_EXPORT_PORT_RANGE!PROMETHEUS_METRICS_EXPORT_ADDRESSr)getattrrr.r)rr,r rrr SetupPrometheusExportsFromConfigds   r3cCsFdtjvs dtjvrt}t|ntj}t|}t|tj dS)zmExports /metrics as a Django view. You can use django_prometheus.urls to map /metrics to this view. PROMETHEUS_MULTIPROC_DIRprometheus_multiproc_dir) content_type) r r rCollectorRegistryrMultiProcessCollectorREGISTRYgenerate_latestrCONTENT_TYPE_LATEST)requestregistry metrics_pagerrrExportToDjangoViewos   r?)r)loggingr threadingr django.confr django.httprrBaseHTTPServerr ImportError http.server getLoggerr r)rThreadrr.r3r?rrrrs$       )