Uploaded image for project: 'RAML Module Builder'
  1. RAML Module Builder
  2. RMB-669

Add default metrics to RMB: incoming API calls

    XMLWordPrintable

Details

    • CP: sprint 96, CP: sprint 97
    • 0
    • Core: Platform

    Description

      Similarly to metrics being added to Okapi via OKAPI-860.

      What metrics should be added?

      1. outgoing API calls need to have their own set of metrics:

      • rate (reqs/sec) of calls to API "x"
      • total count of calls to API "x"
      • duration of calls to API "x"

      We can provide instrumentation in the verticle: https://github.com/folio-org/raml-module-builder/blob/master/domain-models-runtime/src/main/java/org/folio/rest/RestVerticle.java

      TestRail: Results

        Attachments

          Issue Links

            clones

            New Feature - New feature requests RMB-655 Add default metrics to RMB: Outgoing API calls

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            is blocked by

            Task - A task that needs to be done. RMB-720 Replace DropWizard with Micrometer InfluxDB metrics options

            • TBD - To be determined
            • Closed
            relates to

            New Feature - New feature requests RMB-668 Add default metrics to RMB: DB calls

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OKAPI-860 Add HTTP (API calls, system calls) metrics to Okapi

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            New Feature - New feature requests RMB-655 Add default metrics to RMB: Outgoing API calls

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Task - A task that needs to be done. RMB-670 Fix RestVerticle requestId logging, replace log4j 1.2 MDC by log4j 2 ThreadContext

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Activity

              People

                hji Hongwei Ji
                jakub Jakub Skoczen
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases