✨ RUM Browser Angular Integration

[rgaignault]

What does this PR do?

Updates the Angular integration tile with documentation for the new @datadog/browser-rum-angular plugin, covering error tracking and router integration.

Motivation

The @datadog/browser-rum-angular package is being released with two features:

• Error handling: provideDatadogErrorHandler() and addAngularError() — browser-sdk#4315
• Router integration: provideDatadogRouter() — browser-sdk#4358

The existing Angular tile only had generic RUM/logs/traces links. This PR adds plugin-specific documentation following the same structure as the React integration.

Review checklist

• PR has a meaningful title or PR has the no-changelog label attached
• Feature or bugfix has tests
• Git history is clean
• If PR impacts documentation, docs team has been notified or an issue has been opened on the documentation repo

[rtrieu]

Created DOCS-13971 for editorial review.

[iadjivon]

Hi there,
Thanks for your patience here!
I've added a couple of suggestions and recommendation.
Approved as to not be a blocker on this, but recommend reviewing the suggestions. Thanks so much and please let me know if you have any questions!

[cit-pr-commenter-54b7da]

Monitor Template Quality Assessment

52 monitors analyzed across 9 integrations.

• 34 monitors have missing sections
• Most common missing sections: WHY, IMPACT, HOW_TO_TROUBLESHOOT

Monitors with missing sections

Integration	Monitor	Missing Sections	Suggested Links
kubernetes	[Kubernetes] Monitor Kubernetes Deployments Replica Pods	IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS	- Logs

• Infrastructure
• Metrics Explorer (kubernetes_state.deployment.replicas_desired)
• Metrics Explorer (kubernetes_state.deployment.replicas_available) |
  | kubernetes | [Kubernetes] Monitor Unschedulable Kubernetes Nodes | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Logs
• Infrastructure
• Metrics Explorer (kubernetes_state.node.status) |
  | kubernetes | [Kubernetes] Pod {{pod_name.name}} is CrashloopBackOff on namespace {{kube_namespace.name}} | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Logs
• Infrastructure
• Metrics Explorer (kubernetes_state.container.status_report.count.waiting) |
  | kubernetes | [Kubernetes] Pod {{pod_name.name}} is ImagePullBackOff on namespace {{kube_namespace.name}} | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Logs
• Infrastructure
• Metrics Explorer (kubernetes_state.container.status_report.count.waiting) |
  | kubernetes | [Kubernetes] Pod {{pod_name.name}} is OOMKilled on namespace {{kube_namespace.name}} | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Logs
• Infrastructure
• Metrics Explorer (kubernetes.containers.state.terminated) |
  | kubernetes | [Kubernetes] Monitor Kubernetes Failed Pods in Namespaces | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Logs
• Infrastructure
• Metrics Explorer (kubernetes_state.pod.status_phase) |
  | kubernetes | [Kubernetes] Monitor Kubernetes Pods Restarting | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Logs
• Infrastructure
• Metrics Explorer (kubernetes.containers.restarts) |
  | kubernetes | [Kubernetes] Monitor Kubernetes Statefulset Replicas | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Logs
• Infrastructure
• Metrics Explorer (kubernetes_state.statefulset.replicas_desired)
• Metrics Explorer (kubernetes_state.statefulset.replicas_ready) |
  | nginx | [NGINX] 5xx Errors higher than usual | WHY | - Logs
• Infrastructure
• Metrics Explorer (nginx.upstream.peers.responses.5xx) |
  | nginx | [NGINX] Upstream peers fails | WHY | - Logs
• Infrastructure
• Metrics Explorer (nginx.stream.upstream.peers.fails) |
  | postgres | [Postgres] Number of connections is approaching connection limit on {{host.name}} | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Metrics Explorer (postgresql.percent_usage_connections) |
  | postgres | [Postgres] Replication delay is abnormally high on {{host.name}} | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Metrics Explorer (postgresql.replication_delay) |
  | redis | [Redis] High memory consumption | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Metrics Explorer (redis.mem.used)
• Metrics Explorer (redis.mem.maxmemory) |
  | amazon-rds | [AWS] RDS CPU utilization is high | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Logs
• Infrastructure
• Metrics Explorer (aws.rds.cpuutilization) |
  | amazon-rds | [AWS] RDS Anomaly in database connections | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Logs
• Infrastructure
• Metrics Explorer (aws.rds.database_connections) |
  | amazon-rds | [AWS] RDS Storage utilization is high | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Logs
• Infrastructure
• Metrics Explorer (aws.rds.free_storage_space)
• Metrics Explorer (aws.rds.total_storage_space) |
  | amazon-sqs | Queue {{queuename.name}} has a high age of oldest message | WHY | - Logs
• Infrastructure
• Metrics Explorer (aws.sqs.approximate_age_of_oldest_message) |
  | apm | Abnormal change in p75 latency for $service.value on $env | WHATS_HAPPENING, IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | no metrics found in query |
  | apm | Watchdog Anomaly: {{event.title}} for {{service}} | WHATS_HAPPENING, IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | Monitor type is not supported for message generation: event-v2 alert |
  | apm | New issues found for $service on $env | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | no metrics found in query |
  | apm | High p95 latency for $service on $env | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | no metrics found in query |
  | apm | Abnormal change in Apdex for $service.value on $env | WHATS_HAPPENING, IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | no metrics found in query |
  | apm | Low traffic on $service on $env | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | no metrics found in query |
  | apm | New issues found for {{service}} on {{env}} | WHATS_HAPPENING, IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | Monitor type is not supported for message generation: error-tracking alert |
  | apm | No data for $service.value on $env | WHATS_HAPPENING, IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | no metrics found in query |
  | apm | Increased error rate for $service.value in $env | WHATS_HAPPENING, IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | no metrics found in query |
  | real-user-monitoring | Cumulative Layout Shift is high for view {{[view.name].name}} | WHY | Unhandled exception while parsing message: parsing metric query failed: Rule 'or_op' didn't match at '.name} by {view.name' (line 1, column 47). |
  | real-user-monitoring | View Error Rate is high for view {{[view.name].name}} | WHY | Unhandled exception while parsing message: parsing metric query failed: Rule 'or_op' didn't match at '.name} by {view.name' (line 1, column 53). |
  | real-user-monitoring | Largest Contentful Paint is high for view {{[view.name].name}} | WHY | Unhandled exception while parsing message: parsing metric query failed: Rule 'or_op' didn't match at '.name} by {view.name' (line 1, column 48). |
  | real-user-monitoring | ANR Rate is high | WHY | Unhandled exception while parsing message: parsing metric query failed: Rule 'or_op' didn't match at '.name}.as_count() / ' (line 1, column 29). |
  | system | CPU usage is high for host {{host.name}} | WHY | - Logs
• Infrastructure
• Metrics Explorer (system.cpu.idle) |
  | system | Disk latency is high for host {{host.name}} on device {{device.name}} | WHY | - Logs
• Infrastructure
• Metrics Explorer (system.io.await) |
  | system | Network traffic (sent) is high on host {{host.name}} | WHY | - Logs
• Infrastructure
• Metrics Explorer (system.net.bytes_sent) |
  | system | Host $host.value not reporting data | WHATS_HAPPENING, IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | Monitor type is not supported for message generation: service check |

[rgaignault]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-04-22 12:06:32 UTC ℹ️ Start processing command /merge

---

2026-04-22 12:06:39 UTC ℹ️ MergeQueue: waiting for PR to be ready

This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
It will be added to the queue as soon as checks pass and/or get approvals. View in MergeQueue UI.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

---

2026-04-22 12:07:08 UTC ⚠️ MergeQueue: This merge request was unqueued

roman.gaignault@datadoghq.com unqueued this merge request

[rgaignault]

/merge -c

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-04-22 12:07:02 UTC ℹ️ Start processing command /merge -c