![]() ![]() The email has a link in it to an asset on the website, and they’re going to track how many customers click that link as well as who they are using a marketing automation tool.īut what if the downloadable asset suddenly disappears for an unexpected reason halfway through sending the email to the database? The sales team is about to send out a sales email to 2,000 existing customers inviting them to sign up for a new service based on their current preferences. ![]() I want to ensure the website is serving the correct content, so my targeted mailings don’t go unanswered. I want to understand page load times, so I can ensure our content is optimised appropriately.īoth image optimisation and compression of assets are known to be reasons for long page load times and, with access to the monitoring dashboards, your marketing teams can look at the way they generate media for the site and find the levels of compression/quality loss that are acceptable. I want to know how my application is performing, so I can prioritise the backlog more effectively.Īpplication performance can help product owners, tech-leads, scrum facilitators, and agile coaches move stories around the backlog to prioritise performance enhancements alongside new features. This is a story about a process we’re all familiar with-we check the data, then we refactor and see if the data improves-however, when was the last time you wrote it down as a user story on the backlog? 2. I want to see how my application is performing, so I can refactor the appropriate parts of the codebase to improve user experience. Let’s take a look at what the change would be within your organisation’s approach to monitoring if you started to add in the following stories. Stories such as “As a user, I want to be able to add an item to my basket, so I can buy it” are not uncommon, but what about the internal requirements for our team and those around us within our own organisation that fall outside the “end-user” customer? Often in engineering, we focus our development stories on the user interaction. Why You Should Build Monitoring into Everything You Do While monitoring has previously focused on API and website response times-or system metrics such as CPU, RAM, and disk space-observability takes a more holistic approach to system health and often includes user experience and business processes, in addition to more traditional monitoring measurements.Īs the world moves towards an SRE approach to systems development and deployment, it is vital that we start moving away from asking if a service is “up or down” and towards proving that service is providing value to our customers, the business, and our engineering teams.Īt Contino, we expand observability outside the cloud environment or data centre and into your business by monitoring not just your application and platform, but also how your business, developer teams and even revenue streams are performing-to give you a complete picture of your organisation from feature request through to customer satisfaction. When we talk about observability, we mean taking an approach to monitoring where the platform or product being monitored is a “black box”-and the only way to understand what it is doing inside is to observe the outputs. ![]() Observability is the logical next step from traditional monitoring practices, and a core tenet of the Site Reliability Engineering (SRE) movement. An observable system is one where you can infer its internal state purely from the system's outputs-and one that is operable at the speed demanded by modern digital transformations.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |