Operations | Monitoring | ITSM | DevOps | Cloud

Healthcare providers are under more pressure than ever to provide better care and improve patient outcomes despite clinical resource scarcity, high turnover, and burn-out. Staffing shortages of physicians and nurses, growing populations in need of care, and rising costs create real barriers to exceptional care.

From production monitoring to security concerns, businesses need to analyze and review their logs on a daily basis to make sure their system is up to par. Here are the reasons why analyzing your log data is so important. If you landed here, chances are you probably know what logs are, but we’ll start off with a short explanation of what it is.

You will have seen the Nastel Messaging Middleware Performance Benchmark Report comparing the performance of the commonly used messaging middleware platforms – IBM MQ, RabbitMQ, Apache Kafka, ActiveMQ Classic, ActiveMQ Artemis, TIBCO EMS, and Apache Pulsar. Nastel produced this using its CyBench performance benchmarking technology. StreamNative has also produced its own benchmark report focused on comparing Apache Pulsar vs. Apache Kafka using the Linux Foundation Open Messaging benchmark.

A couple of weeks ago, we had a great time hosting the workshop you can see below with Vlad Mihalcea. It was loads of fun and I hope to do this again soon! In this workshop we focused on Spring Boot performance but most importantly on Hibernate performance, which is a common issue in production environments. It’s especially hard to track since issues related to data are often hard to perceive when debugging locally.

Uptime monitoring. You keep hearing us talking about it and you know why it’s important, hey, you might even have a StatusCake account. But do you know what to do if you do experience website downtime? Let’s do a little quiz. Your website has suffered two hours of downtime. Do you: If you answered a, you might be a lost cause (I’m only joking, you should just definitely read to the end of this post), and if you answered d, crack out the sales bell and start dinging!

One of the most critical aspects of monitoring your digital assets is getting a timely alert when something goes wrong. Even when you finish building a monitoring stack and expose metrics on a beautifully designed dashboard if you cannot notice abnormal behaviors and fail to take pre-emptive or follow-up actions swiftly, this means your monitoring system does not serve the purpose.

Frontend technologies typically talk to several services in your backend, and those services talk to other services. At the root of every issue is a single event that causes a domino effect. A domino effect that impacts every operation from the first experience on the frontend to the backend API call. Sentry can show you how these exceptions and latency issues impact every one of your services. For example, take the ever common and seemingly simple to resolve 500 - Internal Server Error.

Preloads are a powerful optimization technique that can make significant improvements to crucial performance metrics such as Core Web Vitals. I have written on prefetching a DNS lookup or even preconnecting to a domain. Preloading is a much more powerful extension of these concepts because it enables you to download entire resources in advance. In this article, let’s look at.

Time series databases like InfluxDB are databases that specialize in handling time series data, which is data that is indexed by time. Unlike traditional databases, time series databases are optimized for reading and writing data with less performance consideration for updating or deleting data. Due to the time-dependent nature of time series data, time series databases are handy for application monitoring.