April was one of our busiest and exciting month of events so far. Here’s a recap of where we were, what we saw and where you can catch us next. While writing this, we are on the road at both DockerCon and Open Infrastructure Summit so if you are there, don’t hesitate to find our pink shirts to meet us and get a demo!
How many recipes do you have in your cookbook? This isn’t off topic, for today I’ll be exploring the ins and outs of Chef logging to help you maintain the state of your kitchen. (Last of the bad puns.) For those unfamiliar, Chef is a configuration management and platform automation tool that sits in the same space as Puppet (which we wrote about previously).
I spoke at Container World 2019 in Santa Clara and shared insights on what LogDNA has learned in scaling Elastic Search using Kubernetes over the years. Here are some highlights from the talk and you can also find the slide deck below.
Today we are releasing Grafana 5.4.4 and 6.1.5. These patch releases include an important security fix for all Grafana installations between 5.4.0 and 6.1.6. Grafana installs between 6.0.0 and 6.1.4 are less vulnerable due to other security improvements. These versions are only vulnerable if the administrator has disabled default security settings.
Recently Amazon launched Open Distro for Elasticsearch, a distribution of Elasticsearch with a number of additional features. The project was created out of concern that Elasticsearch was starting to include proprietary features, and that Elastic was straying from its open source roots.
So you have a Grafana dashboard that shows failures at 0.01% and that latency is down throughout the company. But rather than get a pat on the back, “your boss’s boss is saying cut the crap or stop the mumbo jumbo. What does it really mean for our business?” said Peter Zaitsev, CEO of Percona, which offers solutions such as support, management services, consultant training, and custom engineering for MySQL, MariaDB, MongoDB, Postgres and other open source databases.
We are pleased to announce the release of Ingest Budgets, a new feature which enables our users to track and control how much data is ingested into Sumo Logic and avoid overages in environments where data ingestion can spike unexpectedly. With Ingest Budgets, users can create budgets with ingestion thresholds that either cap data ingestion to a daily limit or simply alert whenever the threshold is exceeded.
Last month, AWS announced an initiative called Open Distro for Elasticsearch. Since then, there has been a lot of debate as to what this move means for the future of the ELK Stack and the community. What are the motives behind this move? Does this split actually signify a fork?
