Hi Pankaj,

What API reference document are you using?  Is it the v7.2.1 doc named docu60111.pdf?

I'm trying to locate the right doc to look for this specific API call.  Some of the URIs change between different versions of OneFS.

Thanks.

Thanks for the Reply RobChang,

I need to check which document we were referring for Platform APIs.

But generally, I prefer to first execute command https:// :8080/ ? describe which gives all the required information for that call.

For Isilon events I executed this call and below is the piece of output for it and It is clearly described how begin parameter should work, but unfortunately when I provide epoch times with begin, though it gives less number of events in output but still results are not correct.

==================================================================

/platform/2/event/events 
Overview:
  This resource applies the standard collection pattern to events.
Method GET:
  Retrieve event information.
Query Arguments:
  sort=
  The field that will be used for sorting.
  count=
  If true, return a count of events.
  begin=
   
  Specifies the earliest time to query events from.
  end=
  Specifies the latest time to query events from.

Thanks,

Pankaj

I've been able to reproduce this behavior on a 7.2.1 cluster:

https:// :8080/platform/2/event/events?begin=1468488325

...

...

"media_type" : "HDD",

"model" : "HGST HUS724040ALA640",

"val" : 0.0

},

"start" : 1468432054,

"update_count" : 1,

"value" : 0.0

...

...

x210-1# perl -e 'print scalar localtime 1468488325, "\n"'

Thu Jul 14 05:25:25 2016

x210-1# perl -e 'print scalar localtime 1468432054, "\n"'

Wed Jul 13 13:47:34 2016

So on the surface this looks like a bug to me, but I'll have to consult with some of our API SMEs.  I did check OneFS 8.0, and I could not reproduce the problem.

A long shot, but doesn't an event have a time interval [start, end] ?

So when the event interval overlaps with the query interval,

shouldn't the event be included? In the original example, event end

is null, which means that the event has not yet "ended".  Thus

it would be included with any query for "recent" events.

cheers

-- Peter

Hi Kip,

The "begin" parameter is no longer supported on version 8.0 so you would not be able to verify this issue.

Thanks,

Pankaj

> The "begin" parameter is no longer supported on version 8.0 so you would not be able to verify this issue.

I used this:

https:// :8080/platform/3/event/eventgroup-occurrences?begin=1468488325

> A long shot, but doesn't an event have a time interval [start, end] ?

Yes, events have defined intervals.

> So when the event interval overlaps with the query interval, shouldn't the event be included?

Well, I don't know about "should" , but it could based on the design of the feature.  My research didn't clearly indicate that this is the case.  I've asked around internally and if I find out anything I'll post it here.  Frankly I can see the logic behind including events that are or were active during the search interval.  My first thought, though, when reading about "begin" was that only events that *started* after that time would be included in results.

Whatever the behavior, it's clear that the documentation needs some updating.