Operations | Monitoring | ITSM | DevOps | Cloud

To gain adequate visibility into your distributed applications, you need to observe those applications at different levels of granularity. This means that you need to be able to query collected telemetry data both at the level of the whole application and at the level of selected components. Thanks to the power of Datadog tagging, you can already do this by aggregating your metrics within any scope of your choosing.

By Sara Miteva Sr. Product Marketing Manager, Checkly ‍ Modern applications are complex. Microservices, third-party dependencies, and continuous deployments all contribute to a flood of telemetry data—logs, metrics, traces—flying in from every direction.

Grafana Alerting has evolved dramatically since the legacy dashboard-alert days. Today, Grafana-managed alerts power enterprise-scale monitoring in Grafana Cloud and on-prem installations. And over the last two years, we’ve added RBAC, state history, versioning, and much more. At the same time, our own monitoring at Grafana Labs relies heavily on Prometheus-style alerts—a situation that’s not uncommon for our users, too.

The internal DevOps team at JFrog needed to provision cloud resources, create environments, and manage infrastructure for our developers. Unfortunately, it involved wasting a significant amount of time on repetitive tasks, that was slowing down the pace of innovation and taking away our developers’ focus from building new features and industry leading products.

This is a guest post from Armin Ulrich, a fullstack developer, and founder of placid.app. He also created the MadeWith* network where he shares his projects and allows other developers to share theirs. There are many things I would rather do at 9pm than tracking down a mission-critical bug, but sometimes you don’t have a choice. Let me tell you the story about a slow query that led to a cascading failure–and how it could have been worse.

With over 50 built-in integrations, Cortex customers have an always-up-to-date, single interface for their engineering priorities, tools, and tasks. But large organizations have a lot of tools. And if you're running internally hosted tools, or for policy or security reasons would prefer to keep your access tokens private, that used to limit what was possible in your internal developer. Not anymore.

Today marks an exciting milestone not just for Cortex, but for every organization looking to foster a culture of engineering excellence. Knowing who owns what is one of the hardest and most important challenges for engineering teams. Without clear ownership, incidents take longer to resolve, migrations stall, and enforcing standards becomes nearly impossible.

Today we’re thrilled to announce the launch of Entity Relationships, a powerful new capability that gives you more flexibility and control over the data model in your IDP. By allowing you to create custom relationships between entities in your catalog, you can model your internal developer portal to accurately reflect your own organization’s taxonomy, letting you better answer deep questions about your environments, releases, packages, and beyond.