Operations | Monitoring | ITSM | DevOps | Cloud

This week, ChaosSearch announced some exciting news -- we're honored to have been named Most Likely to be the Next Boston Unicorn in Startup Boston’s first-ever Community Awards! The award celebrates companies that have made extraordinary achievements in the startup ecosystem in Boston, and represents grassroots recognition from tech entrepreneurs, employees, investors, journalists, and educators in the region.

Dropped log lines due to out-of-order timestamps can be a thing of the past! Allowing out-of-order writes has been one of the most-requested features for Loki, and we’re happy to announce that in the upcoming v2.4 release, the requirement to have log lines arrive in order by timestamp will be lifted. Simple configuration will allow out-of-order writes for Loki v2.4.

To monitor your Elastic Stack with Elastic Cloud on Kubernetes (ECK), you can deploy Metricbeat and Filebeat to collect metrics and logs and send them to the monitoring cluster, as mentioned in this blog. However, this requires understanding and managing the complexity of Beats configuration and Kubernetes role-based access control (RBAC). Now, in ECK 1.7, the Elasticsearch and Kibana resources have been enhanced to let us specify a reference to a monitoring cluster.

Monitoring, troubleshooting, and debugging your code all require logging. It not only makes the underlying execution of your project more visible and understandable, but it also makes the approach more approachable. Intelligent logging procedures can assist everyone in a company or community to stay on the same page about the project's status and progress.

Sysadmins, cartographers, and dashboard designers can now personalize Elastic Maps to create richer geodata stories. The 7.14 release of Elastic Maps has the geo capabilities to highlight points of interest, hide unnecessary details, and help you explore new trends in your data. Elastic Maps is available now on Elastic Cloud — the only hosted Elasticsearch offering to include all of its latest features.

“What happened?” If you’ve never uttered those words, this blog isn’t for you. For those of us in cybersecurity, this pint-sized phrase triggers memories of unforeseen security incidents and long email threads with the CISO. What happened to those security patches? Why didn’t we prevent that intrusion? Organizations tend to lean towards protecting their borders and less towards understanding the importance of overall security hygiene.