A mix of content this week, from some good posts on managing monitoring infrastructure to tools for maintaining health test suites, provisioning Kubernetes clusters for development and lots more.
StackHawk sponsors Devops Weekly
gRPC security scanning is in open beta. Scan each microservice and improve engineering best practices with StackHawk’s support for scanning gRPC services. Sign up to join the first gRPC security testing beta available in the market!
If you run your own monitoring infrastructure at scale, you’ll invariably be surprised by the cost of storage. This post looks at one team’s work to reduce the storage cost by a third for their Prometheus infrastructure.
Another monitoring post. This one on the design of a Prometheus, Grafana, Alert Manager setup and considering the tradeoffs around various topologies.
A look at TypeAPI, a new alternative to OpenAPI for describing an API that is more optimised for automatically generating client tools.
A nice introduction to AWS Vault, which aims to solve the problem of AWS credentials ending up in plain text all over the place.
A nice overview of Kubernetes evolution to a system that’s well suited to large batch processing workloads as well as lots of microservices.
If you’re managing an ElasticSearch cluster then keeping a track on unassigned shards is important for monitoring search stability. This post explains why as well as looking at what to measure.
Captain is a CLI tool that can detect and quarantine flaky tests, automatically retry failed tests, partition files for parallel execution and generate comprehensive test failure summaries. It works with your existing test runners.
An interesting use of GPT, in this case it consumes event information from Falco and then generates recommendations for actions that are shared in Slack.
Provisioning a Kubernetes cluster for development isn’t always simple. Kubelift aims to provide a great experience for anyone wanting a single node Kubernetes setup on Azure, with an UI inspired by Vagrant.
A handy tool for visualising a toolchain, document which tools you’re using and where they are in their adoption.