In this blog miniseries, I’m talking about how to think about doing data analysis, the Honeycomb way. In Part I, I talked about how heatmaps help us understand how data analysis works. In Part II, I’d like to broaden the perspective to include the subject of actually analyzing data.

Red Hat OpenShift container platform enables enterprise/start-ups to develop, deploy, and manage existing container applications on-premise or in the cloud. Organizations can make use of proven, efficient, and powerful open-source technologies to create and deploy applications that are secured, scalable, highly available with minimal management and configuration.

Organizations that handle logging at scale eventually run into the same problem: too many events are being generated, and logging components can’t keep up. Even with persistent queues and other mitigating features enabled, there’s simply not enough of a buffer between log generators and log ingesters to handle the volume of log lines coming in.

We have a running joke at Stackery regarding our tiny little gong that’s used to mark the occasion when we get a new customer. And while I’m all about the sales team celebrating their successes (albeit with a far-too-small gong), I felt like the dev team needed its own way to commemorate major product releases and iterations.

As you know, B2B marketing refers to the techniques and practices used by companies to sell their product or services to other organizations and businesses rather than individuals. The most essential thing in B2B marketing is to reach out to the right customers and influence them to purchase. However, in achieving this, there are some pitfalls you would want to avoid.

Logging is an important topic in software development, especially if you need to analyze bugs and other unexpected events in your production environment. Implementing your logging often seems easy. But as you probably experienced yourself, logging is far more complex than it might seem. That’s why you can find lots of articles about it here on the blog.

Ever since humankind developed the ability to write, much of our progress has been made thanks to recording and using data. In ages long past, notes were made on the production and gathering of resources, the exact number of available soldiers and other important personnel, and were compiled and stored by hand. Because of this documentation method, important information was also prone to being misplaced, lost, or even mishandled.

I hosted a webinar where I covered why logging is important, how to choose a logging provider. And then shared our experience of setting up logging on Kubernetes containers, the Kubernetes logging framework and the logging best practices we’ve implemented internally and supported our customers who run Kubernetes in production.

Healthcare organizations that deploy Epic to support the patients that they see every day have a responsibility to ensure that Epic is always online and performing well. Take for example, a hospital that uses Epic for all its patient services to keep the patients healthy and to ensure their safety Epic needs to be online 24×7. Monitoring and troubleshooting both the underlying infrastructure and Epic are critical to ensuring patients get the care they need.