# Ground Cover

Level up your K8s observability game with eBPF

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Opening groundcover on Duo and looking at our own mobile RUM

DevFeed: [Opening groundcover on Duo and looking at our own mobile RUM](<https://devfeed.tech/articles/opening-groundcover-on-duo-and-looking-at-our-own-mobile-rum-141939.md>)

Original publisher: [Read original article](<https://www.groundcover.com/blog/opening-groundcover-on-duo-and-looking-at-our-own-mobile-rum>)

Author: Anais Dotis

Published: 2026-11-18T10:05:00Z

Content type: article

Language: en

Sources: [Ground Cover](<https://devfeed.tech/sources/ground-cover.md>)

Topics: [real user monitoring](<https://devfeed.tech/topics/real-user-monitoring.md>), [Mobile](<https://devfeed.tech/topics/mobile.md>), [mobile-app-development](<https://devfeed.tech/topics/mobile-app-development.md>), [mobile optimization](<https://devfeed.tech/topics/mobile-optimization.md>), [mobile-ui-design](<https://devfeed.tech/topics/mobile-ui-design.md>), [dogfooding](<https://devfeed.tech/topics/dogfooding.md>), [Mobile Testing](<https://devfeed.tech/topics/mobile-testing.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [Android](<https://devfeed.tech/topics/android.md>), [Linear](<https://devfeed.tech/topics/linear.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-observability](<https://devfeed.tech/tags/ai-observability.md>), [android](<https://devfeed.tech/tags/android.md>), [apple-store](<https://devfeed.tech/tags/apple-store.md>), [checkout](<https://devfeed.tech/tags/checkout.md>), [codex](<https://devfeed.tech/tags/codex.md>), [coding-agent](<https://devfeed.tech/tags/coding-agent.md>), [crashes](<https://devfeed.tech/tags/crashes.md>), [customer](<https://devfeed.tech/tags/customer.md>), [duo](<https://devfeed.tech/tags/duo.md>), [evals](<https://devfeed.tech/tags/evals.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [groundcover](<https://devfeed.tech/tags/groundcover.md>), [hermes](<https://devfeed.tech/tags/hermes.md>), [infrastructure-monitoring](<https://devfeed.tech/tags/infrastructure-monitoring.md>), [investigation](<https://devfeed.tech/tags/investigation.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [rum](<https://devfeed.tech/tags/rum.md>)

### AI overview

groundcover's mobile RUM links real user sessions to backend traces: the React Native SDK captures screens, taps, logs and network calls, while Exceptions records crashes, ANRs and hangs and Vitals tracks slow or frozen frames and app starts per screen. The article says the Flutter package is a release candidate with the same signals and UI. The team also describes using its React Native SDK in its own apps, where it found and fixed missing Hermes stack frames and dropped native crash traces. Separately, testing groundcover on an iPhone Duo revealed a small-screen usability issue: the team pinned key sidebar controls and collapsed "over time" charts on screens 650px tall or shorter, remembering when users reopen them.

### Source excerpt

A customer's experience with groundcover mobile RUM on Duo

## Utilization shows how busy a node is. PSI shows which workloads are waiting.

DevFeed: [Utilization shows how busy a node is. PSI shows which workloads are waiting.](<https://devfeed.tech/articles/utilization-shows-how-busy-a-node-is-psi-shows-which-workloads-are-waiting-141940.md>)

Original publisher: [Read original article](<https://www.groundcover.com/blog/utilization-shows-how-busy-a-node-is-psi-shows-which-workloads-are-waiting>)

Author: Anais Dotis

Published: 2026-11-18T10:03:00Z

Content type: article

Language: en

Sources: [Ground Cover](<https://devfeed.tech/sources/ground-cover.md>)

Topics: [cgroups](<https://devfeed.tech/topics/cgroups.md>), [scheduling](<https://devfeed.tech/topics/scheduling.md>), [cloud service outage management](<https://devfeed.tech/topics/cloud-service-outage-management.md>)

Tags: [aws-fargate](<https://devfeed.tech/tags/aws-fargate.md>), [byoc](<https://devfeed.tech/tags/byoc.md>), [cgroup-v2](<https://devfeed.tech/tags/cgroup-v2.md>), [checkout](<https://devfeed.tech/tags/checkout.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [delay](<https://devfeed.tech/tags/delay.md>), [ebpf](<https://devfeed.tech/tags/ebpf.md>), [i-o](<https://devfeed.tech/tags/i-o.md>), [kubelet](<https://devfeed.tech/tags/kubelet.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-1-36](<https://devfeed.tech/tags/kubernetes-1-36.md>), [latency](<https://devfeed.tech/tags/latency.md>), [memory](<https://devfeed.tech/tags/memory.md>), [node](<https://devfeed.tech/tags/node.md>), [waiting](<https://devfeed.tech/tags/waiting.md>)

### AI overview

PSI measures time workloads stall while waiting for CPU, memory, or I/O, revealing contention that utilization averages can miss. It reports "some" (at least one task stalled) and "full" (all non-idle tasks stalled) over 10-, 60-, and 300-second windows and as cumulative stall time. Kubernetes 1.36 exposes PSI at node, Pod, and container levels through the Summary API and `/metrics/cadvisor`; it requires Linux kernel 4.20+, cgroup v2, and kernel PSI enabled, and is unavailable on Windows. Kubernetes exposes the signal for monitoring but does not use it for scheduling, autoscaling, or eviction decisions. PSI can identify a stalled workload but not the cause, so interpreting it requires time-aligned usage data from neighboring workloads. The text says groundcover does not yet collect PSI or use it in Autonomous Infrastructure; both are described as roadmap work.

### Source excerpt

CPU or memory usage data does not show whether any workload is delayed because it cannot get CPU, memory or I/O when it needs it, and that delay is what users experience as latency and failed requests. Pressure Stall Information (PSI) measures the delay directly, and as of Kubernetes 1.36 the kubelet exposes it as a stable feature.

## Your CPU limits aren't stopping noisy neighbors

DevFeed: [Your CPU limits aren't stopping noisy neighbors](<https://devfeed.tech/articles/your-cpu-limits-aren-t-stopping-noisy-neighbors-141936.md>)

Original publisher: [Read original article](<https://www.groundcover.com/blog/cpu-limits-arent-stopping-noisy-neighbors>)

Author: Anais Dotis

Published: 2026-11-18T10:00:00Z

Content type: article

Language: en

Sources: [Ground Cover](<https://devfeed.tech/sources/ground-cover.md>)

Topics: [cgroups](<https://devfeed.tech/topics/cgroups.md>), [scheduling](<https://devfeed.tech/topics/scheduling.md>), [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [Performance Testing](<https://devfeed.tech/topics/performance-testing.md>)

Tags: [autonomous](<https://devfeed.tech/tags/autonomous.md>), [autonomous-infrastructure](<https://devfeed.tech/tags/autonomous-infrastructure.md>), [bin-packing](<https://devfeed.tech/tags/bin-packing.md>), [byoc](<https://devfeed.tech/tags/byoc.md>), [cfs](<https://devfeed.tech/tags/cfs.md>), [cgroup](<https://devfeed.tech/tags/cgroup.md>), [cgroups](<https://devfeed.tech/tags/cgroups.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [combined](<https://devfeed.tech/tags/combined.md>), [congestion-control](<https://devfeed.tech/tags/congestion-control.md>), [container](<https://devfeed.tech/tags/container.md>), [containers](<https://devfeed.tech/tags/containers.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [cpu-time](<https://devfeed.tech/tags/cpu-time.md>), [groundcover](<https://devfeed.tech/tags/groundcover.md>), [latency](<https://devfeed.tech/tags/latency.md>), [limits](<https://devfeed.tech/tags/limits.md>), [memory](<https://devfeed.tech/tags/memory.md>), [nodes](<https://devfeed.tech/tags/nodes.md>), [oom](<https://devfeed.tech/tags/oom.md>)

### AI overview

Node-level contention explains why accurate per-workload sizing can still leave a cluster unstable: scheduling uses requests, while independently chosen P95 requests do not account for workloads peaking together. Under CPU contention, requests set proportional CPU weight; CPU limits impose quotas that can throttle a container even when other cores are idle. Memory has no proportional sharing: exceeding a limit can trigger an immediate OOM kill, while node pressure can lead to evictions or OOM kills. The post presents groundcover Autonomous Infrastructure as addressing this by using node-level CPU and memory history to identify overlapping peaks, adjust requests within operator-defined bounds, and apply changes to running Pods. It also says this requires high-resolution, per-container history linked to node and workload, and describes groundcover's eBPF sensor and BYOC storage as its collection approach.

### Source excerpt

This post explains what a noisy neighbor is, why CPU requests (not CPU limits) determine how CPU time is divided under contention, and why memory contention ends in OOM kills and evictions instead of added latency. It then explains why sizing each workload at a percentile of its own usage still overloads nodes, and how groundcover's Autonomous Infrastructure addresses that.

## How the groundcover team works now: Slack for people, Linear for agents

DevFeed: [How the groundcover team works now: Slack for people, Linear for agents](<https://devfeed.tech/articles/how-the-groundcover-team-works-now-slack-for-people-linear-for-agents-134508.md>)

Original publisher: [Read original article](<https://www.groundcover.com/blog/slack-for-people-linear-for-agents>)

Author: Anais Dotis

Published: 2026-11-15T10:03:00Z

Content type: article

Language: en

Sources: [Ground Cover](<https://devfeed.tech/sources/ground-cover.md>)

Topics: [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [Code review](<https://devfeed.tech/topics/code-review.md>), [human review](<https://devfeed.tech/topics/human-review.md>), [Linear](<https://devfeed.tech/topics/linear.md>), [Slack](<https://devfeed.tech/topics/slack.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-code-review](<https://devfeed.tech/tags/ai-code-review.md>), [apis](<https://devfeed.tech/tags/apis.md>), [audits](<https://devfeed.tech/tags/audits.md>), [automated-remediation](<https://devfeed.tech/tags/automated-remediation.md>), [autonomous-infrastructure](<https://devfeed.tech/tags/autonomous-infrastructure.md>), [ci-cd-pipelines](<https://devfeed.tech/tags/ci-cd-pipelines.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [groundcover](<https://devfeed.tech/tags/groundcover.md>), [investigations](<https://devfeed.tech/tags/investigations.md>), [linear](<https://devfeed.tech/tags/linear.md>), [root-cause-analysis](<https://devfeed.tech/tags/root-cause-analysis.md>), [slack](<https://devfeed.tech/tags/slack.md>)

### AI overview

The team uses agents to handle lookup, ticket upkeep, and first-pass code review so engineers can focus on design and judgment. Engineers discuss work in Slack; agents create and update Linear tickets from specs and answer questions by checking documentation. Most changes now go directly to pull requests, where reviewers assess both implementation and approach; line-by-line review remains for high-risk areas such as scale, data correctness, and customer-facing APIs. The team bounds retries, checks invariants before saving, keeps interfaces simple, maintains design documents, and rejects code likely to create technical debt. Agents can produce tests but do not yet choose what new information a feature should measure or how to present it. For remediation, groundcover proposes human-reviewed fixes first; teams may later opt into automation. Its existing infrastructure tool allows cluster-by-cluster adoption, logs changes, and can restore prior values. The planned CI/CD integration would compare pre-deploy signals with post-deploy data to flag regressions.

### Source excerpt

Building groundcover Investigations changed more than our product and how you can use groundcover to perform root cause analysis and roll out fixes. It also changed how the team building groundcover Investigations works day to day. Agents now handle much of the lookup work, the ticket updates and the first pass of code review. The engineers spend more of their time making decisions.

## How we built groundcover Investigations - getting agent swarms to follow the scientific method

DevFeed: [How we built groundcover Investigations - getting agent swarms to follow the scientific method](<https://devfeed.tech/articles/how-we-built-groundcover-investigations-getting-agent-swarms-to-follow-the-scientific-method-134506.md>)

Original publisher: [Read original article](<https://www.groundcover.com/blog/groundcover-investigations-using-the-scientific-method>)

Author: Anais Dotis

Published: 2026-11-15T10:02:00Z

Content type: article

Language: en

Sources: [Ground Cover](<https://devfeed.tech/sources/ground-cover.md>)

Topics: [agent to agent communication](<https://devfeed.tech/topics/agent-to-agent-communication.md>), [API Governance](<https://devfeed.tech/topics/api-governance.md>), [AI Context Management](<https://devfeed.tech/topics/ai-context-management.md>), [human review](<https://devfeed.tech/topics/human-review.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [all](<https://devfeed.tech/tags/all.md>), [can](<https://devfeed.tech/tags/can.md>), [claude](<https://devfeed.tech/tags/claude.md>), [codex](<https://devfeed.tech/tags/codex.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [conclusion](<https://devfeed.tech/tags/conclusion.md>), [contribute](<https://devfeed.tech/tags/contribute.md>), [engineers](<https://devfeed.tech/tags/engineers.md>), [follow](<https://devfeed.tech/tags/follow.md>), [full](<https://devfeed.tech/tags/full.md>), [groundcover](<https://devfeed.tech/tags/groundcover.md>), [hypothesis](<https://devfeed.tech/tags/hypothesis.md>), [incident](<https://devfeed.tech/tags/incident.md>), [investigation](<https://devfeed.tech/tags/investigation.md>), [investigations](<https://devfeed.tech/tags/investigations.md>), [issue](<https://devfeed.tech/tags/issue.md>), [keep](<https://devfeed.tech/tags/keep.md>)

### AI overview

groundcover Investigations coordinates engineers, groundcover agents, and outside coding agents through one shared investigation record. Its design separates an AI-free investigation service, which stores cases and enforces API rules, from an agent service that handles research and judgment. The guiding rule is to enforce invariants in code--such as one open case per monitor issue and proposal-based status changes--and leave hypothesis formation, telemetry selection, and evidence assessment to agents. Fixed schemas, scoped tools, and moderator review constrain proposals; event summaries help agents catch up, while Slack receives concise hypothesis assessments and the full detail remains in groundcover. The service split requires manual updates to agent tools when APIs change, and moderator strictness is tuned from engineers' reported examples because groundcover does not store customer data in its own backend. The current approach investigates top-down; a bottom-up evidence-and-correlation model is planned for testing.

### Source excerpt

An investigation starts from a question from the user, usually a firing monitor issue, and grows into a tree. Hypotheses are possible explanations, findings are the evidence, and assessments say whether the evidence supports or refutes each hypothesis. Engineers, groundcover's own agents and outside coding agents like Claude or Codex can all contribute to the same investigation. Two groundcover agents keep it running: the investigator researches the problem and publishes findings and assessments, while the moderator, an LLM-as-a-judge, accepts a conclusion only when the evidence supports it. Updates post to the incident's Slack thread, and the full investigation stays in groundcover.

## groundcover Investigations are a coworking space, not another AI SRE

DevFeed: [groundcover Investigations are a coworking space, not another AI SRE](<https://devfeed.tech/articles/groundcover-investigations-are-a-coworking-space-not-another-ai-sre-134505.md>)

Original publisher: [Read original article](<https://www.groundcover.com/blog/groundcover-investigations-as-a-coworking-space>)

Author: Anais Dotis

Published: 2026-11-15T10:01:00Z

Content type: opinion

Language: en

Sources: [Ground Cover](<https://devfeed.tech/sources/ground-cover.md>)

Topics: [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [human in the loop agent](<https://devfeed.tech/topics/human-in-the-loop-agent.md>), [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-investigation](<https://devfeed.tech/tags/agentic-investigation.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-sre](<https://devfeed.tech/tags/ai-sre.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [control-system](<https://devfeed.tech/tags/control-system.md>), [engineers](<https://devfeed.tech/tags/engineers.md>), [get-involved](<https://devfeed.tech/tags/get-involved.md>), [groundcover](<https://devfeed.tech/tags/groundcover.md>), [investigation](<https://devfeed.tech/tags/investigation.md>), [investigations](<https://devfeed.tech/tags/investigations.md>), [on-call](<https://devfeed.tech/tags/on-call.md>), [people](<https://devfeed.tech/tags/people.md>), [process](<https://devfeed.tech/tags/process.md>), [process-control](<https://devfeed.tech/tags/process-control.md>), [questions](<https://devfeed.tech/tags/questions.md>), [space](<https://devfeed.tech/tags/space.md>), [sre](<https://devfeed.tech/tags/sre.md>)

### AI overview

groundcover Investigations is designed as a shared workspace where its telemetry agents, engineers' coding agents, on-call staff and Slack contributions work against one attributed investigation tree. The investigator uses fault-tree-style questions and hypotheses, pursues multiple explanations, and can use past investigations; findings lead to participant assessments before hypotheses close. A separate LLM moderator checks proposed status changes against attached evidence, while only it can change statuses for agents; on-call engineers can act directly. Missing telemetry integrations are surfaced rather than guessed around. BYOC runs investigations in the customer's cloud, with model calls billed by the customer's LLM provider, which groundcover says lets agents explore more without per-token charges from groundcover. Automatic starts require admin opt-in and use the trigger creator's permissions, connectors and AI budget. The article says moderator strictness remains under experimentation.

### Source excerpt

An agentic investigation should feel like a process control system, and working with the agent should feel collaborative. Your coding agents, groundcover's agents, and the engineers on call all work in the same place, against the same records, and everyone can see everyone else's work. The groundcover investigator doesn't push you out of the loop while it quietly makes its fix. It's designed to pull you in. Investigations show you what every agent and sub-agent is checking, and that visibility invites people to get involved and ask questions.

## Introducing groundcover Investigations - collaboration ground for your agents and engineers

DevFeed: [Introducing groundcover Investigations - collaboration ground for your agents and engineers](<https://devfeed.tech/articles/introducing-groundcover-investigations-collaboration-ground-for-your-agents-and-engineers-134507.md>)

Original publisher: [Read original article](<https://www.groundcover.com/blog/introducing-groundcover-investigations>)

Author: Anais Dotis

Published: 2026-11-15T10:00:00Z

Content type: article

Language: en

Sources: [Ground Cover](<https://devfeed.tech/sources/ground-cover.md>)

Topics: [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [supervisor agent pattern](<https://devfeed.tech/topics/supervisor-agent-pattern.md>), [Slack](<https://devfeed.tech/topics/slack.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [about](<https://devfeed.tech/tags/about.md>), [added](<https://devfeed.tech/tags/added.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [alert](<https://devfeed.tech/tags/alert.md>), [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [assessment](<https://devfeed.tech/tags/assessment.md>), [away](<https://devfeed.tech/tags/away.md>), [branch](<https://devfeed.tech/tags/branch.md>), [but](<https://devfeed.tech/tags/but.md>), [call](<https://devfeed.tech/tags/call.md>), [can](<https://devfeed.tech/tags/can.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [engineers](<https://devfeed.tech/tags/engineers.md>), [faster](<https://devfeed.tech/tags/faster.md>), [groundcover](<https://devfeed.tech/tags/groundcover.md>), [incidents](<https://devfeed.tech/tags/incidents.md>), [investigations](<https://devfeed.tech/tags/investigations.md>)

### AI overview

groundcover Investigations gives engineers and agents one shared, structured record for incident work. Investigations organize hypotheses, telemetry findings, and assessments as supported, refuted, or open, so teams can see what has been checked, what remains unresolved, and what evidence supports conclusions. Its investigator researches issues and can query telemetry or split work into sub-investigations; a separate moderator checks whether findings support proposed conclusions, and only the moderator can resolve a hypothesis. Teams can also use their own agents through MCP, with contributions attributed to their source. Slack carries concise progress updates and accepts team input, while the full investigation tree, queries, and visualizations remain in groundcover. Investigations can currently start from a groundcover monitor issue or Slack; automatic starts when selected monitors fire are described as planned.

### Source excerpt

Meet groundcover Investigations, a shared workspace where engineers and AI agents collaborate, investigate incidents, validate evidence, and resolve issues faster.

## Observability Has Spent 20 Years Finding Problems. It's Time to Start Fixing Them.

DevFeed: [Observability Has Spent 20 Years Finding Problems. It's Time to Start Fixing Them.](<https://devfeed.tech/articles/observability-has-spent-20-years-finding-problems-it-s-time-to-start-fixing-them-116381.md>)

Original publisher: [Read original article](<https://www.groundcover.com/blog/observability-to-autonomous-infrastructure>)

Author: Shahar Azulay

Published: 2026-11-03T08:00:00Z

Content type: opinion

Language: en

Sources: [Ground Cover](<https://devfeed.tech/sources/ground-cover.md>)

Topics: [observability](<https://devfeed.tech/topics/observability.md>), [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>), [eBPF](<https://devfeed.tech/topics/ebpf.md>)

Tags: [ceo](<https://devfeed.tech/tags/ceo.md>), [groundcover](<https://devfeed.tech/tags/groundcover.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [observability](<https://devfeed.tech/tags/observability.md>), [problems](<https://devfeed.tech/tags/problems.md>)

### AI overview

groundcover Autonomous Infrastructure is a beta feature that uses production telemetry from groundcover's existing eBPF Kubernetes sensor to continuously adjust CPU and memory requests based on workload behavior. It can reduce over-allocation or increase requests within customer-defined boundaries, accounting for node fit and remaining capacity. Customers can inspect over- and under-provisioned workloads and estimated savings before enabling changes, then choose workloads, namespaces, or clusters to optimize. It is off by default; policy changes are tracked, and beta adjustments cover requests, not resource limits. The article says customers running the Kubernetes sensor can use the beta at no additional cost, with telemetry stored in their cloud through BYOC. Its stated aim is to connect observability to operational changes while keeping customers in control.

### Source excerpt

Observability has spent decades finding problems. groundcover CEO Shahar Azulay explains why it's time for infrastructure to start fixing them.

## Introducing Autonomous Infrastructure: Kubernetes Requests That Keep Themselves Right

DevFeed: [Introducing Autonomous Infrastructure: Kubernetes Requests That Keep Themselves Right](<https://devfeed.tech/articles/introducing-autonomous-infrastructure-kubernetes-requests-that-keep-themselves-right-116380.md>)

Original publisher: [Read original article](<https://www.groundcover.com/blog/introducing-autonomous-infra>)

Author: Shelby Salling

Published: 2026-11-03T08:00:00Z

Content type: release

Language: en

Sources: [Ground Cover](<https://devfeed.tech/sources/ground-cover.md>)

Topics: [Cloud Native Operations](<https://devfeed.tech/topics/cloud-native-operations.md>), [GitOps](<https://devfeed.tech/topics/gitops.md>), [linkerd](<https://devfeed.tech/topics/linkerd.md>)

Tags: [autonomous-infrastructure](<https://devfeed.tech/tags/autonomous-infrastructure.md>), [cost](<https://devfeed.tech/tags/cost.md>), [guardrails](<https://devfeed.tech/tags/guardrails.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>)

### AI overview

groundcover Autonomous Infrastructure is a beta that continuously adjusts CPU and memory requests for selected Kubernetes Deployments, shrinking over-provisioned requests and increasing undersized ones. Recommendations account for node contention and sidecars; resources used by HPA or KEDA scaling are left unchanged. Users can inspect recommendations and estimated monthly cost impact before enabling changes, with estimates customizable to their prices and discounts. It is off by default and enabled cluster by cluster and Deployment by Deployment. It changes requests, never limits; uses in-place resizes when possible and otherwise a rollout with backoff; records changes in annotations intended to avoid Argo CD and Flux drift; and restricts settings to admins with audit events. Recommendations use unsampled eBPF data, processed by the groundcover backend in the customer's cloud via BYOC. The beta covers Deployments and sidecars; other workload types, OOM-kill response, and JVM-aware sizing are listed as roadmap items.

### Source excerpt

Kubernetes requests are set once and rarely revisited. Autonomous Infrastructure keeps them right for cost and stability, inside your guardrails.

## Building the AWS Partnership from the Other Side of the Table

DevFeed: [Building the AWS Partnership from the Other Side of the Table](<https://devfeed.tech/articles/building-the-aws-partnership-from-the-other-side-of-the-table-105939.md>)

Original publisher: [Read original article](<https://www.groundcover.com/blog/aws-partnership-mmiller>)

Author: Max Miller

Published: 2026-10-27T14:07:00Z

Content type: opinion

Language: en

Sources: [Ground Cover](<https://devfeed.tech/sources/ground-cover.md>)

Topics: [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [observability](<https://devfeed.tech/topics/observability.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [apm](<https://devfeed.tech/tags/apm.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [aws](<https://devfeed.tech/tags/aws.md>), [bring-your-own-cloud](<https://devfeed.tech/tags/bring-your-own-cloud.md>), [byoc](<https://devfeed.tech/tags/byoc.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [code](<https://devfeed.tech/tags/code.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [compute](<https://devfeed.tech/tags/compute.md>), [cost](<https://devfeed.tech/tags/cost.md>), [costs](<https://devfeed.tech/tags/costs.md>), [customer](<https://devfeed.tech/tags/customer.md>), [data](<https://devfeed.tech/tags/data.md>), [distributed-tracing](<https://devfeed.tech/tags/distributed-tracing.md>), [ebpf](<https://devfeed.tech/tags/ebpf.md>), [groundcover](<https://devfeed.tech/tags/groundcover.md>), [partner](<https://devfeed.tech/tags/partner.md>), [partnership](<https://devfeed.tech/tags/partnership.md>), [re-invent](<https://devfeed.tech/tags/re-invent.md>)

### AI overview

The author says groundcover's AWS partnership is built around aligning co-sell efforts with customer needs and AWS field teams. Its eBPF sensor collects traces, logs, metrics, and network activity without SDKs, code changes, or redeployments; its BYOC design processes and stores telemetry in the customer's AWS account. The article says that infrastructure spend can count toward AWS EDP or PPA commitments, while per-node pricing avoids charges that rise with telemetry volume. It cites BigBasket as having halved observability costs while expanding full-stack coverage. The author also describes groundcover's re:Invent plans, two pending AWS competency submissions, and its listing as a Kiro power for observability.

### Source excerpt

Hear from our AWS Partner Manager, Max Miller as he discusses why he joined the groundcover team, the groundcover AWS partnership as well as our plans for re:Invent.

## Why I joined groundcover

DevFeed: [Why I joined groundcover](<https://devfeed.tech/articles/why-i-joined-groundcover-80112.md>)

Original publisher: [Read original article](<https://www.groundcover.com/blog/why-i-joined-groundcover-aturner>)

Author: Alex Turner

Published: 2026-09-28T10:12:00Z

Content type: opinion

Language: en

Sources: [Ground Cover](<https://devfeed.tech/sources/ground-cover.md>)

Topics: [observability](<https://devfeed.tech/topics/observability.md>), [Google Cloud Platform (GCP)](<https://devfeed.tech/topics/google-cloud.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-infrastructure](<https://devfeed.tech/tags/ai-infrastructure.md>), [bring-your-own-cloud](<https://devfeed.tech/tags/bring-your-own-cloud.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [ebpf](<https://devfeed.tech/tags/ebpf.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [google-cloud](<https://devfeed.tech/tags/google-cloud.md>), [groundcover](<https://devfeed.tech/tags/groundcover.md>)

### AI overview

Alex Turner explains why he joined groundcover, highlighting its Google Cloud partnership and BYOC observability architecture. He says the approach keeps telemetry within customers' Google Cloud environments, reducing the need to send large data volumes to an external vendor. The article also describes an integration with GKE Autopilot that aims to provide eBPF-based observability for managed Kubernetes clusters while retaining data control.

### Source excerpt

Hear from groundcover's Google Cloud Partner Manager Alex Turner as he describes why he joined groundcover and the milestones already achieved with the partnership.

## Why we acquired Wand: Building toward autonomous infrastructure

DevFeed: [Why we acquired Wand: Building toward autonomous infrastructure](<https://devfeed.tech/articles/why-we-acquired-wand-building-toward-autonomous-infrastructure-80114.md>)

Original publisher: [Read original article](<https://www.groundcover.com/blog/why-we-acquired-wand-autonomous-infrastructure>)

Author: Shahar Azulay

Published: 2026-09-24T09:30:00Z

Content type: news

Language: en

Sources: [Ground Cover](<https://devfeed.tech/sources/ground-cover.md>)

Topics: [platform engineering automation](<https://devfeed.tech/topics/platform-engineering-automation.md>), [observability](<https://devfeed.tech/topics/observability.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>)

Tags: [autonomous-infrastructure](<https://devfeed.tech/tags/autonomous-infrastructure.md>), [cost-optimization](<https://devfeed.tech/tags/cost-optimization.md>), [groundcover](<https://devfeed.tech/tags/groundcover.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-resource-management](<https://devfeed.tech/tags/kubernetes-resource-management.md>), [observability](<https://devfeed.tech/tags/observability.md>)

### AI overview

groundcover says it is acquiring Wand, whose software continuously adjusts Kubernetes resources based on workload behavior. The article presents the deal as a step toward infrastructure that can use production telemetry and engineering context to make operational decisions within engineer-defined boundaries. It discusses how autonomous resource management could affect cost, reliability, observability, and the role of engineers in production operations.

### Source excerpt

groundcover acquires Wand to bring autonomous, self-optimizing Kubernetes resource management to the next generation of observability platforms.

## Open source didn't get less important because AI can write the code

DevFeed: [Open source didn't get less important because AI can write the code](<https://devfeed.tech/articles/open-source-didn-t-get-less-important-because-ai-can-write-the-code-80081.md>)

Original publisher: [Read original article](<https://www.groundcover.com/blog/open-source-ai-naor-peled>)

Author: Anais Dotis

Published: 2026-09-22T17:27:00Z

Content type: article

Language: en

Sources: [Ground Cover](<https://devfeed.tech/sources/ground-cover.md>)

Topics: [open source maintenance](<https://devfeed.tech/topics/open-source-maintenance.md>), [Maintainers](<https://devfeed.tech/topics/maintainers.md>), [ai code review](<https://devfeed.tech/topics/ai-code-review.md>)

Tags: [code-review](<https://devfeed.tech/tags/code-review.md>), [coding-agent](<https://devfeed.tech/tags/coding-agent.md>), [open-source](<https://devfeed.tech/tags/open-source.md>)

### AI overview

Naor Peled, a software engineer and open-source maintainer, argues that contributing remains valuable in the age of AI-generated code. The article discusses how contributions help build maintainer communities, reduce project backlogs, and develop contributors' judgment, while AI-assisted pull requests can increase review demands when submitters do not engage with feedback.

### Source excerpt

Learn about the importance of contributing to open source in the AI era with Naor Peled.

## How eBPF and OpenTelemetry Reveal a Payment Service Regression

DevFeed: [How eBPF and OpenTelemetry Reveal a Payment Service Regression](<https://devfeed.tech/articles/how-ebpf-enriches-otel-a-payment-service-quietly-regressing-after-an-unsuccessful-migration-79994.md>)

Original publisher: [Read original article](<https://www.groundcover.com/blog/ebpf-otel-payment-service-regression>)

Author: Anais Dotis

Published: 2026-09-22T17:13:00Z

Content type: article

Language: en

Sources: [Ground Cover](<https://devfeed.tech/sources/ground-cover.md>)

Topics: [eBPF](<https://devfeed.tech/topics/ebpf.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [expand and contract migration](<https://devfeed.tech/topics/expand-and-contract-migration.md>), [zero downtime deployment](<https://devfeed.tech/topics/zero-downtime-deployment.md>)

Tags: [ebpf](<https://devfeed.tech/tags/ebpf.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [migrations](<https://devfeed.tech/tags/migrations.md>), [otel](<https://devfeed.tech/tags/otel.md>), [payment](<https://devfeed.tech/tags/payment.md>)

### AI overview

The article demonstrates how eBPF payload capture, OpenTelemetry traces, and Kubernetes configuration diffs helped investigate a payment service regression after a migration. It also describes eBPF's limits for identifying application functions without symbols and frame pointers.

### Source excerpt

Explore how eBPF payload capture and Kubernetes config diffs reveal payment service regressions and failed migrations that traditional APM tracing misses.

## How eBPF Enriches OTel-A slow SQL query caused by one user with a million rows.

DevFeed: [How eBPF Enriches OTel-A slow SQL query caused by one user with a million rows.](<https://devfeed.tech/articles/how-ebpf-enriches-otel-a-slow-sql-query-caused-by-one-user-with-a-million-rows-79996.md>)

Original publisher: [Read original article](<https://www.groundcover.com/blog/ebpf-otel-slow-sql-query>)

Author: Anais Dotis

Published: 2026-09-22T17:07:00Z

Content type: tutorial

Language: en

Sources: [Ground Cover](<https://devfeed.tech/sources/ground-cover.md>)

Topics: [eBPF](<https://devfeed.tech/topics/ebpf.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [database-optimization](<https://devfeed.tech/topics/database-optimization.md>), [SQL](<https://devfeed.tech/topics/sql.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>)

Tags: [bedrock](<https://devfeed.tech/tags/bedrock.md>), [data](<https://devfeed.tech/tags/data.md>), [ebpf](<https://devfeed.tech/tags/ebpf.md>), [observability](<https://devfeed.tech/tags/observability.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [otel](<https://devfeed.tech/tags/otel.md>), [sql](<https://devfeed.tech/tags/sql.md>)

### AI overview

The article demonstrates how eBPF telemetry can complement OpenTelemetry by exposing database bind parameters and response data omitted from ordinary spans. In a Postgres example, isolating one user's data explains elevated query latency; the article reports that excluding it reduced P95 latency from 562 ms to 125 ms. It also describes using a saved AI agent skill to investigate the telemetry and recommends data-volume remedies rather than adding an index.

### Source excerpt

Four failure modes where eBPF and OpenTelemetry each answer half the question, and where relying on only one leaves you guessing. Learn how eBPF enriches OTel data for complete observability into your application and services.

## How eBPF and OpenTelemetry Help Diagnose a Blocking Postgres Index Rebuild

DevFeed: [How eBPF and OpenTelemetry Help Diagnose a Blocking Postgres Index Rebuild](<https://devfeed.tech/articles/how-ebpf-enriches-otel-a-postgres-index-rebuild-strangling-everything-around-it-79995.md>)

Original publisher: [Read original article](<https://www.groundcover.com/blog/ebpf-otel-postgres-index-rebuild>)

Author: Anais Dotis

Published: 2026-09-22T17:07:00Z

Content type: article

Language: en

Sources: [Ground Cover](<https://devfeed.tech/sources/ground-cover.md>)

Topics: [eBPF](<https://devfeed.tech/topics/ebpf.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [database-optimization](<https://devfeed.tech/topics/database-optimization.md>), [performance-optimization](<https://devfeed.tech/topics/performance-optimization.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [database](<https://devfeed.tech/tags/database.md>), [database-performance](<https://devfeed.tech/tags/database-performance.md>), [ebpf](<https://devfeed.tech/tags/ebpf.md>), [latency](<https://devfeed.tech/tags/latency.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [otel](<https://devfeed.tech/tags/otel.md>), [performance](<https://devfeed.tech/tags/performance.md>)

### AI overview

The article demonstrates how eBPF and OpenTelemetry telemetry can help an agent identify a blocking Postgres index rebuild that causes latency across a cluster. It argues that eBPF provides broad visibility into database statements while OpenTelemetry adds application context, making problems easier to investigate without relying on prior instrumentation.

### Source excerpt

Discover how eBPF and OpenTelemetry help diagnose hidden database performance bottlenecks, such as a blocking Postgres index rebuild causing silent latency spikes.

## How eBPF Enriches OTel-A missing database table

DevFeed: [How eBPF Enriches OTel-A missing database table](<https://devfeed.tech/articles/how-ebpf-enriches-otel-a-missing-database-table-79993.md>)

Original publisher: [Read original article](<https://www.groundcover.com/blog/ebpf-otel-missing-db-table>)

Author: Anais Dotis

Published: 2026-09-22T17:07:00Z

Content type: tutorial

Language: en

Sources: [Ground Cover](<https://devfeed.tech/sources/ground-cover.md>)

Topics: [eBPF](<https://devfeed.tech/topics/ebpf.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [cloud service outage management](<https://devfeed.tech/topics/cloud-service-outage-management.md>)

Tags: [api-gateway](<https://devfeed.tech/tags/api-gateway.md>), [container](<https://devfeed.tech/tags/container.md>), [ebpf](<https://devfeed.tech/tags/ebpf.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [otel](<https://devfeed.tech/tags/otel.md>)

### AI overview

The article demonstrates how eBPF and OpenTelemetry (OTel) surface a missing database table caused by an uninstrumented Kubernetes job. The failure's SQL statement, error code, latency, pod, and cluster appear in telemetry despite the job having no application-level instrumentation. It argues that eBPF provides broad service coverage while OTel adds application context.

### Source excerpt

Learn how eBPF captures database errors, full statements, and missing table failures from uninstrumented scripts and background jobs where OpenTelemetry has no visibility.

## groundcover Now Supports Google Kubernetes Engine (GKE) Autopilot

DevFeed: [groundcover Now Supports Google Kubernetes Engine (GKE) Autopilot](<https://devfeed.tech/articles/groundcover-now-supports-google-kubernetes-engine-gke-autopilot-80004.md>)

Original publisher: [Read original article](<https://www.groundcover.com/blog/gke-autopilot-support>)

Author: Adam Hicks

Published: 2026-09-17T17:28:00Z

Content type: release

Language: en

Sources: [Ground Cover](<https://devfeed.tech/sources/ground-cover.md>)

Topics: [Gke](<https://devfeed.tech/topics/gke.md>), [eBPF](<https://devfeed.tech/topics/ebpf.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>)

Tags: [ebpf](<https://devfeed.tech/tags/ebpf.md>), [google-kubernetes-engine](<https://devfeed.tech/tags/google-kubernetes-engine.md>), [groundcover](<https://devfeed.tech/tags/groundcover.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [instrumentation](<https://devfeed.tech/tags/instrumentation.md>), [managed-kubernetes](<https://devfeed.tech/tags/managed-kubernetes.md>), [observability](<https://devfeed.tech/tags/observability.md>)

### AI overview

groundcover announces approval as a Google Kubernetes Engine Autopilot partner, enabling deployment of its eBPF sensor through Google's allowlisting process. The sensor provides telemetry across infrastructure, applications, Kubernetes workloads, and AI services without requiring application instrumentation.

### Source excerpt

Deploy groundcover's eBPF-powered observability platform on Google Kubernetes Engine (GKE) Autopilot with Google's approved partner allowlisting. Get zero-instrumentation, full-stack observability in fully managed Kubernetes clusters.

## Everything New in groundcover Dashboards: August 2026

DevFeed: [Everything New in groundcover Dashboards: August 2026](<https://devfeed.tech/articles/everything-new-in-groundcover-dashboards-august-2026-80008.md>)

Original publisher: [Read original article](<https://www.groundcover.com/blog/groundcover-everything-new-in-dashboards>)

Author: Shelby Salling

Published: 2026-08-26T05:00:00Z

Content type: article

Language: en

Sources: [Ground Cover](<https://devfeed.tech/sources/ground-cover.md>)

Topics: [Grafana](<https://devfeed.tech/topics/grafana.md>), [Data visualization](<https://devfeed.tech/topics/data-visualization.md>), [feature flags](<https://devfeed.tech/topics/feature-flags.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [apm](<https://devfeed.tech/tags/apm.md>), [dashboards](<https://devfeed.tech/tags/dashboards.md>), [groundcover](<https://devfeed.tech/tags/groundcover.md>)

### AI overview

Groundcover's dashboard update adds sketch-to-dashboard creation with an agent, visualization controls, search and version history, sharing and export features, and expanded gcQL querying. The article presents these changes as improvements for both agent-assisted dashboard building and human review and use.

### Source excerpt

A roundup of everything new in groundcover Dashboards this quarter: thresholds, tree maps, gcQL, and more, all built for agents and humans alike.

## groundcover's Partner Ecosystem Is Scaling Fast - Here's What's Behind the Momentum

DevFeed: [groundcover's Partner Ecosystem Is Scaling Fast - Here's What's Behind the Momentum](<https://devfeed.tech/articles/groundcover-s-partner-ecosystem-is-scaling-fast-here-s-what-s-behind-the-momentum-80009.md>)

Original publisher: [Read original article](<https://www.groundcover.com/blog/groundcover-partner-ecosystem-scaling-fast>)

Author: Karen Hui

Published: 2026-08-25T17:00:00Z

Content type: article

Language: en

Sources: [Ground Cover](<https://devfeed.tech/sources/ground-cover.md>)

Topics: [API Business Models](<https://devfeed.tech/topics/api-business-models.md>), [Product Management](<https://devfeed.tech/topics/product-management.md>), [Digital Ocean](<https://devfeed.tech/topics/digital-ocean.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-applications](<https://devfeed.tech/tags/ai-applications.md>), [ai-observability](<https://devfeed.tech/tags/ai-observability.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [aws](<https://devfeed.tech/tags/aws.md>), [build](<https://devfeed.tech/tags/build.md>), [building](<https://devfeed.tech/tags/building.md>), [business](<https://devfeed.tech/tags/business.md>), [c](<https://devfeed.tech/tags/c.md>), [channel](<https://devfeed.tech/tags/channel.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-native](<https://devfeed.tech/tags/cloud-native.md>), [ecosystem](<https://devfeed.tech/tags/ecosystem.md>), [groundcover](<https://devfeed.tech/tags/groundcover.md>), [launch](<https://devfeed.tech/tags/launch.md>), [partner](<https://devfeed.tech/tags/partner.md>), [partners](<https://devfeed.tech/tags/partners.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [scaling](<https://devfeed.tech/tags/scaling.md>)

### AI overview

groundcover describes the growth of its partner ecosystem, reporting that partner-sourced pipeline has increased eight-fold and now accounts for more than 10 percent of its overall pipeline. The article outlines its reseller and services partnerships, cloud provider referrals, and plans for certifications and a marketing development fund.

### Source excerpt

Partner-sourced pipeline has grown eight-fold since launch and now represents more than 10 percent of groundcover's overall pipeline, a strong indication that partners are becoming an increasingly important source of new business rather than a secondary channel.

## Groundcover connects observability agents to Slack, Linear, and team context

DevFeed: [Groundcover connects observability agents to Slack, Linear, and team context](<https://devfeed.tech/articles/meet-groundcover-put-agent-mode-to-work-where-your-team-already-works-80066.md>)

Original publisher: [Read original article](<https://www.groundcover.com/blog/meet-groundcover>)

Author: Anais Dotis

Published: 2026-08-13T19:50:00Z

Content type: article

Language: en

Sources: [Ground Cover](<https://devfeed.tech/sources/ground-cover.md>)

Topics: [telemetry](<https://devfeed.tech/topics/telemetry.md>), [agent observability](<https://devfeed.tech/topics/agent-observability.md>), [workflow automation](<https://devfeed.tech/topics/workflow-automation.md>), [Slack](<https://devfeed.tech/topics/slack.md>), [Linear](<https://devfeed.tech/topics/linear.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [dashboards](<https://devfeed.tech/tags/dashboards.md>), [groundcover](<https://devfeed.tech/tags/groundcover.md>), [linear](<https://devfeed.tech/tags/linear.md>), [logs](<https://devfeed.tech/tags/logs.md>), [root-cause-analysis](<https://devfeed.tech/tags/root-cause-analysis.md>), [slack](<https://devfeed.tech/tags/slack.md>), [traces](<https://devfeed.tech/tags/traces.md>)

### AI overview

Groundcover describes first-class connectors that let its observability agent use organizational context from tools such as Slack, Linear, Cursor Cloud Agents, and Notion alongside telemetry. The agent can investigate alerts, build dashboards, and create Linear tickets, with controls to allow, require approval for, or block specific actions. The article demonstrates an incident workflow in which the agent analyzes telemetry, requests approval before creating a ticket, and records a root cause analysis.

### Source excerpt

Learn about how to set up the Slack and Linear connector with groundcover to use the groundcover agent directly in Slack to retrieve logs, traces, monitor issues, dashboards, and even RUM. Then use the groundcover agent in Slack to perform root cause analysis and file Linear tickets.

## True BYOC: What It Actually Means, and How to Evaluate It

DevFeed: [True BYOC: What It Actually Means, and How to Evaluate It](<https://devfeed.tech/articles/true-byoc-what-it-actually-means-and-how-to-evaluate-it-80105.md>)

Original publisher: [Read original article](<https://www.groundcover.com/blog/true-byoc>)

Author: Anais Dotis

Published: 2026-08-13T19:42:00Z

Content type: article

Language: en

Sources: [Ground Cover](<https://devfeed.tech/sources/ground-cover.md>)

Topics: [Redpanda BYOC](<https://devfeed.tech/topics/redpanda-byoc.md>), [observability](<https://devfeed.tech/topics/observability.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>)

Tags: [all](<https://devfeed.tech/tags/all.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [bring-your-own-cloud](<https://devfeed.tech/tags/bring-your-own-cloud.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [control-plane](<https://devfeed.tech/tags/control-plane.md>), [data-residency](<https://devfeed.tech/tags/data-residency.md>), [ebpf](<https://devfeed.tech/tags/ebpf.md>), [observability](<https://devfeed.tech/tags/observability.md>)

### AI overview

The article explains how to distinguish true bring-your-own-cloud (BYOC) observability deployments from self-hosting and storage-only arrangements. It describes where vendor-managed components, telemetry data, and query execution run, and discusses the tradeoffs for operational responsibility, pricing, data residency, and AI features. It offers questions for evaluating BYOC claims, including how access is scoped, which signals are covered, and where agents and models process data.

### Source excerpt

Understand what True BYOC means and why other observability platforms don't actually offer data residency, control, and sovereignty.

## groundcover's July product showcase: agent integrations, observability updates, dashboards, and AWS cost data

DevFeed: [groundcover's July product showcase: agent integrations, observability updates, dashboards, and AWS cost data](<https://devfeed.tech/articles/groundcover-monthly-showcase-80072.md>)

Original publisher: [Read original article](<https://www.groundcover.com/blog/monthly-showcase>)

Author: Anais Dotis

Published: 2026-08-13T19:35:00Z

Content type: release

Language: en

Sources: [Ground Cover](<https://devfeed.tech/sources/ground-cover.md>)

Topics: [observability](<https://devfeed.tech/topics/observability.md>), [LLM observability](<https://devfeed.tech/topics/llm-observability.md>), [infrastructure monitoring](<https://devfeed.tech/topics/infrastructure-monitoring.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [api](<https://devfeed.tech/tags/api.md>), [app](<https://devfeed.tech/tags/app.md>), [aws](<https://devfeed.tech/tags/aws.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [connectors](<https://devfeed.tech/tags/connectors.md>), [cost](<https://devfeed.tech/tags/cost.md>), [cost-control](<https://devfeed.tech/tags/cost-control.md>), [cursor](<https://devfeed.tech/tags/cursor.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [dashboards](<https://devfeed.tech/tags/dashboards.md>), [databases](<https://devfeed.tech/tags/databases.md>), [monthly](<https://devfeed.tech/tags/monthly.md>), [showcase](<https://devfeed.tech/tags/showcase.md>)

### AI overview

groundcover's July showcase describes expanded Agent Mode connectors for workplace tools, permission controls and incident workflows, along with updates to monitor issues, dashboards, retention management, AWS cost data, and a curated dashboard catalog. The release focuses on giving the observability agent more context and making its findings easier to use.

### Source excerpt

We're proud of what we build at grouncover. This showcase highlights the most impressive work from this past month.

## Dashboards aren't dead. They help pave the path for custom agents and promote human feedback.

DevFeed: [Dashboards aren't dead. They help pave the path for custom agents and promote human feedback.](<https://devfeed.tech/articles/dashboards-aren-t-dead-they-help-pave-the-path-for-custom-agents-and-promote-human-feedback-79983.md>)

Original publisher: [Read original article](<https://www.groundcover.com/blog/dashboards-arent-dead>)

Author: Anais Dotis

Published: 2026-08-12T21:58:00Z

Content type: article

Language: en

Sources: [Ground Cover](<https://devfeed.tech/sources/ground-cover.md>)

Topics: [observability](<https://devfeed.tech/topics/observability.md>), [dashboards](<https://devfeed.tech/topics/dashboards.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [human review](<https://devfeed.tech/topics/human-review.md>)

Tags: [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [dashboards](<https://devfeed.tech/tags/dashboards.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [human-feedback](<https://devfeed.tech/tags/human-feedback.md>), [observability](<https://devfeed.tech/tags/observability.md>)

### AI overview

The article argues that dashboards remain useful alongside AI agents in observability work. Agents can investigate alerts, visualize telemetry, and help build or migrate dashboards, while dashboards provide structured context that can improve agent responses. It also describes dashboard features for mapping inconsistent data fields, curated dashboard templates, and readability improvements.

### Source excerpt

AI agents aren't replacing dashboards. See how dashboards, observability agents, and human feedback work together to investigate issues, visualize telemetry, and accelerate remediation.

[Next page](<https://devfeed.tech/sources/ground-cover.md?cursor=WyIyMDI2LTA4LTEyVDIxOjU4OjAwKzAwOjAwIiwgIjEyYzNmZjM2LTQ0OWEtNGFmNi1hYjhjLTQzNmI1NjE4YTU0ZCJd>)