search

TylerBrock / saw

Fast, multi-purpose tool for AWS CloudWatch Logs
MIT License
1.41k stars 79 forks source link

"Get" sample in readme is incomplete #16

Closed MdNor closed 5 years ago

MdNor commented 6 years ago

I'm not sure if this issue is specific to my environment but saw get production --prefix api --start 2018-06-26 --stop 2018-06-28 doesn't work for me. I have to specify the datetime as per RFC 3339.

This is working saw get production --prefix api --start 2018-06-26T00:00:00Z --stop 2018-06-28T00:00:00Z

You may want to revise that portion of the document. The rest is working for me.

Environment

Anyway great tool. Saves me headache trying to figure out CloudWatch API/SDK. Thanks.

TylerBrock commented 6 years ago

It's kind of lame that we require the full timestamp. I think it would be nice if we interpreted the date alone as a full datetime. Thoughts?

MdNor commented 6 years ago

It's kind of lame that we require the full timestamp. I think it would be nice if we interpreted the date alone as a full datetime. Thoughts?

Agree. That is default behavior with most other tools that many already familiar with. At least, that's how I noticed this in the first place.

2018-06-26 should always be interpreted as 2018-06-26T00:00:00Z