o ˜à·iÙ ã@svUddlZddlZddlmZmZmZddlmZeeƒZ da ej dBe d<dd„Z defdd „Zd d „Zd d „ZdS)éN)ÚREGISTRYÚCollectorRegistryÚ multiprocess)Ú init_loggerÚ_prometheus_multiproc_dircCs>dtjvrt ¡atjtjd<t dtj¡dSt d¡dS)zFSet up prometheus multiprocessing directory if not already configured.ÚPROMETHEUS_MULTIPROC_DIRz&Created PROMETHEUS_MULTIPROC_DIR at %sz½Found PROMETHEUS_MULTIPROC_DIR was set by user. This directory must be wiped between vLLM runs or you will find inaccurate metrics. Unset the variable and vLLM will properly handle cleanup.N) ÚosÚenvironÚtempfileÚTemporaryDirectoryrÚnameÚloggerÚdebugÚwarning©rrúP/home/ubuntu/vllm_env/lib/python3.10/site-packages/vllm/v1/metrics/prometheus.pyÚsetup_multiprocess_prometheuss  ÿÿrÚreturncCs0t d¡durt d¡tƒ}t |¡|StS)zŽGet the appropriate prometheus registry based on multiprocessing configuration. Returns: Registry: A prometheus registry rNz2Using multiprocess registry for prometheus metrics)rÚgetenvr rrrÚMultiProcessCollectorr)ÚregistryrrrÚget_prometheus_registry's   rcCs6t}t|jƒD]}t|dƒrd|jvr| |¡qdS)aUnregister any existing vLLM collectors from the prometheus registry. This is useful for testing and CI/CD where metrics may be registered multiple times across test runs. Also, in case of multiprocess, we need to unregister the metrics from the global registry. Ú_nameÚvllmN)rÚlistÚ_collector_to_namesÚhasattrrÚ unregister)rÚ collectorrrrÚunregister_vllm_metrics7s   €þrc Csnt}|durdSzt ¡}t ||¡t d|¡WdSty6}zt dt |ƒ¡WYd}~dSd}~ww)zShutdown prometheus metrics.Nz0Marked Prometheus metrics for process %d as deadz Error during metrics cleanup: %s) rrÚgetpidrÚmark_process_deadr rÚ ExceptionÚerrorÚstr)ÚpathÚpidÚerrrÚshutdown_prometheusGs €ÿr()rr Úprometheus_clientrrrÚ vllm.loggerrÚ__name__r rr Ú__annotations__rrrr(rrrrÚs