- Save up to 90% disk space based on VRR (Variable Replication factor and Retention) estimations by playing with replication, retention and custom classification.
Differentiate important from redundant information and apply different policies to them.
- Log useful information for once, that you will be able to filter, query, plot and alert on.
We are covering parameters, structured arguments, and how to avoid grok to parse them.
- Save tons of OPS time by using the right tools to empower DEVs to be responsible of their logs.
Let's avoid bothering our heroes with each change in a log line. Minimizing OPS time is paramount.
haven't contacted the author but he describes his supposed route. I'm trying to replicate his results and there is indeed a possible integer overflow condition but I'd be doubtful of reports of successful exploitation with systems linked with a newer version of glibc w/ heap consistency checking, stackguard &/| aslr.
I've been over every file that referenced by ngx_http_request_t http://lxr.evanmiller.org/http/ident?i=ngx_http_request_t looking for buffers, directly or indirectly using a value derived from a ngx_http_request->count (not -> main -> count), and although the bug condition he describes is possibly real, I'd love to see an RCE proof of concept from the author.
- Save up to 90% disk space based on VRR (Variable Replication factor and Retention) estimations by playing with replication, retention and custom classification. Differentiate important from redundant information and apply different policies to them.
- Log useful information for once, that you will be able to filter, query, plot and alert on. We are covering parameters, structured arguments, and how to avoid grok to parse them.
- Save tons of OPS time by using the right tools to empower DEVs to be responsible of their logs. Let's avoid bothering our heroes with each change in a log line. Minimizing OPS time is paramount.