You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@eagle.apache.org by Daniel Zhou <Da...@dataguise.com> on 2016/06/17 19:29:21 UTC
policy match criteria field : timestamp
Hi guys,
I've one question about match criteria field timestamp in policy setting: why eagle expect user to input time in milliseconds?
Take 'hdfsAudit" for example, hdfs audit log parser converts human readable date to milliseconds and then construct a new message for siddhi engine to evaluate. But this cause trouble for users:
- User might do not know what is the timestamp he need to set, we shouldn't expect a user to do this calculation by himself.
- User might only want to set time interval such as "2016-04-06 00:01:00 to 2016-04-07 9:01:00", a drop down menu for time setting should make sense.
Any advice?
Regards,
Da
Re: policy match criteria field : timestamp
Posted by Senthil Kumar <se...@gmail.com>.
Thanks Daniel for checking this..
Yes i too noticed In Policy Creation Page it's accepting only Timestamp in
Milliseconds.
[image: Inline image 1]
It's really good to allow users enter only Date Time not converted
milliseconds .. Also in meta data we should change LONG to DATE ..
--Senthil
On Sat, Jun 18, 2016 at 12:59 AM, Daniel Zhou <Da...@dataguise.com>
wrote:
> Hi guys,
>
> I've one question about match criteria field timestamp in policy
> setting: why eagle expect user to input time in milliseconds?
>
> Take 'hdfsAudit" for example, hdfs audit log parser converts human
> readable date to milliseconds and then construct a new message for siddhi
> engine to evaluate. But this cause trouble for users:
>
> - User might do not know what is the timestamp he need to set,
> we shouldn't expect a user to do this calculation by himself.
>
> - User might only want to set time interval such as "2016-04-06
> 00:01:00 to 2016-04-07 9:01:00", a drop down menu for time setting should
> make sense.
>
> Any advice?
>
> Regards,
> Da
>