Azure Functions is Microsoft’s solution to serverless computing. While it actually does run on servers, the key difference here is that you aren’t responsible for maintaining the function hosting environment. This is both a blessing and a curse.

Where does your company want to be in one year? Five years? Ten years? And what does this growth mean for your technology stack? These questions play on repeat for any growing organization.

A record high of 162,414 cars per day cross the Golden Gate bridge, in wind, rain, and countless other environmental factors (don’t say earthquakes!) that compound stress on it. An Atlassian instance is a lot like a bridge. Users access each instance hundreds and thousands of times a day, amid conditions that include the size of the instance itself (with its load of comments, pages, repos, etc.), the apps you’ve added, API calls, and much more.

One of my biggest issues with the display of performance data in digital experience monitoring is using the “average” as the main value. Averages are of course useful in certain scenarios but when it comes to real user interactions on your website, averages are really unreliable.

It’s February, which means it’s the perfect time for us to publish our 2018 year in review. Other organizations publish these in January or even December, and they are wrong to do so. February is the best month for this, except for those years when we publish it in March. 2016 was a big year for us. 2017 was even bigger. You know what that means: 2018 was the biggest yet. How big was it?

In a previous article, we explained the importance of monitoring the performance of your servers. Keeping tabs on metrics such as CPU, memory, disk usage, uptime, network traffic and swap usage will help you gauge the general health of your environment as well as provide the context you need to troubleshoot and solve production issues.

In a separate article, we introduced the concept of performing synthetic transactions with LogicMonitor to ensure website services are up and running correctly. It may be necessary to authenticate with a website before you can fully monitor it, and authentication may require presenting an MFA code that has been delivered via email. Let’s take this a step further and incorporate an MFA (Multifactor Authentication) Challenge.

Today at Think 2019 we’re announcing our intent to work with IBM to support the Sysdig Cloud-Native Intelligence Platform on IBM Cloud Private and IBM Multicloud Manager. By supporting IBM Multicloud Manager and IBM Cloud Private, Sysdig will help IBM customers accelerate the transition to cloud architectures.