Operations | Monitoring | ITSM | DevOps | Cloud

3 ways telecommunications companies can improve the customer experience

The COVID-19 pandemic brought connectivity to the forefront, as companies quickly shifted to remote working. As the new world of hybrid work emerges, connectivity continues to be at the center of conversations, putting pressure on telecommunications companies to deliver. At the same time, customers are demanding a better user experience with more consistent, high-quality service, shorter wait times, and personalized interactions.

Announcing Support for AWS Lambda Functions running on AWS Graviton2 processors

AWS Graviton2 processors use the Arm architecture to provide high-efficiency, low-cost computing. AWS already offers the ability to provision EC2 instances powered by Graviton2, and Datadog is proud to partner with them for the launch of new Graviton2 compute resources for Lambda functions. In this post, we’ll discuss how Datadog can provide deep visibility into your Lambda functions across whichever platform you’re using.

What is OpenTelemetry: A guide to understanding OpenTelemetry and the way forward

OpenTelemetry is a vendor-neutral approach that enables DevOps and developers to collect performance metrics in a standardized manner. Currently a Cloud Native Computing Foundation (CNCF) sandbox project, OpenTelemetry was conceived by merging OpenCensus, Google's open-source method of collecting metrics and traces, and OpenTracing, a vendor-neutral API to collect traces.

Log Observability and Log Analytics

Logs play a key role in understanding your system’s performance and health. Good logging practice is also vital to power an observability platform across your system. Monitoring, in general, involves the collection and analysis of logs and other system metrics. Log analysis involves deriving insights from logs, which then feeds into observability. Observability, as we’ve said before, is really the gold standard for knowing everything about your system.

New Feature: Slug URLs

Healthchecks.io pinging API has always been based on UUIDs. Each Check in the system has its own unique and immutable UUID. To signal a start, a failure, or a particular exit status, clients can add more bits after the UUID: This is conceptually simple and has worked quite well. It requires no additional authentication. The UUID value is the authentication, and the UUID “address space” is so vast nobody is going to find valid ping URLs by random guessing any time soon.

The Way We Work: N-able's hybrid work model

We’ve all seen the headlines. It’s no secret companies are being forced to re-examine the employee experience and what the future of work will look like in a post-pandemic world. With the adaptation to remote work, the pandemic created a new normal—where office and home life are blended, and people became accustomed to more flexibility. Now that flexibility is a benefit people don’t want to lose.

Let's Encrypt DST Root CA X3 certificate set to expire

If you've been using Let's Encrypt for a while, you may have noticed that their certificates are signed by a root certificate titled DST Root CA X3. That root certificate is set to expire in a few hours. Any certificates still signed by that root will no longer be valid. But luckily, that shouldn't form a problem for most Let's Encrypt users. For a while now, new SSL issuances by Let's Encrypt have issued certificates against DST Root CA X3 (the one that is about to expire) and ISRG Root X1.