Over the last few days, most of us have been getting to grips with this new, albeit temporary, norm of remote working. At SquaredUp, we’ve always been able to work like this as all of the tools we use day-to-day are SaaS products or hosted in Azure, but while we’ve always had the right tools, we’ve never actually had to experience everyone being out of the office at the same time.
AWS S3 buckets are an indisputably powerful—and extremely well-organized—DevOps tool. Standing for “simple storage service,” the S3 is the lowest tier offered for AWS storage, but it is also the most indispensable. S3 buckets store data for immediate recall, the most active components in Amazon’s arsenal of storage options. They can store a variety of developer applications and up to five terabytes of data each.
One of the challenges introduced by microservices architectures is the ability to understand how the application performs and where most time is spent. The Elastic Stack and Elastic APM can provide observability for modern, microservice-based solutions as well as monolithic applications. Application Performance Monitoring (APM) combines different technologies to provide a deep, transparent and holistic view of what each service component is doing, where, when, and for how long.
Application performance monitoring (APM) is a critical part of a unified observability strategy. APM offers deep insights into application performance and behavior, and organizations depend on it to deliver performant and high-quality digital experiences to their customers — both for keeping a proactive pulse on the health of their applications and for troubleshooting issues.
No matter how careful developers are or how comprehensive tests are applied before deployment, there will always be some level of issues to deal with in production. When it comes to managing issues and ensuring application quality, two main metrics should be on our radar: time to discover and time to resolve issues.
The reasons to move to Kubernetes are many and compelling. This post doesn’t make the case that you should migrate, but assumes you have already decided that you want to. When you’re clear on what you want to do and why you want to do it, the questions of “When?” and “How?” become your focus. What follows centers on the question of how to approach making Kubernetes the platform on which your workloads thrive.
It’s easy to see the value of sensor data that enables acting in time. Just picture driving as the scene of a massive traffic accident unfolds and ambulances race to the rescue…what a difference a few seconds can make. What if past traffic patterns could help city operators predict and manage traffic flow at critical times?
In my last post I walked through a brief introduction to Application Insights, and APM tools in general, and hopefully the simple outside-in availability test I concluded the chapter with has been a useful starting point for you on your APM journey. In this post, I’m going to dig deeper into Application Insights and walk you through a use case that should make the purpose of Application Insights really clear.
The Oracle Weblogic Scripting Tool (WLST) is stand for monitoring, managing, and configuring Oracle WebLogic Server from the command line. While monitoring WebLogic domains mostly administrators prefer to use WLST (WebLogic Scripting Tool) scripts but there are more efficient and robust way available to monitor WebLogic domain resources like health status and states of servers (JVMs), deployments, data sources and JMS resources etc.
With all the buzz surrounding user experience these days, I thought it might be worthwhile to start “at 50,000 feet” and dissect user experience into its component parts and see what all the fuss is about. User experience (UX) is somewhat different than customer experience (CX). Customer experience has been defined as the quality of all a consumer’s encounters with a company’s products, services, and brand. Today, user experience typically refers to the digital user experience.
