Operations | Monitoring | ITSM | DevOps | Cloud

One of the unique features of Oh Dear is that we crawl your entire site and report any broken links. Our broken links report had two main categories: In both categories, the problem is caused by something related to the site's content. In most cases, a page you're linking to was removed or archived. The solution is often letting the content manager of the site fix this. Today, we're introducing a third category in our report: internal broken links that resulted in a 5xx status code.

Within enterprises, it used to be that applications ran on a single server. Owners could directly monitor that discrete machine, conveniently access all the logs they needed, see all the metrics that mattered, and hit the reboot button, without needing to confer with “everyone.” Those days are gone. Modern application architectures stretch the definitions of the words “federated” and “distributed.” We now have distributed applications.

As developers, we all seek to build web applications that can scale seamlessly, adapt to changing needs and do so without incurring excessive costs. One way to achieve this is by migrating web applications to AWS Lambda, which can provide scalability, flexibility, and cost savings. To make this process even easier, AWS provides the Lambda web adapter, a simple and efficient tool that enables you to migrate your web apps quickly.

Contrary to Betteridge’s Law of Tabloid Headlines, the answer to the question, "does OpenTelemetry in.NET cause performance degradation?" is yes, but context is important. I get this question so often that I thought it was time to get some stats on it. I’ve heard comments like: I can only assume that these are based on previous versions, or things like OpenTracing / OpenCensus (the heritage frameworks that were the feeders for OpenTelemetry).

Businesses are generating vast amounts of data from various sources, including applications, servers, and networks. As the volume and complexity of this data continue to grow, it becomes increasingly challenging to manage and analyze it effectively. Centralized logging is a powerful solution to this problem, providing a single, unified location for collecting, storing, and analyzing log data from across an organization’s IT infrastructure.

Grafana Alerting enables users to create and customize alert rules as separate entities and link them to Grafana panels. It also supports various data sources with built-in alerting engines, such as Prometheus, Grafana Mimir, and Grafana Loki, allowing users to manage their alert rules directly from Grafana’s UI.

There are several reasons you may want to route to Amazon S3 destinations, including routing to object storage for archival, routing to S3 buckets to utilize Cribl.Cloud’s Search feature, and archiving data that can be replayed later. When setting up Amazon S3 destinations in Cribl, there are three authentication methods: Auto, Manual, and Secret. Using the Auto authentication method paired with Assume Role is the most secure way to connect Amazon S3 to Cribl.

Since its initial conception on the back of a napkin, BGP has been an essential part of the Internet. However, its ubiquity and simplicity also make it a potential weak spot in any organization's Internet Stack. As an open, near-universal protocol it's a vector for potentially malicious attacks. It can also cause the same amount of problems simply through misconfiguration (in fact telling the difference between the two can be a challenge in and of itself).

In today’s business landscape, predictive maintenance has emerged as a critical strategy to optimize equipment performance, reduce downtime, and minimize maintenance costs. In this article you will learn about some tools that can be used to simplify the complexity involved with implementing a successful predictive maintenance program.