Operations | Monitoring | ITSM | DevOps | Cloud

Software development and delivery requires cross-team collaboration and cross-service orchestration—all while ensuring that organizational standards for quality, security, and compliance are consistently met. Without careful monitoring, you risk a lack of visibility into delivery workflows, making it difficult to evaluate how they impact release velocity and stability, developer experience, and application performance.

At GrafanaCON last month, we announced Grafana Alloy, our open source distribution of the OpenTelemetry Collector. Alloy is a telemetry collector that is 100% OTLP compatible and offers native pipelines for OpenTelemetry and Prometheus telemetry formats, supporting metrics, logs, traces, and profiles. Today, we are excited to share that Grafana Beyla is now available in Grafana Alloy as the default eBPF-based application auto-instrumentation solution.

I was just asked how to troubleshoot an HTTP Error 500.19 - Internal Server Error when trying to launch an ASP.NET Core website on IIS. I have seen this error too many times for both ASP.NET and ASP.NET Core so decided to write a blog post about at least one, obvious, fix. The problem happens when deploying the ASP.NET or ASP.NET Core website to IIS and getting the following error message in the browser.

We're excited to kick off our first-ever Spotlight Week, a week-long celebration of innovation and progress at Spectate! Each day, we'll be shining a spotlight on new features, updates, and announcements that showcase our commitment to making monitoring and incident management easier and more efficient.

In today’s hybrid IT environments, alert storms feel like a commonplace ocurrence. While serving their purpose of notifying ITOps teams of potentially urgent business-impacting issues, they can also create stress and fatigue as teams engage in what can feel like an endless fire drill, constantly switching between siloed monitoring tools to identify and resolve the root cause of software incidents.