Uploaded image for project: 'Hawkular Metrics'
  1. Hawkular Metrics
  2. HWKMETRICS-358

REST API should accept relative timestamps

    XMLWordPrintable

    Details

      Description

      http://www.hawkular.org/docs/rest/rest-metrics.html#_time_ranges

      > The API understands all timestamps as milliseconds since January 1, 1970, 00:00:00 UTC.

      The problem is that the client clock can be out of sync with the server clock. This makes it very difficult to show, say, the last 30 minutes of data. If the client clock is slow, you're missing data at the end. If the client clock is fast, there is a gap at the end of the chart. There's no way to know if the gap is because the clock is ahead or there is just no data for that time period (e.g., the container in OpenShift is stopped).

      In OpenShift, we've settled on using a start timestamp only and leaving off the end timestamp, which defaults to now. However if the client clock is way off, it's possible that the chart will show no data at all or data for a much longer time period.

      What I'd really like is a way to say give me the metrics for the last 30 minutes or hour or day.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                mwringe Matt Wringe
                Reporter:
                spadgett Samuel Padgett
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: