In this post we will cover some of the main use cases FluentD supports and provide example FluentD configurations for the different cases.

CIOs and other IT leaders know the importance of having a well-oiled machine to support the vast requirements of the business. Not having a Google-like experience of an always-up, always-fast, easy to use technology ecosystem can be a competitive disadvantage. More pressing is that while most businesses want to reinvent, through digital transformation or other methods, these large-scale efforts fail 70% of the time.

It’s no secret that information threats appear in numbers nowadays. It may be time to refresh some typical rules, tested by years of practice worldwide, to make your monitoring setups as up-to-date as possible. None of these rules are cast in iron; they are all flexible enough to adapt to any given environment. What matters is underlying idea; the implementation is what makes them suitable for custom needs.

Do all your synthetic monitors include a content check? Why not? Content checks are free with all our monitor types, but for the most part, Uptrends users underutilize content checks. In this article, we talk about why content checks are important for your monitoring, and we touch on some tips to help you pick the content checks that work best for you.

Over 44 records are stolen per second every day due to data breaches, and according to the Risk Based Security Research report published in 2019, databases are the top most targeted assets for malicious actors to exploit organizations’ confidential data. Often, organizations don’t realize their databases have been compromised for months. Once sensitive data is leaked, the damage can’t be undone.

Every JavaScript project starts ambitiously, trying not to use too many NPM packages along the way. Even with a lot of effort on our side, packages eventually start piling up. package.json gets more lines over time, and package-lock.json makes pull requests look scary with the number of additions or deletions when dependencies are added. “This is fine” — the team lead says, as other team members nod in agreement. What else are you supposed to do?

Now that we’ve talked a lot about how to monitor your Azure resources, let’s talk about how to monitor Azure itself. As the classic statement goes, “there is no cloud – it’s just someone else’s computer” – and all computers can go down. Even Microsoft’s. So how do you know when poor availability or performance of your resources is actually a result of Azure itself being sick?