All Together Now: Better Debugging With Multiple Visualizations

“Nines don’t matter when users aren’t happy” is something you may have heard a time or two from folks here at Honeycomb. We often emphasize the fact that while your system can look healthy at a high level, deep down something is likely broken in ways that cause pain for users. If you are empowered to ask detailed questions about your services, you can find and understand these problems more easily.


Best serverless video tutorials

Now I’m sure this is not the case for everyone but for me personally, I like watching video tutorials on subjects that I need help with. I spent a good amount of time searching for these tutorials and while there might be a lot more of them out there I believe these are some of the best and easiest tutorials to follow but nevertheless, I’d like to keep this list updated so if you have any suggestions please let me know.


How to Check Memory Usage in WebLogic Console and Monitoring WebLogic JVM Heap and CPU Usage in WLSDM

Weak JVM performance affects WebLogic domain performance directly. That’s why the host’s CPU and memory usage is very important in terms of improving WebLogic performance. Higher CPU consumption and Garbage Collection duration can cause applications to run slowly, even cause the WebLogic servers facing downtime. JVM instances in a WebLogic need to be monitored constantly and notification/alarm infrastructure must be installed as well.


Why the Rise of DevOps Demands Continuous Optimization

The rise of DevOps has been wonderful. Now that developers and operations folk can work together in an agile setting, deployment windows are no longer stuck within slow, quarterly rhythms. Production deployments can occur hundreds of times every day, and companies can deliver features, fixes and updates in rapid fashion. Within an agile DevOps setting, Continuous Integration (CI), Continuous Delivery and Continuous Deployment (CD) have become established practices.


How Grafana Labs Effectively Pairs Loki and Kubernetes Events

As we’ve rolled out Loki internally at Grafana Labs, we wanted logs beyond just simple applications. Specifically while debugging outages due to config, Kubernetes, or node restarts, we’ve found Kubernetes events to be super useful. The Kubernetes events feature allows you to see all of the changes in a cluster, and you can get a simple overview by just retrieving them: This also captures when nodes go unresponsive and when a pod has been killed along with the reason.