The latest News and Information on Monitoring for Websites, Applications, APIs, Infrastructure, and other technologies.
Purchase decisions often begin with a price check. Log management is no different. Evaluate your budget and narrow down the options that fit to choose the tool that gives you the most for what you pay. As always, cheaper is better as long as the platform doesn’t cut any corners. But with log management, there is a catch – not all tools are transparent with their pricing model.
In this article you’ll find out how to 10x your development speed with local serverless debugging. Questions such as “what happens when you scale your application into millions of requests?”, “what to expect when going serverless?”, “how does it look like?”, or “how is it to build applications on serverless and work locally?” will be addressed.
Have you ever tried to search for a leadership position in IT that’s dedicated exclusively to employee experience, sometimes listed as end user experience or Digital Employee Experience (DEX)? I’m not talking about a CXO (Chief Experience Officer) role outside of IT—that position is usually advertised for customer experience or employee communications and human resources. I’m talking strictly enterprise IT.
Log centralization is kind of like brushing your teeth: everyone tells you to do it. But until you step back and think about it, you might not appreciate why doing it is so important. If you’ve ever wondered why, exactly, teams benefit from centralized logging and analysis, keep reading. This article walks through five key advantages of log centralization for IT teams and the businesses they support.
Monitoring solutions are a vital component in managing an application’s environment. From the systems layer all the way up to the end user’s connection to the app, you want to find out how the platform is performing. Indicators like CPU, memory, the number of connections, and overall health help teams make informed decisions for guaranteeing uptime. Teams monitor metrics (short-term information) and logs (long-term information) mainly from a reactive perspective.
Site Reliability Engineering (SRE) and Operations (Ops) teams heavily rely on notifications. We use them to know what’s going on with application workloads and how applications are performing. Notifications are critical to ensuring SREs and Ops teams can resolve errors and reduce downtime. They’re also crucial when monitoring environments — not only when running in production but also during the dev-test or staging phase.
I recently spoke to the IT Director and Head of End User Computing at a leading healthcare company who implemented Salesforce globally across their entire employee user base 9 months ago (before later becoming a Nexthink customer). She told me their Salesforce licensing model was similar to others you’ll see in market: a set of base licenses and then selected add-ons based on employee roles – with some at no charge and others priced ala carte. Her problem? License metering.
What do Google’s DevOps Research and Assessment (DORA) and Rollbar have to do with each other? DORA identified four key metrics to measure DevOps performance and identified four levels of DevOps performance from Low to Elite. One way for a team to become an Elite DevOps performer is by focusing on Continuous Code Improvement.
