Marcin Ciszak

Also, option to `order` incidents by `createdAt` / `updatedAt` would be very useful.

Will take a stab at adding the filtering in for existing data. As for the `componentID` adding that in the Incident model would be pretty handy. Basic use case here...

Terraform native module would be nice, however, in the interim you can achieve similar thing with `aws_cloudformation_stack`. Currently lambstatus stack exceeds AWS size limitations (potentially splitting that in smaller chunks...

I was wondering it adding network check failure/success rates would be useful in the report? In some cases one might get an occasional network check failure but it might not...

Also, adding top level field e.g. `Success`, `CheckSuccess` (or just `Status`) could be useful and would save time going through individual results to determine if there were any errors?

Another thought. I think It would be great to aggregate some checks and rename some to be more representative as to what check took place, what were the details of...

Looks good. I've added a couple of related questions in the [Issue](https://github.com/apprenda/kuberang/issues/5#issuecomment-265214792) itself.

Hi @Anthirian. Thanks for the report. The above is most likely caused by the significant RBAC structure in one of your clusters. Would you be able to share more detail...

Hi @kplimack. Thanks for logging the issue above. We'll look into that.

Hello @greg-cook. Thanks for pointing that out. We're aware of existence of Shopify/krane tool and should come up with a solution to that potential issue. Note that appvia/krane is not...