Operations | Monitoring | ITSM | DevOps | Cloud

Has this ever happened in your weekly stand-up? ‍

In today’s world, a significant fraction of a software business’s reputation depends on its web application and its speed. It all comes down to how fast your server responds to client requests (assuming your application is reliable and reasonably user-friendly). Therefore, you could argue that the server endpoint is the centerpoint of all the server-side action — the operations here primarily determine the performance of your application.

Migrating to a cloud-based phone system is compelling because it eliminates the costs and time associated with deploying and managing legacy phone system/PBX hardware and proprietary business phones. However, moving 100% of an organization’s communications infrastructure off-site can present new challenges. If the connection to the cloud is lost, a site could lose both external communications and intra-site communications.

In the early years of the internet, it was common to simply use a spreadsheet to manually assign and track IP addresses. We’d be given a generous pool of IP addresses that were not so widely distributed, and most network devices were desktops and not mobile. But this soon got out of hand as networks grew and mobile devices became the norm.

One of the critical differences between distributed tracing and business activity monitoring is that distributed tracing usually assumes that your transaction executes from start to end in a reasonably short time. An example would be that your call to an API might then drop a message on a queue which a function processes and loads into a database.