# Frontend observability

Frontend observability measures web application performance, errors, interactions, and telemetry in users' browsers, correlating frontend data with backend systems.

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

## Track Lighthouse scores alongside real-user data in Datadog

DevFeed: [Track Lighthouse scores alongside real-user data in Datadog](<https://devfeed.tech/articles/track-lighthouse-scores-alongside-real-user-data-in-datadog-145233.md>)

Original publisher: [Read original article](<https://www.datadoghq.com/blog/lighthouse-audits-rum-synthetic-monitoring/>)

Author: Quentin Sellem; Stella Ma

Published: 2026-11-19T00:00:00Z

Content type: article

Language: en

Sources: [Datadog](<https://devfeed.tech/sources/datadog-the-monitor-blog.md>)

Topics: [real user monitoring](<https://devfeed.tech/topics/real-user-monitoring.md>), [synthetic monitoring](<https://devfeed.tech/topics/synthetic-monitoring.md>), [Frontend observability](<https://devfeed.tech/topics/frontend-observability.md>), [Core Web Vitals](<https://devfeed.tech/topics/core-web-vitals.md>), [datadog](<https://devfeed.tech/topics/datadog.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [dashboards](<https://devfeed.tech/topics/dashboards.md>)

Tags: [2-2](<https://devfeed.tech/tags/2-2.md>), [accessibility](<https://devfeed.tech/tags/accessibility.md>), [audits](<https://devfeed.tech/tags/audits.md>), [compare](<https://devfeed.tech/tags/compare.md>), [data](<https://devfeed.tech/tags/data.md>), [datadog](<https://devfeed.tech/tags/datadog.md>), [digital-experience-monitoring](<https://devfeed.tech/tags/digital-experience-monitoring.md>), [field](<https://devfeed.tech/tags/field.md>), [health](<https://devfeed.tech/tags/health.md>), [lab](<https://devfeed.tech/tags/lab.md>), [lighthouse](<https://devfeed.tech/tags/lighthouse.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [performance](<https://devfeed.tech/tags/performance.md>), [real-user-monitoring](<https://devfeed.tech/tags/real-user-monitoring.md>), [releases](<https://devfeed.tech/tags/releases.md>), [results](<https://devfeed.tech/tags/results.md>), [rum](<https://devfeed.tech/tags/rum.md>), [run](<https://devfeed.tech/tags/run.md>), [scheduled](<https://devfeed.tech/tags/scheduled.md>), [synthetic](<https://devfeed.tech/tags/synthetic.md>), [synthetic-monitoring](<https://devfeed.tech/tags/synthetic-monitoring.md>), [testing](<https://devfeed.tech/tags/testing.md>), [user](<https://devfeed.tech/tags/user.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Datadog runs Lighthouse audits on the regular schedule of existing Synthetic browser tests and sends results to RUM, including for authenticated pages. RUM places controlled lab scores and metrics alongside real-user Core Web Vitals: when both worsen, that can indicate a page-level regression; when field performance worsens but Lighthouse stays stable, the issue may affect a subset of users and can be investigated by segmenting RUM data. Teams can inspect failed audits and reports, chart category scores over time, break metrics down by release, and use them in dashboards, monitors, and SLOs. Lighthouse-enabled tests can also be configured from an unaudited RUM view. The feature requires both Datadog Synthetic Monitoring and RUM.

### Source excerpt

Run scheduled Lighthouse audits with Datadog Synthetic Monitoring, compare lab results with field data in RUM, and track page health across releases.

## Web-Perf Wednesday 018 - Soft Navigations Lift the CrUX Pass Rate

DevFeed: [Web-Perf Wednesday 018 - Soft Navigations Lift the CrUX Pass Rate](<https://devfeed.tech/articles/web-perf-wednesday-018-soft-navigations-lift-the-crux-pass-rate-141986.md>)

Original publisher: [Read original article](<https://csswizardry.com/2026/11/web-perf-wednesday-018-soft-navigations-lift-the-crux-pass-rate/>)

Author: Harry Roberts

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

Content type: article

Language: en

Sources: [CSS Wizardry](<https://devfeed.tech/sources/css-wizardry.md>)

Topics: [Core Web Vitals](<https://devfeed.tech/topics/core-web-vitals.md>), [Single-page application (SPA)](<https://devfeed.tech/topics/spa.md>), [Page Speed Optimization](<https://devfeed.tech/topics/page-speed-optimization.md>), [Frontend observability](<https://devfeed.tech/topics/frontend-observability.md>), [Interaction to Next Paint](<https://devfeed.tech/topics/interaction-to-next-paint.md>), [Firefox](<https://devfeed.tech/topics/firefox.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>), [Web](<https://devfeed.tech/topics/web.md>), [Web APIs](<https://devfeed.tech/topics/web-apis.md>)

Tags: [advertising](<https://devfeed.tech/tags/advertising.md>), [core-web-vitals](<https://devfeed.tech/tags/core-web-vitals.md>), [crux](<https://devfeed.tech/tags/crux.md>), [perf](<https://devfeed.tech/tags/perf.md>), [privacy](<https://devfeed.tech/tags/privacy.md>), [rum](<https://devfeed.tech/tags/rum.md>), [spa](<https://devfeed.tech/tags/spa.md>), [spas](<https://devfeed.tech/tags/spas.md>), [web-perf-wednesdays](<https://devfeed.tech/tags/web-perf-wednesdays.md>)

### AI overview

October 2026 CrUX experimental metrics that include SPA soft navigations raise the share of origins passing all three Core Web Vitals from 56.3% to 60.3%; this reflects a changed measurement population, not sites suddenly getting faster. The article recommends comparing current and experimental data for the same URLs and form factors, tracing differences to routes, and checking whether RUM recognizes the same navigations. CrUX APIs and CrUX Vis expose soft-navigation FCP and navigation-type views; BigQuery additions are planned for the next monthly release. The existing series remains the reported data for now, with graduation targeted for May 2027 subject to feedback and Search Console use expected afterward. The excerpt also notes Firefox 161 beta support for identifying failed navigation destinations, WPE Android browser traces in Perfetto, and a proposed EU Digital Fairness Act that remains under discussion.

### Source excerpt

CrUX's latest data shows how including SPA soft navigations will raise Core Web Vitals pass rates without sites suddenly becoming faster.

## Speed Insights now measures soft navigations

DevFeed: [Speed Insights now measures soft navigations](<https://devfeed.tech/articles/speed-insights-now-measures-soft-navigations-140173.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/speed-insights-now-measures-soft-navigations>)

Author: Chris Widmaier

Published: 2026-11-17T12:40:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [real user monitoring](<https://devfeed.tech/topics/real-user-monitoring.md>), [Frontend observability](<https://devfeed.tech/topics/frontend-observability.md>), [Core Web Vitals](<https://devfeed.tech/topics/core-web-vitals.md>), [Single-page application (SPA)](<https://devfeed.tech/topics/spa.md>), [Interaction to Next Paint](<https://devfeed.tech/topics/interaction-to-next-paint.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>)

Tags: [billing](<https://devfeed.tech/tags/billing.md>), [chromium](<https://devfeed.tech/tags/chromium.md>), [client](<https://devfeed.tech/tags/client.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [filter](<https://devfeed.tech/tags/filter.md>), [frameworks](<https://devfeed.tech/tags/frameworks.md>), [inp](<https://devfeed.tech/tags/inp.md>), [insights](<https://devfeed.tech/tags/insights.md>), [lcp](<https://devfeed.tech/tags/lcp.md>), [navigation](<https://devfeed.tech/tags/navigation.md>), [next-js](<https://devfeed.tech/tags/next-js.md>), [nuxt](<https://devfeed.tech/tags/nuxt.md>), [performance](<https://devfeed.tech/tags/performance.md>), [plus](<https://devfeed.tech/tags/plus.md>), [project](<https://devfeed.tech/tags/project.md>), [route](<https://devfeed.tech/tags/route.md>), [score](<https://devfeed.tech/tags/score.md>), [speed](<https://devfeed.tech/tags/speed.md>), [sveltekit](<https://devfeed.tech/tags/sveltekit.md>), [users](<https://devfeed.tech/tags/users.md>)

### AI overview

Vercel Speed Insights now tracks client-side soft navigations by default, measuring LCP, FCP, INP, and CLS and including them in the Real Experience Score; it does not measure TTFB because no new document request occurs. The feature works with modern frameworks such as Next.js, SvelteKit, and Nuxt in Chromium-based browsers. The dashboard's Navigation Type filter separates All, Hard, and Soft navigation data. Soft-navigation events count toward Speed Insights Plus usage; existing Plus customers will be emailed when billing begins, while newly enabled Plus projects are billed for these events from the start. To opt out, set `softNavs` to `false` in application code and redeploy using `@vercel/speed-insights` 2.1.0 or later.

### Source excerpt

Speed Insights now measures soft navigations: client-side route changes that update page content without a full reload. This means you can now track performance as users move through your app, not just on full-page loads. Speed Insights captures LCP, FCP, INP, and CLS for soft navigations and includes these measurements in your Real Experience Score. TTFB is not captured because there is no new document request. Soft-navigation tracking is enabled by default for all projects using Speed Insights, with no action required. It works with modern web frameworks such as Next.js, SvelteKit, and Nuxt, in Chromium-based browsers. In your project's Speed Insights dashboard, use the new Navigation Type filter to view All, Hard, or Soft navigation data. Soft-navigation events count toward Speed Insights Plus usage. Existing Plus customers will receive an email with details about when billing for these events begins. For projects that newly enable Plus, these events are billed from the start. To disable soft-navigation tracking, set softNavs to false in your application code and redeploy. This option requires @vercel/speed-insights version 2.1.0 or later: Learn more in the Speed Insights documentation. Read more

## LinkedIn Uses OpenTelemetry to Trace the Member Journey from Tap to Backend

DevFeed: [LinkedIn Uses OpenTelemetry to Trace the Member Journey from Tap to Backend](<https://devfeed.tech/articles/linkedin-uses-opentelemetry-to-trace-the-member-journey-from-tap-to-backend-114150.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/11/linkedin-opentelemetry-journey/>)

Author: Craig Risi

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

Content type: article

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Frontend observability](<https://devfeed.tech/topics/frontend-observability.md>), [gRPC](<https://devfeed.tech/topics/grpc.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [apache](<https://devfeed.tech/tags/apache.md>), [apache-kafka](<https://devfeed.tech/tags/apache-kafka.md>), [backend](<https://devfeed.tech/tags/backend.md>), [clickhouse](<https://devfeed.tech/tags/clickhouse.md>), [client](<https://devfeed.tech/tags/client.md>), [clients](<https://devfeed.tech/tags/clients.md>), [consistency](<https://devfeed.tech/tags/consistency.md>), [correlation](<https://devfeed.tech/tags/correlation.md>), [datadog](<https://devfeed.tech/tags/datadog.md>), [devops](<https://devfeed.tech/tags/devops.md>), [distributed-tracing](<https://devfeed.tech/tags/distributed-tracing.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grpc](<https://devfeed.tech/tags/grpc.md>), [ios](<https://devfeed.tech/tags/ios.md>), [journey](<https://devfeed.tech/tags/journey.md>), [linkedin](<https://devfeed.tech/tags/linkedin.md>), [linkedin-opentelemetry-journey](<https://devfeed.tech/tags/linkedin-opentelemetry-journey.md>), [news](<https://devfeed.tech/tags/news.md>), [observability](<https://devfeed.tech/tags/observability.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>), [trace](<https://devfeed.tech/tags/trace.md>), [user-experience](<https://devfeed.tech/tags/user-experience.md>), [web](<https://devfeed.tech/tags/web.md>)

### AI overview

LinkedIn connects member interactions across iOS, Android, and web to backend execution using OpenTelemetry. Each request keeps its traceId, while a pageForestId groups related requests from a page so engineers can investigate a broader member experience as well as individual traces. LinkedIn's wrappers standardize instrumentation across its varied client and backend stack; shared HTTP and gRPC frameworks instrument common paths, with teams adding spans for business operations. Telemetry moves through Kafka to ClickHouse. Coordinated head sampling uses a pseudonymised member identifier to keep client and server sampling decisions aligned. The platform also batches mobile spans and can flush them when an app backgrounds, and applies attribute allowlists, denylists, and redaction to control trace data. The article characterizes this as a customized OpenTelemetry foundation, rather than a capability unavailable in Jaeger, Grafana Tempo, Datadog, or New Relic.

### Source excerpt

LinkedIn has built an OpenTelemetry-based telemetry platform that connects what members do in its iOS, Android, and web applications with the backend services processing those interactions. By Craig Risi

## Diagnose frontend performance issues with RUM Profiling

DevFeed: [Diagnose frontend performance issues with RUM Profiling](<https://devfeed.tech/articles/diagnose-frontend-performance-issues-with-rum-profiling-113324.md>)

Original publisher: [Read original article](<https://www.datadoghq.com/blog/rum-profiling-mobile/>)

Author: Arti Arutiunov; Jessica Manheimer

Published: 2026-11-02T00:00:00Z

Content type: article

Language: en

Sources: [Datadog](<https://devfeed.tech/sources/datadog-the-monitor-blog.md>)

Topics: [mobile-app-performance](<https://devfeed.tech/topics/mobile-app-performance.md>), [real user monitoring](<https://devfeed.tech/topics/real-user-monitoring.md>), [Frontend observability](<https://devfeed.tech/topics/frontend-observability.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Android](<https://devfeed.tech/topics/android.md>), [bits ai](<https://devfeed.tech/topics/bits-ai.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [browser](<https://devfeed.tech/tags/browser.md>), [code](<https://devfeed.tech/tags/code.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [datadog](<https://devfeed.tech/tags/datadog.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [diagnose](<https://devfeed.tech/tags/diagnose.md>), [digital-experience-monitoring](<https://devfeed.tech/tags/digital-experience-monitoring.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [frontend-performance](<https://devfeed.tech/tags/frontend-performance.md>), [ios](<https://devfeed.tech/tags/ios.md>), [launches](<https://devfeed.tech/tags/launches.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [performance](<https://devfeed.tech/tags/performance.md>), [profiling](<https://devfeed.tech/tags/profiling.md>), [real-user-monitoring](<https://devfeed.tech/tags/real-user-monitoring.md>), [rum](<https://devfeed.tech/tags/rum.md>)

### AI overview

Datadog RUM Profiling links CPU profiles to real-user performance events so teams can investigate code behind slow launches, app hangs, ANRs, and critical workflows without reproducing issues locally. Profiles can be inspected individually or aggregated across sessions, compared between slow and typical launches or app versions, and evaluated alongside RUM metrics such as TTID and TTFD. Teams control iOS and Android collection through adjustable sampling rates; profiling only samples production sessions to limit overhead. Collection differs by platform: Android uses the OS ProfilingManager API, subject to app and device rate limits, and Android 16+ ANR profiles can include system traces; iOS profiles cover launches, hangs, and long tasks. Browser profiling captures JavaScript CPU activity correlated with RUM events. Across platforms, profiles attach to RUM events and feed shared aggregated views. Bits AI and Datadog MCP Server tools can help identify causes and query problematic sessions.

### Source excerpt

Use Datadog RUM Profiling to identify CPU-intensive code behind slow mobile app launches and frontend interactions across iOS, Android, and the browser.

## Front-end observability at scale: How OpenReplay captures billions of daily events in real time with ClickHouse

DevFeed: [Front-end observability at scale: How OpenReplay captures billions of daily events in real time with ClickHouse](<https://devfeed.tech/articles/front-end-observability-at-scale-how-openreplay-captures-billions-of-daily-events-in-real-time-with-clickhouse-93148.md>)

Original publisher: [Read original article](<https://clickhouse.com/blog/openreplay-front-end-observability-at-scale-clickhouse>)

Author: ClickHouse

Published: 2026-10-21T18:40:19Z

Content type: article

Language: en

Sources: [ClickHouse Blog](<https://devfeed.tech/sources/clickhouse-blog.md>)

Topics: [clickhouse](<https://devfeed.tech/topics/clickhouse.md>), [session replay](<https://devfeed.tech/topics/session-replay.md>), [Frontend observability](<https://devfeed.tech/topics/frontend-observability.md>), [streaming data analytics](<https://devfeed.tech/topics/streaming-data-analytics.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2019](<https://devfeed.tech/tags/2019.md>), [about](<https://devfeed.tech/tags/about.md>), [absolute](<https://devfeed.tech/tags/absolute.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [clickhouse](<https://devfeed.tech/tags/clickhouse.md>), [daily](<https://devfeed.tech/tags/daily.md>), [events](<https://devfeed.tech/tags/events.md>), [front-end](<https://devfeed.tech/tags/front-end.md>), [observability](<https://devfeed.tech/tags/observability.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [queries](<https://devfeed.tech/tags/queries.md>), [real-time](<https://devfeed.tech/tags/real-time.md>), [retention](<https://devfeed.tech/tags/retention.md>), [scale](<https://devfeed.tech/tags/scale.md>), [time](<https://devfeed.tech/tags/time.md>), [ttl](<https://devfeed.tech/tags/ttl.md>), [up](<https://devfeed.tech/tags/up.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

OpenReplay moved behavioral event analytics from Postgres to ClickHouse after indexed, partitioned, and sharded session searches still took about three seconds on average and sometimes up to ten; ClickHouse brought average response time to about one second and compressed roughly 1 TB of event tables to 1-2 GB. Retention now uses a ClickHouse TTL setting, replacing scripts, table locks, vacuuming, and weekend cleanup work. Events flow through materialized views, cutting some pipeline changes from two days to about half a day; Go code remains for parts of the pipeline and faster insertion once schemas stabilize. OpenReplay stores metadata in Postgres and recording files in object storage with lifecycle rules. Its self-hosted deployments use one ClickHouse instance and scale vertically, with reported customers reaching billions of events and up to 6 TB daily. The tradeoff is deliberate: a lean single-instance design for customer-controlled infrastructure, rather than sharding; the account says a SaaS-only deployment might use ClickHouse Cloud.

### Source excerpt

OpenReplay replaced Postgres with ClickHouse to ingest billions of events and up to 6 TB a day on a single, vertically scaled instance, with sub-second queries and retention handled by a single TTL setting.

## Grafana Labs connects observability and incident response with Knowledge Graph

DevFeed: [Grafana Labs connects observability and incident response with Knowledge Graph](<https://devfeed.tech/articles/grafana-labs-connects-observability-and-incident-response-with-knowledge-graph-92557.md>)

Original publisher: [Read original article](<https://www.helpnetsecurity.com/2026/10/21/grafana-labs-knowledge-graph/>)

Author: Industry News

Published: 2026-10-21T09:30:38Z

Content type: release

Language: en

Sources: [Help Net Security](<https://devfeed.tech/sources/help-net-security.md>)

Topics: [Grafana Cloud](<https://devfeed.tech/topics/grafana-cloud.md>), [observability](<https://devfeed.tech/topics/observability.md>), [digital experience monitoring](<https://devfeed.tech/topics/digital-experience-monitoring.md>), [incident](<https://devfeed.tech/topics/incident.md>), [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>), [knowledge-engineering](<https://devfeed.tech/topics/knowledge-engineering.md>), [база знаний](<https://devfeed.tech/topics/tag-c51cc4bf76e5.md>), [knowledge-management](<https://devfeed.tech/topics/knowledge-management.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [session replay](<https://devfeed.tech/topics/session-replay.md>), [Frontend observability](<https://devfeed.tech/topics/frontend-observability.md>), [Grafana Cloud Frontend Observability](<https://devfeed.tech/topics/grafana-cloud-frontend-observability.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-systems](<https://devfeed.tech/tags/agentic-systems.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-systems](<https://devfeed.tech/tags/ai-systems.md>), [context](<https://devfeed.tech/tags/context.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [digital-experience](<https://devfeed.tech/tags/digital-experience.md>), [digital-experience-monitoring](<https://devfeed.tech/tags/digital-experience-monitoring.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-cloud](<https://devfeed.tech/tags/grafana-cloud.md>), [grafana-labs](<https://devfeed.tech/tags/grafana-labs.md>), [graph](<https://devfeed.tech/tags/graph.md>), [incident-response](<https://devfeed.tech/tags/incident-response.md>), [industry-news](<https://devfeed.tech/tags/industry-news.md>), [knowledge-graph](<https://devfeed.tech/tags/knowledge-graph.md>), [observability](<https://devfeed.tech/tags/observability.md>)

### AI overview

Grafana Labs is adding a Knowledge Graph to every Grafana Cloud stack to connect telemetry across infrastructure, applications and user experience, giving responders and agents shared runtime context for tracing dependencies and business impact. Custom entities and agent access are generally available; service ownership and runbooks in the graph are in private preview. Digital Experience Monitoring adds Session Replay (public preview), mobile observability and Critical User Journeys (private previews), linking browser or mobile experience to stack telemetry. Grafana Cloud IRM adds event-driven Workflows (public preview), plus private-preview Operational Context that retains prior investigation findings and a Response Console for people and agents to collaborate. The excerpt describes the announcements and availability stages, not measured outcomes.

### Source excerpt

Grafana Labs has announced a Knowledge Graph in every Grafana Cloud stack, alongside new Digital Experience Monitoring capabilities and updates to Grafana Cloud Incident Response Management (IRM). The releases connect infrastructure and application dependencies with user experience and incident response, giving people and agents shared context to investigate problems and take action. As agentic systems become more architecturally complex and teams use agents to investigate and respond to problems, those agents need context that connects ... More -> The post Grafana Labs connects observability and incident response with Knowledge Graph appeared first on Help Net Security.

## Web-Perf Wednesday 012 - Return to the Unresolved Trace

DevFeed: [Web-Perf Wednesday 012 - Return to the Unresolved Trace](<https://devfeed.tech/articles/web-perf-wednesday-012-return-to-the-unresolved-trace-66639.md>)

Original publisher: [Read original article](<https://csswizardry.com/2026/10/web-perf-wednesday-012-return-to-the-unresolved-trace/>)

Author: Harry Roberts

Published: 2026-10-07T11:00:00Z

Content type: article

Language: en

Sources: [CSS Wizardry](<https://devfeed.tech/sources/css-wizardry.md>)

Topics: [synthetic monitoring](<https://devfeed.tech/topics/synthetic-monitoring.md>), [performance-optimization](<https://devfeed.tech/topics/performance-optimization.md>), [Frontend observability](<https://devfeed.tech/topics/frontend-observability.md>)

Tags: [investigations](<https://devfeed.tech/tags/investigations.md>), [measurement](<https://devfeed.tech/tags/measurement.md>), [performance](<https://devfeed.tech/tags/performance.md>), [rum](<https://devfeed.tech/tags/rum.md>), [traces](<https://devfeed.tech/tags/traces.md>), [web-performance](<https://devfeed.tech/tags/web-performance.md>)

### AI overview

A quiet week in web performance offers a chance to revisit unresolved investigations, unexplained dashboard changes, and tests that need another run. The article encourages teams to use partial RUM, synthetic test, or browser trace evidence to define a testable performance question and decide what to check next.

### Source excerpt

A quiet week leaves room to revisit unfinished performance investigations and turn partial evidence into a clear next step.

## Digital Experience Monitoring with Grafana Cloud: Session Replay, synthetic checks, and faster investigations

DevFeed: [Digital Experience Monitoring with Grafana Cloud: Session Replay, synthetic checks, and faster investigations](<https://devfeed.tech/articles/digital-experience-monitoring-with-grafana-cloud-session-replay-synthetic-checks-and-faster-investigations-21514.md>)

Original publisher: [Read original article](<https://grafana.com/blog/digital-experience-monitoring-with-grafana-cloud-session-replay-synthetic-checks-and-faster-investigations/>)

Author: Bukola Ayodele

Published: 2026-09-15T01:35:30.954353Z

Content type: article

Language: en

Sources: [Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [digital experience monitoring](<https://devfeed.tech/topics/digital-experience-monitoring.md>), [Grafana Cloud](<https://devfeed.tech/topics/grafana-cloud.md>), [Frontend observability](<https://devfeed.tech/topics/frontend-observability.md>), [synthetic monitoring](<https://devfeed.tech/topics/synthetic-monitoring.md>), [real user monitoring](<https://devfeed.tech/topics/real-user-monitoring.md>), [session replay](<https://devfeed.tech/topics/session-replay.md>), [Instrumentation](<https://devfeed.tech/topics/instrumentation.md>), [Web app](<https://devfeed.tech/topics/webapp.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [Core Web Vitals](<https://devfeed.tech/topics/core-web-vitals.md>), [tracing](<https://devfeed.tech/topics/tracing.md>)

Tags: [analytics](<https://devfeed.tech/tags/analytics.md>), [core-web-vitals](<https://devfeed.tech/tags/core-web-vitals.md>), [digital-experience-monitoring](<https://devfeed.tech/tags/digital-experience-monitoring.md>), [frontend-observability](<https://devfeed.tech/tags/frontend-observability.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-cloud](<https://devfeed.tech/tags/grafana-cloud.md>), [grafana-cloud-frontend-observability](<https://devfeed.tech/tags/grafana-cloud-frontend-observability.md>), [instrumentation](<https://devfeed.tech/tags/instrumentation.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [real-user-monitoring](<https://devfeed.tech/tags/real-user-monitoring.md>), [session-replay](<https://devfeed.tech/tags/session-replay.md>), [synthetic](<https://devfeed.tech/tags/synthetic.md>), [synthetic-monitoring](<https://devfeed.tech/tags/synthetic-monitoring.md>), [traces](<https://devfeed.tech/tags/traces.md>), [web-applications](<https://devfeed.tech/tags/web-applications.md>)

### AI overview

This article explains how Digital Experience Monitoring in Grafana Cloud combines Frontend Observability, Synthetic Monitoring, real user monitoring, and session replay. It shows how these capabilities help engineering teams detect issues proactively, understand their scope and root causes, correlate frontend signals with backend traces, and resolve production problems faster.

### Source excerpt

When something breaks in production, the questions that matter most are also the toughest to answer from metrics alone: who was affected, what did they actually see, and is this worth waking someone up for? Answering those questions requires a fuller picture of the issue and its impact on your users. That's where Digital Experience Monitoring (DEM) in Grafana Cloud comes in. By combining Frontend Observability and Synthetic Monitoring, DEM connects real user experiences with proactive testing, helping engineering teams understand the scope of an issue, investigate its cause, and resolve it faster, all within Grafana Cloud. In this blog post, we'll walk through some of the latest DEM updates in Grafana Cloud, and how to get started. You can also learn more by watching the video below. First, what is Digital Experience Monitoring? Digital Experience Monitoring in Grafana Cloud gives you a complete picture of how users experience your web applications, from real user data to proactive synthetic checks. DEM helps your team achieve: Real user visibility: know how users truly experience your web application, not just what your backend metrics suggest. Proactive detection: catch problems before your users do, using automated checks against your critical user journeys. End-to-end correlation: connect a frontend signal to the backend trace behind it. Faster resolution: cut your mean time to recovery from hours to minutes. Session Replay: see exactly what your users saw Session Replay in Grafana Cloud Frontend Observability lets you visually replay what a user saw and did inside your web application. Your team can watch exactly what users experienced and correlate it with real user monitoring signals like Core Web Vitals, user actions, and traces, which makes it a powerful tool for investigating bugs and running root cause analysis. Session Replay is powered by Faro, Grafana's open source JavaScript instrumentation library for collecting real user monitoring data. Let's walk

## From failed check to real user impact: Pairing Synthetic Monitoring and Frontend Observability in Grafana Cloud

DevFeed: [From failed check to real user impact: Pairing Synthetic Monitoring and Frontend Observability in Grafana Cloud](<https://devfeed.tech/articles/from-failed-check-to-real-user-impact-pairing-synthetic-monitoring-and-frontend-observability-in-grafana-cloud-8586.md>)

Original publisher: [Read original article](<https://grafana.com/blog/from-failed-check-to-real-user-impact-pairing-synthetic-monitoring-and-frontend-observability-in-grafana-cloud/>)

Author: Mark Meier

Published: 2026-09-12T11:22:06.456390Z

Content type: tutorial

Language: en

Sources: [Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [synthetic monitoring](<https://devfeed.tech/topics/synthetic-monitoring.md>), [Frontend observability](<https://devfeed.tech/topics/frontend-observability.md>), [Grafana Cloud](<https://devfeed.tech/topics/grafana-cloud.md>), [observability](<https://devfeed.tech/topics/observability.md>)

Tags: [analytics](<https://devfeed.tech/tags/analytics.md>), [frontend-observability](<https://devfeed.tech/tags/frontend-observability.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-cloud](<https://devfeed.tech/tags/grafana-cloud.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [synthetic-monitoring](<https://devfeed.tech/tags/synthetic-monitoring.md>), [traces](<https://devfeed.tech/tags/traces.md>), [uptime](<https://devfeed.tech/tags/uptime.md>)

### AI overview

This article explains how to combine Grafana Cloud Synthetic Monitoring with Frontend Observability to connect proactive checks with real-user impact. It describes the blind spots of synthetic-only monitoring and presents a combined workflow for faster triage, impact-aware alerts, and tests that evolve with real traffic.

### Source excerpt

Say you get a support escalation about a page in the app that won't load. But when you pull up your synthetic checks, they're all green: 100% uptime, probes are passing. Something's not adding up, but which one do you trust? If you've run Grafana Cloud Synthetic Monitoring, you've been on both sides of this. Sometimes it's the ticket: real users hit a wall on the path but your checks pass cleanly. Other times, it's the inverse: a check is failing, you're in a panic, and you start trying to reproduce things for 30 minutes--only to find it was a blip from a single region, with minimal impact to real users. Neither the green dashboard nor the red alert were lying, they just weren't answering the correct question. This ends up being the root problem. Synthetic Monitoring is exceptionally good at telling you if something broke. It can not, however, tell you who it happened to, how bad it was, or why it matters. This is not a flaw in Synthetic Monitoring; it's the boundary of what a controlled, scheduled test can know. Grafana Cloud Frontend Observability helps to close this gap. Synthetic Monitoring gives you a proactive, outside-in signal; Frontend Observability gives you the real-user, inside-out signal. Together they form a closed loop: synthetic alerts end up getting some real user context, and real user data can make your synthetic tests smart. In this post, we'll look at why a synthetic-only strategy can leave blind spots, what Frontend Observability adds, and walk through practical workflows for running them together in Grafana Cloud. Along the way, you'll learn that the payoff is concrete: faster triage, alerts that carry blast-radius context, and a check suite that evolves with real traffic instead of aging against it. Green checks don't mean happy users Synthetic Monitoring is an active signal. You script a journey or declare a target, run it on a schedule from known probe locations, and in return get clean consistent results. This precise control of variables i

## Visual playback of the user journey: Introducing Session Replay in Grafana Cloud Frontend Observability

DevFeed: [Visual playback of the user journey: Introducing Session Replay in Grafana Cloud Frontend Observability](<https://devfeed.tech/articles/visual-playback-of-the-user-journey-introducing-session-replay-in-grafana-cloud-frontend-observability-8594.md>)

Original publisher: [Read original article](<https://grafana.com/blog/visual-playback-of-the-user-journey-introducing-session-replay-in-grafana-cloud-frontend-observability/>)

Author: Lukasz Gut

Published: 2026-09-12T11:22:06.456390Z

Content type: article

Language: en

Sources: [Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [session replay](<https://devfeed.tech/topics/session-replay.md>), [Grafana Cloud Frontend Observability](<https://devfeed.tech/topics/grafana-cloud-frontend-observability.md>), [Frontend observability](<https://devfeed.tech/topics/frontend-observability.md>), [Web app](<https://devfeed.tech/topics/webapp.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [SDK](<https://devfeed.tech/topics/sdk.md>)

Tags: [analytics](<https://devfeed.tech/tags/analytics.md>), [frontend-observability](<https://devfeed.tech/tags/frontend-observability.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-cloud-frontend-observability](<https://devfeed.tech/tags/grafana-cloud-frontend-observability.md>), [instrumentation](<https://devfeed.tech/tags/instrumentation.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [privacy](<https://devfeed.tech/tags/privacy.md>), [session-replay](<https://devfeed.tech/tags/session-replay.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>), [traces](<https://devfeed.tech/tags/traces.md>), [web-applications](<https://devfeed.tech/tags/web-applications.md>)

### AI overview

The article introduces Session Replay, a public-preview add-on for Grafana Cloud Frontend Observability. It visually reconstructs how a web application appeared and changed during a user session, linking that playback to session timelines and technical telemetry so engineering teams can investigate frontend problems more directly.

### Source excerpt

Grafana Cloud Frontend Observability helps engineering teams quantify the end user experience by bringing metrics, logs, traces, and user session context to client-side web applications. Teams can monitor application health and performance over time, triage errors, and correlate frontend signals with backend telemetry to investigate issues across the stack. Yet some of the hardest frontend problems remain difficult to diagnose. A support ticket might report that a checkout button did nothing, a form unexpectedly reset, or a workflow broke only in one browser or on one device. Metrics can reveal a performance regression, logs can capture an error, and traces can expose a slow request, but no single signal shows what the interface actually looked like to the user. This is exactly why we built Session Replay, an add-on feature in Frontend Observability that provides a visual reconstruction of a user's journey, connected to the telemetry Grafana Cloud already collects. It helps engineering teams move from a reported problem to seeing what happened and knowing exactly where to investigate next. What is Session Replay in Grafana Cloud Frontend Observability? Session Replay, now in public preview, adds visual playback capabilities to Frontend Observability. It reconstructs how a web application appeared and changed as a user navigated and interacted with it, so you can observe the journey as it unfolded instead of inferring it from individual telemetry events. Frontend Observability already brings together a chronological timeline of the events within a user session. That timeline tells you what happened and when. Session Replay adds the missing visual context: what was happening in the interface around those events and how one interaction led to the next. Because both views belong to the same session, you can move between the user experience and the relevant technical signals without losing the thread of your investigation. Session Replay builds on the Grafana Faro Web SD

## How groundcover rebuilt its dashboards to handle full fidelity observability

DevFeed: [How groundcover rebuilt its dashboards to handle full fidelity observability](<https://devfeed.tech/articles/the-dashboarding-journey-every-observability-startup-takes-79982.md>)

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

Author: Anais Dotis

Published: 2026-06-22T05:00:00Z

Content type: article

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>), [Frontend observability](<https://devfeed.tech/topics/frontend-observability.md>), [eBPF](<https://devfeed.tech/topics/ebpf.md>)

Tags: [dashboard](<https://devfeed.tech/tags/dashboard.md>), [observability](<https://devfeed.tech/tags/observability.md>), [performance](<https://devfeed.tech/tags/performance.md>), [scale](<https://devfeed.tech/tags/scale.md>), [scaling](<https://devfeed.tech/tags/scaling.md>)

### AI overview

groundcover describes replacing its SVG charting system with a hybrid canvas and SVG engine after dashboards struggled with large volumes of observability data. The team separated performance constraints around series count, point density, interactions, and chart correctness, then used canvas for high-cardinality data and SVG for tooltips and other interactive elements. The rewrite raised the practical series limit from 40 to 1,000, while some widget and backend query limitations remain.

### Source excerpt

Learn how groundcover evolved from off-the-shelf charting to a custom canvas-powered dashboard engine, overcoming scaling, performance, and correctness challenges to support full-fidelity observability at scale.

## You don't need to pick one: how Sentry and OpenTelemetry work together

DevFeed: [You don't need to pick one: how Sentry and OpenTelemetry work together](<https://devfeed.tech/articles/you-don-t-need-to-pick-one-how-sentry-and-opentelemetry-work-together-24110.md>)

Original publisher: [Read original article](<https://blog.sentry.io/sentry-opentelemetry-work-together/>)

Author: Lazar Nikolov

Published: 2026-05-27T00:00:00Z

Content type: article

Language: en

Sources: [Sentry](<https://devfeed.tech/sources/sentry-blog.md>)

Topics: [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [tracing](<https://devfeed.tech/topics/tracing.md>), [Frontend observability](<https://devfeed.tech/topics/frontend-observability.md>), [SDK](<https://devfeed.tech/topics/sdk.md>)

Tags: [apis](<https://devfeed.tech/tags/apis.md>), [application](<https://devfeed.tech/tags/application.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [backend](<https://devfeed.tech/tags/backend.md>), [browser](<https://devfeed.tech/tags/browser.md>), [collector](<https://devfeed.tech/tags/collector.md>), [context](<https://devfeed.tech/tags/context.md>), [events](<https://devfeed.tech/tags/events.md>), [export](<https://devfeed.tech/tags/export.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [instrumentation](<https://devfeed.tech/tags/instrumentation.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [opentelemetry-collector](<https://devfeed.tech/tags/opentelemetry-collector.md>), [option](<https://devfeed.tech/tags/option.md>), [otel](<https://devfeed.tech/tags/otel.md>), [parent](<https://devfeed.tech/tags/parent.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [sentry](<https://devfeed.tech/tags/sentry.md>)

### AI overview

Keep OpenTelemetry for existing backend instrumentation and use the Sentry SDK on the frontend for browser context such as tracing, errors, logs, Session Replay, and source maps. Configure the frontend SDK to send W3C trace headers so a browser action can continue as the parent of backend OpenTelemetry work. Backend OTLP events can go directly to Sentry's OTLP endpoint or through an OpenTelemetry Collector that forwards them. Sentry's OTLP ingest supports traces and logs, but not metrics at the time described.

### Source excerpt

Use Sentry on the frontend, keep OpenTelemetry on the backend, and choose direct OTLP or Collector forwarding for OTLP events.

## Introducing Automations

DevFeed: [Introducing Automations](<https://devfeed.tech/articles/introducing-automations-82715.md>)

Original publisher: [Read original article](<https://resend.com/blog/introducing-automations>)

Author: Carolina Josephik, Danilo Campos, Isabella Aquino, Lucas Motta, Vitor Capretz, and Zeno Rocha

Published: 2026-04-13T00:00:00Z

Content type: release

Language: en

Sources: [Resend](<https://devfeed.tech/sources/resend.md>)

Topics: [Event-Streaming](<https://devfeed.tech/topics/event-streaming.md>), [personalization](<https://devfeed.tech/topics/personalization.md>), [Frontend observability](<https://devfeed.tech/topics/frontend-observability.md>), [Val Town](<https://devfeed.tech/topics/val-town.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [lifecycle](<https://devfeed.tech/tags/lifecycle.md>), [personalization](<https://devfeed.tech/tags/personalization.md>), [product](<https://devfeed.tech/tags/product.md>), [real-time](<https://devfeed.tech/tags/real-time.md>), [triggers](<https://devfeed.tech/tags/triggers.md>)

### AI overview

Resend introduces Automations, which let teams build lifecycle email sequences triggered by application events. Sequences can be designed visually or with natural-language AI assistance, use conditions and existing templates, and run through the dashboard, API, SDKs, MCP Server, or CLI. The observability panel tracks runs in real time, and the feature includes 10,000 free Automation Runs.

### Source excerpt

Set up lifecycle messages and drip campaigns with triggers, personalization, and real-time observability.

## Elastic named a Leader in the IDC MarketScape: Worldwide Observability Platforms 2025 Vendor Assessment

DevFeed: [Elastic named a Leader in the IDC MarketScape: Worldwide Observability Platforms 2025 Vendor Assessment](<https://devfeed.tech/articles/elastic-named-a-leader-in-the-idc-marketscape-worldwide-observability-platforms-2025-vendor-assessment-134084.md>)

Original publisher: [Read original article](<https://www.elastic.co/blog/elastic-observability-idc-marketscape-leader-2025>)

Author: Natalie Blake

Published: 2025-11-14T21:09:30Z

Content type: release

Language: en

Sources: [Elastic Blog](<https://devfeed.tech/sources/elastic-blog-elasticsearch-kibana-and-elk-stack.md>)

Topics: [observability](<https://devfeed.tech/topics/observability.md>), [Logging](<https://devfeed.tech/topics/logging.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [Elastic Cloud](<https://devfeed.tech/topics/elastic-cloud.md>), [Frontend observability](<https://devfeed.tech/topics/frontend-observability.md>), [tracing](<https://devfeed.tech/topics/tracing.md>), [LLM observability](<https://devfeed.tech/topics/llm-observability.md>), [Machine learning](<https://devfeed.tech/topics/machine-learning.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [aiops-log-monitoring-log-management-opentelemetry](<https://devfeed.tech/tags/aiops-log-monitoring-log-management-opentelemetry.md>), [apm-log-analytics-observability](<https://devfeed.tech/tags/apm-log-analytics-observability.md>), [assessment](<https://devfeed.tech/tags/assessment.md>), [elastic](<https://devfeed.tech/tags/elastic.md>), [idc](<https://devfeed.tech/tags/idc.md>), [leader](<https://devfeed.tech/tags/leader.md>), [logs](<https://devfeed.tech/tags/logs.md>), [observability](<https://devfeed.tech/tags/observability.md>)

### AI overview

Elastic says it was named a Leader in the IDC MarketScape: Worldwide Observability Platforms 2025 Vendor Assessment (November 2025). The post attributes the recognition to native OpenTelemetry support and EDOT, scalable telemetry processing, correlation of backend traces with frontend experience and business metrics, and centralized governance controls. It also presents Streams as a way to send logs in varied formats to Elastic, use AI to parse and structure them, and surface "Significant Events" to guide investigations. The post describes these as reducing pipeline work and investigation complexity, while claiming lower storage costs; it does not provide comparative measurements for Streams. Other cited innovations include Elastic AI Assistant, serverless cloud storage, LLM observability, and Elasticsearch logsdb. The recognition and product benefits are presented by Elastic, and the post notes that feature availability and timing are at Elastic's discretion.

### Source excerpt

Elastic is a Leader in the IDC MarketScape: Worldwide Observability Platforms 2025 Vendor Assessment. Learn why Elastic was recognized in the report.

## How groundcover Reimagined Querying Across All Data Types

DevFeed: [How groundcover Reimagined Querying Across All Data Types](<https://devfeed.tech/articles/how-groundcover-reimagined-querying-across-all-data-types-80103.md>)

Original publisher: [Read original article](<https://www.groundcover.com/blog/the-framework-behind-the-query-language>)

Author: Amir Sheffer

Published: 2025-11-12T00:00:00Z

Content type: article

Language: en

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

Topics: [Frontend observability](<https://devfeed.tech/topics/frontend-observability.md>), [data](<https://devfeed.tech/topics/data.md>), [database-optimization](<https://devfeed.tech/topics/database-optimization.md>)

Tags: [backend](<https://devfeed.tech/tags/backend.md>), [designing](<https://devfeed.tech/tags/designing.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [groundcover](<https://devfeed.tech/tags/groundcover.md>), [observability](<https://devfeed.tech/tags/observability.md>)

### AI overview

Groundcover describes redesigning its query framework while building a migration tool from legacy observability vendors. It chose MetricsQL for metrics and created a middleware query language for logs, traces, and events, with a frontend compiler/parser and a query builder that supports builder and code modes. The company says the framework supports dashboards and monitors and is being explored for RUM analytics and security use cases.

### Source excerpt

Learn how groundcover redesigned data querying to create a unified, efficient framework that simplifies working across all observability signals.

## Frontend Observability with Real User Monitoring (RUM)

DevFeed: [Frontend Observability with Real User Monitoring (RUM)](<https://devfeed.tech/articles/frontend-observability-with-real-user-monitoring-rum-80095.md>)

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

Author: Gilles Perez

Published: 2025-03-31T00:00: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>), [Frontend observability](<https://devfeed.tech/topics/frontend-observability.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [observability](<https://devfeed.tech/topics/observability.md>), [session replay](<https://devfeed.tech/topics/session-replay.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [bring-your-own-cloud](<https://devfeed.tech/tags/bring-your-own-cloud.md>), [dashboards](<https://devfeed.tech/tags/dashboards.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [devops](<https://devfeed.tech/tags/devops.md>), [frontend-observability](<https://devfeed.tech/tags/frontend-observability.md>), [groundcover](<https://devfeed.tech/tags/groundcover.md>), [instrumentation](<https://devfeed.tech/tags/instrumentation.md>), [observability](<https://devfeed.tech/tags/observability.md>), [real-user-monitoring](<https://devfeed.tech/tags/real-user-monitoring.md>)

### AI overview

Groundcover introduces Real User Monitoring (RUM) as an addition to its observability platform, collecting browser interactions, performance metrics, errors, and session context through a JavaScript SDK. The article describes integrating this frontend data with backend telemetry and says its BYOC deployment keeps the data in customers' environments.

### Source excerpt

Discover groundcover's Real User Monitoring (RUM) and how our BYOC architecture enables deeper frontend visibility with zero-instrumentation overhead.

## Guide to K8s Container Events: Tracking, Errors & Collection

DevFeed: [Guide to K8s Container Events: Tracking, Errors & Collection](<https://devfeed.tech/articles/guide-to-k8s-container-events-tracking-errors-collection-80018.md>)

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

Author: Max Levin

Published: 2022-06-22T00:00:00Z

Content type: tutorial

Language: en

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

Topics: [CrashLoopBackOff troubleshooting](<https://devfeed.tech/topics/crashloopbackoff-troubleshooting.md>), [Frontend observability](<https://devfeed.tech/topics/frontend-observability.md>), [Logging](<https://devfeed.tech/topics/logging.md>)

Tags: [container](<https://devfeed.tech/tags/container.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [events](<https://devfeed.tech/tags/events.md>), [k8s](<https://devfeed.tech/tags/k8s.md>)

### AI overview

This guide explains how Kubernetes represents Pod and container states, how to investigate failed starts, and why exit codes alone may not reveal the cause of a termination. It describes watching Pod updates, comparing container status and restart counters, and collecting termination details to create richer restart signals for monitoring and debugging.

### Source excerpt

Learn how to manage Kubernetes container events from tracking to errors. Use our essential guide to optimize Kubernetes container event management.

## The Web Performance Impact Of Lossy Network Conditions

DevFeed: [The Web Performance Impact Of Lossy Network Conditions](<https://devfeed.tech/articles/the-web-performance-impact-of-lossy-network-conditions-27974.md>)

Original publisher: [Read original article](<https://tech.trivago.com/post/2019-08-08-thewebperformanceimpactoflossynetworkcon/>)

Author: Tobias Baldauf

Published: 2019-08-08T00:00:00Z

Content type: article

Language: en

Sources: [Trivago](<https://devfeed.tech/sources/trivago.md>)

Topics: [Latency](<https://devfeed.tech/topics/latency.md>), [network device monitoring](<https://devfeed.tech/topics/network-device-monitoring.md>), [User Experience](<https://devfeed.tech/topics/user-experience.md>), [synthetic monitoring](<https://devfeed.tech/topics/synthetic-monitoring.md>), [Monitoring & Alerting](<https://devfeed.tech/topics/monitoring-alerting.md>), [network troubleshooting commands](<https://devfeed.tech/topics/network-troubleshooting-commands.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>), [Frontend observability](<https://devfeed.tech/topics/frontend-observability.md>), [Web](<https://devfeed.tech/topics/web.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>)

Tags: [alerting](<https://devfeed.tech/tags/alerting.md>), [api](<https://devfeed.tech/tags/api.md>), [arq](<https://devfeed.tech/tags/arq.md>), [automatic-repeat-request](<https://devfeed.tech/tags/automatic-repeat-request.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [bounce](<https://devfeed.tech/tags/bounce.md>), [business](<https://devfeed.tech/tags/business.md>), [cdn](<https://devfeed.tech/tags/cdn.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-regions](<https://devfeed.tech/tags/cloud-regions.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [dns](<https://devfeed.tech/tags/dns.md>), [extensions](<https://devfeed.tech/tags/extensions.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [middleware](<https://devfeed.tech/tags/middleware.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [network](<https://devfeed.tech/tags/network.md>), [performance](<https://devfeed.tech/tags/performance.md>), [servers](<https://devfeed.tech/tags/servers.md>), [user-experience](<https://devfeed.tech/tags/user-experience.md>), [web](<https://devfeed.tech/tags/web.md>), [web-performance](<https://devfeed.tech/tags/web-performance.md>)

### AI overview

During a cloud-service rollout, one region showed slower API responses, more user bounces, intermittent origin unreachability, and negative business metrics even though routine Synthetic and Real User Monitoring missed the outages. High-frequency object tests exposed intermittent failures; MTR tracing then found 10%-100% packet loss on middleware routers between the CDN and origin. The excerpt attributes slower responses to TCP retransmissions, while DNS and successful-connection "Connect" and "Receive" measurements appeared unaffected. Tests excluding failed connections still showed users waited about twice as long for responses, with "Wait" time rising by over 300 ms. The team worked with its CDN vendor to contact the responsible ISP, which did not respond, then mitigated the problem by routing CDN-to-origin traffic over IPv6, where tests found the unhealthy IPv4 hardware was not involved.

### Source excerpt

tl;dr: continuously monitor your CDN and origin servers on layer 3 with tools like MTR. Layer 3 issues on external middleware can have ...

## Logging Javascript errors in production

DevFeed: [Logging Javascript errors in production](<https://devfeed.tech/articles/logging-javascript-errors-in-production-19999.md>)

Original publisher: [Read original article](<http://engineering.hackerearth.com/2016/01/29/hackerearth-logging-javascript-errors-production/>)

Published: 2016-01-29T00:00:00Z

Content type: tutorial

Language: en

Sources: [HackerEarth](<https://devfeed.tech/sources/hackerearth.md>)

Topics: [Frontend observability](<https://devfeed.tech/topics/frontend-observability.md>), [Cross-origin resource sharing (CORS)](<https://devfeed.tech/topics/cors.md>), [Logging](<https://devfeed.tech/topics/logging.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [browser](<https://devfeed.tech/topics/browser.md>)

Tags: [aws](<https://devfeed.tech/tags/aws.md>), [aws-s3](<https://devfeed.tech/tags/aws-s3.md>), [cors](<https://devfeed.tech/tags/cors.md>), [errors](<https://devfeed.tech/tags/errors.md>), [fastly](<https://devfeed.tech/tags/fastly.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [logging](<https://devfeed.tech/tags/logging.md>), [production](<https://devfeed.tech/tags/production.md>)

### AI overview

The article reports that Errorception could not capture useful stack traces for JavaScript served from S3 through Fastly because the cross-origin scripts lacked CORS headers. The authors enabled CORS on the S3 bucket with a GET rule and on Fastly with an Access-Control-Allow-Origin header, added crossorigin="anonymous" to script tags, and changed JavaScript asset versions to clear caches. They describe checking the resulting headers with curl. The supplied text presents this as their implementation experience; it does not establish whether the configuration is suitable for other setups.

### Source excerpt

We had implemented a javascript logger to capture the pesky issues our users faced and had problems when using the site. When we came up with the idea, we thought it would be just a five minute job where we would just have to add a snippet and would be done, but as it is well know, nothing is simple when it comes to real world production issues. After analyzing a lot of loggers, we decided to use errorception as our javascript logger. It was simple in its approach and it provided the data we needed. This was the easy part, next came the part of integration, and yes there was a snippet which we just had to paste in our base javascript file, but one thing we had forgotten, CORS. We host our static files on S3 and they are served via fastly, because of which they are delivered through another domain. The error tracking snippet could not log the errors because 'window.onerror' would not return the necessary stack trace and information. Many of you may have heard about CORS, it is a mechanism that allows restricted resources (e.g. fonts) on a web page to be requested from another domain outside the domain from which the resource originated. For security reasons, browsers restrict cross-origin HTTP requests initiated from within scripts. The only way to solve this and get errors to be posted to errorception was to allow CORS in the header of the static files. After some research (errorception also has a good blog on it), we finally managed to have the error logging implemented. Below are the steps we had to go through: Configuring S3 S3 has this unnecessarily complicated "CORS configuration" that you need to create. Here's the steps to get that right: Log into your AWS S3 console, select your bucket, and select "Properties". S3 CORS configurations seem to apply at the level of the bucket, and not the file. I have no clue why. Expand the "Permissions" pane, and click on "Add CORS configuration" or "Edit CORS configuration" depending on what you see. You should already be p