Operations | Monitoring | ITSM | DevOps | Cloud

Today, we made an important announcement that builds on and extends our category leadership in Continuous Intelligence. This blog is to put that announcement into context for our customers, partners and the broader industry. In 2017, we shared our strategy to democratize machine data by building a cloud-native, Continuous Intelligence Platform™ to 1) unify modern application and machine data; 2) support the ongoing proliferation of users and access; and 3) leverage cloud-scale economics.

As more and more applications move to the cloud, the complexity of application architectures inevitably increases. It is a burden we willingly take on because the benefits—flexible deployment, technology diversity, independent scaling, and much more— tend to far outweigh the costs. But along this transition, most organizations face a dilemma, to divert resources to the necessary tooling for effective monitoring and troubleshooting of these systems – i.e.

Isn’t all logging pretty much the same? Logs appear by default, like magic, without any further intervention by teams other than simply starting a system… right? While logging may seem like simple magic, there’s a lot to consider. Logs don’t just automatically appear for all levels of your architecture, and any logs that do automatically appear probably don’t have all of the details that you need to successfully understand what a system is doing.

As the world moves towards the “new normal” on account of the pandemic, numerous adjustments and recalibrations have been made in all aspects of our lives, including the organizations we are part of. As businesses base their operations on a dispersed workforce beyond the corporate perimeter, IT teams have been the ones largely enabling this successful migration to home workspaces and further sustaining the remote network to foster productivity.

You hear about APIs (application program interfaces) everywhere now, and even if you don’t know what one is, you’ve probably heard the term more than once. In this article, we cover a few API basics, and we talk a bit about why you should use API monitoring if you publish or have an API that is critical to your business.

Our sources state that there has been a 20% increase in web-skimming attacks since the outbreak of the COVID-19 virus. Recently, we have witnessed some high-profile Magecart attacks on websites which have gained popularity during the pandemic, including fitness-based websites. The latest fitness-based website attack reported is YogaFit, who were compromised for over 6 weeks.

When it comes to troubleshooting application performance, metrics are no longer enough. To fully understand the environment you need logs and traces. Today, we’re going to focus on your Java applications.

You know the feeling. You’ve just deployed a new version to production and are monitoring the Rollbar dashboard for any new errors or looking out for any Slack notifications. You’re keeping an eye on the number of new or reactivated errors, their severity level, and triaging to see which errors need to be assigned and to whom. Now what if you could automate these tasks?