How Does API7 Enterprise Achieve Customized Monitoring?

January 14, 2024


Customers often wonder about the monitoring metrics provided by API7 Enterprise and how it caters to customized monitoring requirements. This query naturally leads to three distinct follow-up questions.

  1. API7 Enterprise, built upon Apache APISIX, stands out as an enterprise-level API gateway. It leverages Apache APISIX's observability features and enhances them. What monitoring metrics does it include by default?

  2. Real-world enterprise users typically require the collection of specific metrics, such as the latency distribution for specific response codes. How can API7 Enterprise support this situation? Is it adding all the dimensions to API7 Enterprise?

  3. Additionally, can end-users customize their displays based on specific needs?

In addressing these questions, API7 Enterprise excels in collecting metrics. These indicators are obtained by combining the usage scenarios of various enterprises, which are relatively versatile. However, it acknowledges the need for customization and, as a response, offers a two-fold strategy.

For unique or specialized metrics, API7 Enterprise allows for customized modifications in monitoring. Therefore, developers can customize data collection according to their specific needs.

  • To maintain a standard and efficient approach to data storage, API7 Enterprise integrates with Prometheus.
  • Recognizing the importance of a personalized user experience, API7 Enterprise introduces specific display panels. These panels enable users to showcase data based on their requirements, providing a more focused and effective monitoring experience.

API7 Enterprise integrates with Prometheus

When implementing API7 Enterprise in practical usage scenarios, the adjustment of monitoring metrics becomes a critical phase. This adaptation involves refining default metrics and potentially introducing industry or business-specific metrics. The variance in industry needs, such as the sensitivity of specific response latencies, highlights the significance of such adjustments.

These two entirely different scenarios require on-demand data collection. Detailed collection should be carried out when there is a demand. This approach allows for the maximization of cost and efficiency during the data collection phase. If we collect a large amount of data on the data front but it ends up not being utilized, it is purely wasteful. Therefore, we currently prefer monitoring to be real-time, providing prompt displays of effective data.

API7 Customized Monitoring

In terms of data collection, storage, and presentation, we expect all this data to have clear business value. If there is no value, then data collection should not be pursued.

The monitoring data collection and display for enterprise users are oriented towards business value. The most widely used and effective approach is real-time metric presentation, allowing for quick assessment of API service status. API7 Enterprise Edition meets user monitoring needs in the following ways:

  1. Provides default monitoring metrics to fulfill the common needs of most enterprises.
  2. If there are specific monitoring requirements, metrics data collection and alarm configurations will be customized based on the unique business scenarios of enterprise clients, providing customized solutions on a one-to-one basis.


API7 Enterprise is an enterprise-level API gateway product based on Apache APISIX. It offers default monitoring metrics to meet basic and common monitoring needs. Simultaneously, it supports the classic Prometheus + Grafana combination for customized metric data collection and display. This allows users the flexibility to choose between standard and personalized monitoring solutions.

API7 EnterpriseMonitoring