[Meta] Lens migration phase 4

[milan-elastic]

The initiative to migrate visualizations from TSVB to Lens was launched in the 8.8 release. This migration's first, second and third phases focused on prioritizing critical service, and cloud integrations. The list of phases can be found in below tracker issue:

Phases and issues tracker #6489

Continuing with our efforts in the same direction, the goal of Lens Migration Phase 4 is to migrate key Cloud-native Integrations. This issue describes the tasks to be accomplished in this phase.

• Creating a Migrations Check List
• Migrations Status

Confirmed Integrations:

Completed Integrations:

• Kubernetes [O11y][Kubernetes] Kubernetes Lens migration #7774
• Nats [O11y][Nats] Nats Lens migration #7777
• Containerd [O11y][ContainerD] ContainerD Lens migration #8057
• docker [O11y][Docker] Docker Lens migration #7775
• Prometheus [O11y][Prometheus] Prometheus Lens migration #7776
• Nginx Ingress Controller [O11y][Nginx Ingress controller] Nginx Ingress controller Lens migration #7812
• Stan [O11y][Stan] Stan Lens migration #7778
• Windows [O11y][Windows] Windows Lens migration #8161

Blocker issues

• [O11y][STAN] Could not find reference error in STAN Metrics overview dashboard #7916
• [Lens] Add IP range function kibana#135883

[kush-elastic]

Upon consultation with @SubhrataK, we have opted to migrate only the following data streams as part of the Windows Lens migration process:

• Service
• Performance Monitoring (perfmon)

[rajvi-patel-22]

All mentioned integration are migrated to lens therefore closing this issue.