Airlock Microgateway components can act as a data source for Prometheus metrics for time-series-based real-time events and alert monitoring.
Prometheus can statically scrape metrics from configured Kubernetes resources or retrieve the scrape targets with service discovery. Since Microgateway can be scaled horizontally, a static configuration might be impractical.
This article describes the configuration and gives an overview of available metrics. The article Monitor the licensed throughput shows another useful example of how Prometheus metrics can be used in a Grafana dashboard.
For security reasons, metrics usually should not be accessible outside your network. We strongly recommend setting appropriate network policies for metrics access.
To allow scraping metrics from web applications with injected Airlock Microgateway Engines, the application's corresponding metrics port should be excluded via a Pod annotation. Multiple ports can be excluded in a comma-separated list.
Example:sidecar.microgateway.airlock.com/excludeInboundPorts: "<YourWebApplicationMetricsPort>"