Operations | Monitoring | ITSM | DevOps | Cloud

On Wednesday 17th March, globally used DNS provider Network Solutions experienced the dreaded downtime we all hope to avoid. Starting at 4am Eastern time and continuing through to Thursday 18th with still no resolution, it’s affected thousands of people across the world. Network Solutions are the 4th biggest domain registrar in the world, with nearly 7 million users worldwide.

Imagine, you are developing Java software and suddenly you encounter an error? Where could you have possibly gone wrong? There are many types of errors that you will encounter while developing Java software, but most are avoidable. Some errors are minor lapses when writing codes but that is very much mendable. If you have an error monitoring tool such as Stackify Retrace, you can write codes with ease.

Microservices and serverless are both important topics in the world of cloud-native computing. Yet, although serverless functions and microservices architectures often go hand-in-hand, they’re distinct technologies that fill different roles in modern software environments. Here’s an overview of what microservices and serverless are, how they relate to each other, how they are different, and why you may or may not wish to deploy a serverless microservice.

With the volume, velocity, and variety of today’s data, we have all started to acknowledge that there is no one-size-fits-all database for all data needs. Instead, many companies shifted towards choosing the right data store for a specific use case or project. The distribution of data across different data stores brought the challenge of consolidating data for analytics.

"No one likes documentation", chirped the little blue birds. The bird quotes in the image above are all taken from real tweets and are listed below for accessibility: I can't argue with "liking to write documentation" being a rare skill, since so many people are vocal about disliking it. That tweet might prove to be true, in which case, technical writers should simply be more appreciated for the rare gems that they are. In this blog post, however, I’m going to explain.

More than once, I’ve heard experienced software developers say that there are only two reasons to log: either you log Information or you log an Error. The implication here is that either you want to record something that happened or you want to be able to react to something that went wrong. In this article, we’ll take a closer look at logging and explore the fact that log levels are more than just black or red rows in your main logging system.

Monitoring has always been a crucial operation in a software development cycle. This is mainly because of the complexity of industry-level IT and consumer-facing product development. Additionally, there is an ever-growing demand for rapid upgrades in products. To meet these requirements, streamlined performance and stability have become more important than ever; and without effective monitoring practices, they appear difficult to achieve.

Windows event logs are important for security, troubleshooting, and compliance. When you analyze your logs, you can monitor and report on file access, network connections, unauthorized activity, error messages, and unusual network and system behavior. However, Windows servers produce tens of thousands of log entries every day.

In a previous post I explained how to send metrics to Logz.io Infrastructure monitoring with Prometheus—now let’s analyze them by building Prometheus dashboards and visualizations in our metrics UI! Once you’ve started to send metric data to Logz.io, how do you visualize and interpret that data so that it’s useful for you? Logz.io Infrastructure Monitoring provides powerful querying and visualization of your data.

We recently launched the public preview of a new tool that lets anyone dashboard anything – for free. Meet Dashboard Server! You can download it free because we wanted to get our incredible dashboards in the hands of more people. The SCOM community know us well but our dashboards are perfect for so many use cases beyond System Center monitoring. And if you love them as much as we think you will, all we ask in return is that you share that love by spreading the word.