Lack of PID uniqueness in container environments makes prometheus_multiproc difficult to use

In environments where each container is running in its own PID namespace, multiple instances of the same container will quickly result in (silently) conflicting file names as any my-favorite-server.py process will likely have the same low, single or double digit PID in each of the multiple containers. As a result, the different processes will attempt to mmap the same file in the shared multiprocess metric directory, and various scary errors that aren't always easy to understand the root cause will occur.

It would be beneficial if something in addition to the PID was used to help ensure uniqueness across the files in the PROMETHEUS_MULTIPROC_DIR, or if a string could be passed in at initialization time to be embedded in the file names, such as a container or pod name, or another value determined by the application.

Commencez par retracer comment prometheus_multiproc nomme les fichiers dans PROMETHEUS_MULTIPROC_DIR et comment il dérive les noms à partir des identifiants de processus. Comparez le comportement de plusieurs conteneurs partageant le répertoire, puis déterminez un mécanisme d’unicité ou une valeur d’initialisation adapté à l’issue. C’est terminé lorsque les processus de conteneurs concurrents ne font plus de mmap de fichiers en conflit et que le cas d’échec pertinent est couvert par des tests.