Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-10309

Measuring and tracking API response times within the 3scale API Management platform

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Can't Do
    • Icon: Major Major
    • None
    • 2.13
    • System
    • False
    • None
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • 0
    • 0% 0%

      It would be great to have the functionality to measure and track API response times WITHIN the 3scale API Management platform. Specifically, the following items:

      • Real-time Response Time Monitoring:
        Ability to monitor API response times in real-time, enabling us to identify and address performance issues promptly.
      • Average Response Time Calculation:
        Having an average response time calculation feature that provides insights into the typical performance of the APIs over a given period.
      • Customizable Performance Thresholds:
        Flexibility to set performance thresholds for response times, allowing to receive alerts or trigger actions when response times exceed predefined limits.
      • Historical Data Analysis:
        The feature should support the ability to analyze historical response time data, enabling to identify trends, patterns, and potential bottlenecks for further optimization.

      Integrating this capability directly into the 3scale API Management platform would streamline the monitoring and analysis processes.

      Although there may be tools and technologies currently available, having this feature within 3Scale platform would provide a cohesive and unified solution for API management.

            Unassigned Unassigned
            rhn-support-icaldero Ivan Calderon Clemente
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: