Uploaded image for project: 'Configuration Persistence Service'
  1. Configuration Persistence Service
  2. CPS-2121

CPS NCMP: http_client_requests_* metrics are not available for every endpoints or not in correct form

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: High High
    • New Delhi Release
    • None
    • NCMP
    • None

      Description:
      For bug hunting and debugging we use the spring restTemplate http_client_requests_* and http_server_requests_* metrics.
      Currently in CPS NCMP the outgoing http_client_requests_* metrics are not available for DMI /dmi/v1/ch/{cmHandleId}/data/ds/{datastore} and /dmi/v1/data endpoint calls
      It is available for DMI /dmi/v1/ch/ABCD/modules calls which I guess using the same restTemplate, however we have separate metrics sent with uri=/dmi/v1/ch/ABCD/modules tags where we have separate metrics for each cmhandle instead of having one metrics which contains every calls towards  uri=/dmi/v1/ch/{cmHandleId}/modules
      It is not clear if it is a bug or a configuration issue.
      I guess it never worked before, or at least it is not working for a long time.
      Lack of client metrics makes customer debugging complicated so we definitely need it to be able to compare the DMI plugin server request metrics with CPS client request metrics.

      CPS NCMP http_client_requests_* metrics showing only health and modules endpoint calls but no calls towards  /dmi/v1/ch/{cmHandleId}/data/ds/{datastore}, /dmi/v1/data

      However on DMI plugin side we see the incoming calls from CPS

      Expected behavior
      Have http_client_requests_* metrics for each DMI endpoints /dmi/v1/ch/{cmHandleId}/data/ds/{datastore}, /dmi/v1/ch/{cmHandleId}/modules, /dmi/v1/data etc

            leventecsanyi Levente Csanyi
            csaba.eder csaba Eder
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: