Operations | Monitoring | ITSM | DevOps | Cloud

We’re living history. We’ve heard it uttered in everything from news reports to conversations with loved ones. And it’s true — the tragedy and uncertainty of COVID-19 is shaping history and policy as we know it. But there’s something else newsworthy, too. Amid the pandemic, we’ve seen beacons of hope, humanity and progress. People have banded together to solve monumental problems at record pace.

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.

Nishant Singh is an SRE at LinkedIn based in Bangalore. Currently, he is working towards building and maintaining applications that improve the overall MTTD (Mean time to detect) and MTTR (Mean time to recover) of the site. He likes to build services and play with the latest technologies. Before LinkedIn, Nishant worked for a few companies in the security and e-commerce domain as a DevOps engineer where he was primarily responsible for building infrastructure, deployment pipelines and security.

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?

When monitoring third-party applications with Prometheus, you’ll need an exporter if the application doesn’t already expose metrics in the appropriate format. How do you find an appropriate exporter, and once you have your exporters, how should you organize your label taxonomies to reflect your infrastructure? Many applications in the systems you’re in charge of will be third-party applications, which do not natively expose Prometheus-formatted metrics.