Uploaded image for project: 'CDAP'
  1. CDAP
  2. CDAP-12098

Inconsistent response from metrics API

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 6.1.0
    • Component/s: Metrics
    • Labels:
      None
    • Rank:
      1|i004wf:

      Description

      Steps to reproduce:
      1. Open a pipeline that was deployed roughly a week ago and has couple of runs.
      2. Choose a run and try to get metrics(say 'user.<stage-name>.records.in' for any stage in the pipeline for that particular run.
      3. In the POST metrics api call (/v3/metrics/query) set "aggregate: false" in the "timeRange" object in "body".

      Expected:
      A time series data for the number of records that went in to the stage for that particular run
      Actual:
      An empty series with no data point.

      What makes this misleading is when the same metrics call is made with "aggregate: true" we get a single data time series with "time: 0" and "value: NN". which is correct.

      The pipeline that I tried is omintureHitsPipeline and tried querying data for `BrowserData` source node.

        Attachments

          Activity

            People

            • Assignee:
              yaojie Yaojie Feng
              Reporter:
              ajai Ajai Narayan
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: