Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prometheus metrics to get FrankenPHP and PHP version #1225

Open
jchmielniak opened this issue Dec 5, 2024 · 1 comment · May be fixed by #1248
Open

Prometheus metrics to get FrankenPHP and PHP version #1225

jchmielniak opened this issue Dec 5, 2024 · 1 comment · May be fixed by #1248
Assignees
Labels
enhancement New feature or request

Comments

@jchmielniak
Copy link

Describe you feature request

I have plenty of containers running different FrankenPHP/PHP versions. I have to identify containers that are to be updated if some security fix is available. I cannot easily check the running versions.

Describe the solution you'd like
I would like to have additional prometheus metrics like:

# HELP php_info Information about the PHP environment.
# TYPE php_info gauge
php_info{major="8", minor="3", patchlevel="14", version="8.3.14"} 1
# HELP frankenphp_info Information about the FrankenPHP environment.
# TYPE frankenphp_info gauge
frankenphp_info{major="1", minor="3", patchlevel="3", version="1.3.3"} 1

Describe alternatives you've considered
With k8s lifecycle.postStart I can write this information to container filesystem, but it is not a perfect solution to get this info.

$ frankenphp --version
FrankenPHP v1.2.5 PHP 8.3.12 Caddy v2.8.4

Devs could expose metrics about PHP Version, but they have no knowledge about FrankenPHP.

@jchmielniak jchmielniak added the enhancement New feature or request label Dec 5, 2024
@withinboredom
Copy link
Collaborator

Oh, that is a good idea! I'll get that done for the next release!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants