zytek
You can survive datacenter (AZ) outage IF you have separate stacks per AZ and don't mix traffic. If you have Kafka cluster spread out in 3 AZ don't get surprised if you just LOWERED your availability because any issue in one AZ makes your stack unstable. And issues in single AZ are quite common.
PromQL support (with extensions) and clustered / HA mode. Great storage efficiency. Plays well for monitoring multiple k8s clusters, works great with Grafana, pretty easily deployed on k8s.
No affiliation, just a happy user.
If you're looking at scaling your Prometheus setup - check out also Victoria Metrics.
Operational simplicity and scalability/robustness are what drive me to it.
I used to to send metrics from multiple Kubernetes clusters with Prometheus - each cluster having Prom with remote_write directive to send metrics to central VictoriaMetrics service.
That way my "edge" prometheus installations are practically "stateless", easily set up using prometheus-operator. You don't even need to add persistent storage to them.
At least I'm getting efficient at bad habits ;-)
But nowadays? I'm all in for Aurora.
Clarification: it wasn't that persons only responsibility, just one of many assignments to help automate Ops in the company.
AWS switches from XEN to KVM for new instance types
.. do you actually TEST those backups?
This questions comes from my experience as a system engineeer who found a critical bug in our MySQL backup solution that prevented them from restoring (inconsistent filesystem). Also, a friend of mine learned the hard way that his Backblaze backup was unrestorable.
Such container
python -m SimpleHTTPServer
works everywhere I need it to work.Anyway, kudos for making a Go project shipped, which I fail to accomplish for several months now ;-)
How we go about optimizing Go
What is sad is that we learn about it from Hacker News and not from AWS, even when we have premium support and our own account manager. :/
Let's see how many of us did their homework after previous "xen update", and how much "10%" is now ;-)
OpenBSD kernel source file style guide
Amazon Route 53 Announces Domain Name Registration, Geo Routing, ..
todo: do not leave 15 year old todo lists in the tree.
This code is the reason perl has a name as a write only language.
Remove oh-so-important-from-a-security-pov OpenSSL_rtdsc() function.
Do not feed RSA private key information to the random subsystem as entropy.
It might be fed to a pluggable random subsystem.... What were they thinking?!
<RANT> Whoever thought that RAND_screen(), feeding the PRNG with the contents
of the local workstation's display, under Win32, was a smart idea,
ought to be banned from security programming. </RANT>
Edit: just noticed, there's a BLOG with it.. http://opensslrampage.org/OpenBSD devs comments documenting progress with cleaning of OpenSSL codebase
It's unfortunate that people no longer dive into original system/program documentation, but google/ask for quick answer. When I started my unix/linux journey some ~14 years ago I always found something more when reading docs and thought of guru's as "these guys that read more docs than I did".
Similarly you may noticed how you can no longer write code comfortably when being offline, because you cannot google "how to make dict() return default value for non existing key" etc.
I am now in the process of killing this bad habit of googling through my "coding" and sysadmin tasks, rather than reading docs and examples available on my system.
PS. sorry for my english
So, you might start by doing that.