itcsoft54

In add after some other tests, it's work with `Version: 1.4.0+49+gc43d31f` but not with `Version: 1.4.0+162+gc46f12f0`

Since `Version: 1.4.0+162+gc46f12f0`, aptly seems to make some thing that is incompatible with driver OverlayFS in rootless mode. Changing to VFS is a workaround.

Rename metric create breaking change with existing use of phpfpm_exporter. Need to deprecate old metric instead of remove (or rename) it

``` The Full status returns for each process: ; request duration - the duration in µs of the requests; ``` From php-fpm conf : https://github.com/php/php-src/blob/83697aa95e1d3eefe7bbc4da5e77d899be091be2/sapi/fpm/www.conf.in#L208

User that run php-fpm process and/or own php-fpm depend of various parameters. All are already documented in php documentation. The socket is own by user and that run process, www-data...

Please check if ENV is prior to values in configuration file. If not it can break the way that debian package Prometheus export (using /etc/default/.conf file for parameters) that currently...

php-fpm is base on php-fpm status page, from source code (https://github.com/php/php-src/blob/master/sapi/fpm/fpm/fpm_status.c), they have no "php version" field.

@estahn the PR #173 fix this issue, so we can close it, but bot has mark it at "wontfix"

Hello, If you go in this piece of code : https://github.com/hipages/php-fpm_exporter/blob/master/phpfpm/phpfpm.go#L166 You see that exporter use json&full to get metric. So if you have 404 in your log, exporter doesn't...

Separated exporter are still usefull, if you want to limit ressources allocated to collect metrics or cache informations collected to avoid heavy load on php-fpm.