You can’t really move away from bash, unless there would be alternative as widely available on different Unix systems as bash is.
Yes, you came up with a nice syntax for your Haskell scripts, but what it cost to install all required dependencies on, for example, newly created Ubuntu server?
It gives me so much Perl one-liners vibe, when `perl` command combined with `-p` and `-e` flags allows you to write super concise programs for bash pipelines.
I just watched the presentation from post url and I really liked the tool Roy talked about at 19:00-22:40.
Also he answered a question (34:07-35:23) about which algorithm they use to actually tune thresholds by saying that he was sure it would be open-sourced at some point.
So I searched through the entire list of public repositories on https://github.com/Netflix?sort=stargazers and didn't find anything relatively similar to what Roy described.
Does anyone know:
1. What is the name of the metrics tuning system?
2. Is it open-source?
3. Is it actively supported or is it deprecated?
Nice article! Actually it would be great to see suggestions from LLM for each error log highlighted in the RCA report, so you don't need to ask OpenAI about it manually.
At my current employer we have a company-wide service for aggregating error logs in particular (WARN, ERORR level log rows and stacktraces, if it was an exception) so developers can analyze them for debugging purposes. Also it automatically gathers information about incoming http request (geo, ip address, user agent, etc) and you can easily see a particular segment of errors, and what kind of users getting them.
As I can see you have logs quantitative metric https://community-demo.coroot.com/p/oc1vhnmq/app/default:Dep... but without any detalization (maybe it works this way only for the demo app). I mean, it would be great to be able to inspect each ERROR event separately or to define custom SLO with alert for particular type of errors.
Another great feature we use a lot is historical data, so you can find patterns of error spikes on months scale and when it has gone after fix.
FYI this error-service I'm talking about is built on top of the ClickHouse, so it's quite responsive regardless of the large volumes of data.
Another thing I want to mention is cron-like workload (or batch jobs, you name it). Is there any support or useful metrics for it?