Ever since container technology hit the scene in 2013, it’s generated excitement from developers and operations teams. Using containers to deliver apps and microservices helps enable large scalable deployments with smoother rollouts, accomplishing in minutes what used to take hours, if not days. Delivering the containers themselves, however, can still be challenging to do across all types of modern infrastructure.
In order to keep digital services running around the clock, teams need to be able to solve problems faster—or, ideally, in real time. Many vendors claim to provide value and help organizations bolster their digital operations management.
Root Cause Analysis (RCA) is an all-encompassing process. It is usually very complicated and often requires many people with many different skills – all trying to tackle an incident to determine what happened, when, why, how and ultimately who (to blame). There is, however, secret sauce today that can help solve many issues before a “full-scale” RCA process is initiated – and that is Root Cause Changes (RCC).
The word serverless starts to become a hot topic in the world of Computer Programming. Maybe you heard the word Serverless a couple of times, either by going to conferences or by talking with other people.
Have you ever wanted to get important alerts from Azure Monitor notified on your smartphone and have all the important details of the problem at your fingertips? Have you ever missed the option to easily change the status of alerts from Azure Monitor in the Azure smartphone app? Ever missed a push notification because there was no persistent and advanced alerting? Then this article is for you.
IBM recently announced an expanded Cloud Paks offering with LogDNA. With this offering, developers and engineering teams can easily aggregate and search huge volumes of data from any source to gain real-time insights on their applications. LogDNA is now offered by IBM and deployable on-premise or multi-cloud with all IBM Cloud Paks including Cloud Pak for Applications, Cloud Pak for Data, Cloud Pak for Integration, Cloud Pak for Multi-cloud Management, and Cloud Pak for Automation.
Sensu Summit 2019 featured talks from the Sensu Community, including Harvard University SRE Molly Duggan, who shared how the Harvard FAS Research Computing Department uses CI/CD pipelines and the Sensu Go API to automate monitoring for their highly complex infrastructure.
I never thought that this would be my life. For more than a year, I’ve been talking to individual customers and getting inspired by their stories, challenges, and goals. Now, I have the spectacular opportunity to meet entire conference rooms of people who are excited to hear about my story, challenges, and goals. This is my time to give back to the types of users who have inspired me ever since I entered the serverless space.
This is a technical deep dive into the authentication process — a necessary first step before addressing the authorization decisions that are at the core of Elasticsearch security. The following will be a very detailed explanation of the inner workings of a key part of the authentication process: realms. If you'd prefer to start with a broader view of authentication (and authorization) in Elasticsearch, you may want to check out Demystifying authentication and authorization in Elasticsearch.
Have you used Elastic Maps in Kibana yet? I am very excited about multiple layer support. Heat maps, vector layers from the Elastic Maps Service, and even individual documents all in the same interface! What a fantastic way to analyze and visualize your data. But what about geospatial data that’s not in Elasticsearch? Maybe you want to overlay a shapefile of regional sales territories with sales aggregations.
