You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can use any template engine to process Angie config and generate relevant status_zone directives.
All internal variables exist and processed in runtime only, while status_zone must know its name before starting worker processes in order to be able to allocate all the required shared memory zones where the relevant metrics are stored.
my config contains multiple names under same server section.
It would be neat to be able to provide some context to status_zone directive right in place
my config contains multiple names under same server section. It would be neat to be able to provide some context to status_zone directive right in place
Understood. Thanks. We will consider how Angie metrics API can be improved for this particular case in the future.
I'm looking for a way to dynamically create metrics using variables in status_zone directive, like
I hope this will allow to export prometheus metrics per used domain name later in template
The text was updated successfully, but these errors were encountered: