Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-49887

Change /events endpoint behavior

    XMLWordPrintable

Details

    • Task
    • Resolution: Fixed
    • Major
    • 7.1.0
    • None
    • ns_server
    • None
    • 1

    Description

      Currently when "GET /events" is called we return as a default, 250 event logs starting at the oldest entry in the log. The intention to do it that way to begin with was, if a user wanted to get all the logs as batch (batch-1), they would call "GET /events" and chain future requests via "GET /events?sinceTime="time-on-most-recent-log-in-batch-1".

      But that is essential not needed now since we have /eventsStreaming endpoint.

      Based on feedback from Meni Hillel - "GET /events" will now return the most recent 250 entries. Similarly "GET /events?limit=300" will return the most recent 300 entries. 

      The behavior for GET /events?limit=XXX&sinceTime=YYY remains the same and will return XXX entries starting from YYY time.

      cc: Ashwin Govindarajulu.

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            hareen.kancharla Hareen Kancharla
            hareen.kancharla Hareen Kancharla
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty