3.2 Remote Monitoring

In addition to local observability within a merchant’s own infrastructure, Hyperswitch also supports Remote Monitoring. This allows merchants running Hyperswitch in a self-hosted environment to selectively push operational metrics to a centralized Hyperswitch-managed monitoring stack for aggregated visibility and proactive support.

In a typical setup, application services such as the Hyperswitch Router, Consumer, and Producer expose metrics that are scraped by Prometheus (or an equivalent metrics service) within the merchant’s Kubernetes cluster. Instead of keeping these metrics isolated within the merchant’s environment, a filtered subset of metrics can be pushed securely to the Hyperswitch Remote Monitoring stack using Prometheus Remote Write.

These metrics are authenticated before ingestion. An authentication layer (for example, via vmauth) ensures that only authorized systems can send metrics, preventing unauthorized ingestion and enabling source identification on the Hyperswitch side. Once authenticated, the metrics are stored in a centralized metrics backend (such as VictoriaMetrics), where they can be queried and visualized through Grafana dashboards by Hyperswitch administrators.

This architecture enables:

• Centralized visibility across multiple merchant deployments

• Proactive monitoring of infrastructure and application health

• Faster diagnosis of production issues

• Cross-tenant benchmarking and performance tracking (where applicable)

Merchants retain control over what metrics are exported. They can choose (filter) the specific set of infrastructure and application metrics they are comfortable sharing, ensuring privacy while still enabling operational support.

In summary, Remote Monitoring creates a secure bridge between a merchant’s self-hosted Hyperswitch deployment and a centralized observability layer, enabling better reliability, faster troubleshooting, and improved operational governance without requiring direct access to the merchant’s production systems.