This is the issue that tracks the preliminary list of integrations that will be migrated to Lens from an infrastructure observability perspective. There is a list of phases for this lens migration work, it can be found from below tracker issue:

Phases and issues tracker #6489

Issue tracking the Lens Migration from obs service integrations.

Completed Integrations

• HAproxy [O11y][HAProxy] Lens Migration #5584
• Kafka [O11y][Kafka] Lens Migration #5591
• MySQL [O11y][MySQL] Lens Migration #5709
• Oracle [O11y][Oracle] Lens Migration #5753
• WebSphere Application Server [O11y][WebSphere Application Server] Lens Migration #5575
• CoreDNS [O11y][CoreDNS] Lens Migration #5708
• IIS [O11y][IIS] Lens Migration #5707
• Apache Spark [O11y][Apache Spark] Lens Migration #5491
• ActiveMQ [O11y][ActiveMQ] Lens Migration #5516
• Cassandra [O11y][Cassandra] Lens Migration #5672
• Citrix ADC [O11y][Citrix ADC] Lens Migration #5562 (Not relevant. All viz in lens already)
• Couchbase [O11y][Couchbase] Lens Migration #5609
• CouchDB [O11y][CouchDB] Lens Migration #5564
• Hadoop [O11y][Hadoop] Lens Migration #5504
• IBM MQ [O11y][IBM MQ] Lens Migration #5494
• Nagios XI [O11y][Nagios XI] Lens Migration  #5567
• Oracle WebLogic [O11y][Oracle WebLogic] Lens Migration #5547
• PHP-FPM [O11y][PHP-FPM] Lens Migration #5520
• Salesforce [O11y][Salesforce] Lens Migration #5579
• Spring Boot [O11y][Spring Boot] Lens Migration #5529
• Apache [O11y][Apache] Lens Migration #5608
  • Validate the changes in the PR is taken care.
• CockroachDB [O11y][CockroachDB] Lens Migration #5543
• etcd [O11y][ETCD] Lens Migration #5542
• InfluxDB [O11y][InfluxDb] Lens Migration #5505
• Memcached [O11y][Memcached] Lens Migration #5563 (Not relevant. All viz in lens already)
• MongoDB [O11y][MongoDB] Lens Migration #5541
• Microsoft SQL Server [O11y][Microsoft SQL Server] Lens Migration  #5710
• PostgreSQL [O11y][PostgreSQL] Lens Migration #5701
• Nginx [O11y][Nginx] Lens Migration  #5713
• RabbitMQ [O11y][RabbitMQ] Lens migration #5535
• Redis [O11y][Redis] Lens Migration #5583
• Redis Enterprise [O11y][Redis Enterprise] Lens Migration  #5674
• Traefik [O11y][Traefik] Lens Migration #5692
• Vsphere [O11y][Vsphere] Lens Migration #5676
• Zookeeper [O11y][ZooKeeper] Lens Migration #5690

Issues Identified

Lens/Kibana Issues

• Lens doesn't support number formatting. (For example 20000 -> 20k)
  [Lens] Add more number format options kibana#72711
  • Impact : [ Severity : Blocker, Workaround : No ]
• Not able to convert value into human readable format ( Seconds / Minutes / Hours )
  [Lens] Support the duration formatter kibana#153378
  • Impact : [ Severity : Blocker, Workaround : No ]
  • Comment : Kibana team has provided the workaround. We tried the solution and discussed it with @SubhrataK but it was not user-friendly. So we have provided this comment and asked the kibana team to provide this feature in the lens.
• The text type field is not supported in table type visualizations of Lens.
  Lens only shows keyword fields, not text fields kibana#96576
  • Impact : [ Severity : Blocker, Workaround : No]
  • Comment : As discussed with @agithomas, removing the text field is not the idle option. Hence we will keep the visualization as it is.
• Not having feature to set last bucket value
  [Lens] Not having feature to set last bucket value kibana#153326
  • Impact : [ Severity : Critical, Workaround : Yes ]
  • Comment : As discussed with @SubhrataK for this issue, we are good with the metrics chart to convert into the lens. If metrics charts contains differences which uses the date histogram we can convert them to line charts.
• The TagCloud visualizations are not supported in the lens.
  [Lens] Add word cloud support kibana#95542
  • Impact : [ Severity : Critical, Workaround : Yes (Create horizontal bar chart[reference]])
  • Comment : As per this comment, we have converted tag cloud visualization to horizontal bar chart
• Splitting a chart into multiple smaller charts by a breakdown dimension is not supported in the lens.
  [Lens] Support small multiples / facet / trellis for XY and Partition charts kibana#72063
  • Impact : [ Severity : Critical, Workaround : Yes(Convert to table chart)]
  • Comment : As discussed with @SubhrataK, we have converted split chart to table chart.
• Facing issue related to aggregation based gauge chart to lens gauge chart while migrating.
  [Lens Gauge chart] Gauge chart is not showing value if it exceeds than the provided limit like aggregation based gauge chart kibana#153010
  • Impact : [ Severity : Major, Workaround : Yes (Converting gauge to metric)]
  • Comment : As discussed with @SubhrataK,, we can convert gauge charts to metric. Also Kibana team will work on gauge charts as per this comment
• Gradient and rainbow color palettes are not available in lens and won't be available in the future versions as well. Hence, the closest color palettes (positive and negative) have been used.
  [Lens] Support for Gradient and Rainbow color palette in Lens kibana#152699
  • Impact : [ Severity : Low, Workaround : Yes (Use alternative color palettes)]
  • Comment : As discussed with @agithomas, we will keep the closest color palettes while doing the lens migration.
• TSVB visualization doesn’t show negative values in UI. But the lens shows both negative and positive values. (This will be fixed in 8.8)
  The chart do not render negative values elastic-charts#135
  • Impact : [ Severity : Low, Workaround : This will be fixed in 8.8 ]
  • Comment : This has been identified as a better functionality. In lens user can see both values negative and positive.
• Support multiple metrics in one chart using lens
  [Lens] Support multiple metrics in one chart using lens kibana#153324
  • Impact : [ Severity : Low, Workaround : Yes (Convert into multiple metrics chart) ]
  • Comment : We are able to convert this visualization to single metric charts. So as a workaround, we have converted into single metrics charts.
• In input control visualization, we can make dependency filters that strictly depend on each other but in new controls, dependency filtering is possible but filters are not required to be strict. As per the comment, this is the expected behavior of new controls.
  • Impact : [ Severity : Low, Workaround : No (Expected Behaviour) ]

Integration Issues

• Kafka Update layout of dashboards
  [O11y][Kafka] Update layout of dashboards #7148
• CoreDNS dashboard visualizations are showing error
  [O11y][CoreDNS] Visualizations are showing error #5518
  • Impact : [ Severity : Critical, Workaround : No ]
• The InfluxDB dashboard panel contains an error.
  [InfluxDB] Shard disk size panel from Status metrics dashboard contains error #5506
  • Impact : [ Severity : Critical, Workaround : No]
• SpringBoot dashboards contains meta field (_id)
  [O11y][SpringBoot] Update _id field in SpringBoot dashboard #5871
  • Impact : [ Severity : Critical, Workaround : As mentioned in the documentation of _id, the content of _id field can be copied in another field using ingest pipeline and the new field can be used in visualizations.]

  Note: When user will upgrade to the newer version, spring_boot.audit_events.document_id field will be added only to the new incoming documents. The data that is already present in indices will not get updated. Hence, the Audit Events [Logs Spring Boot] visualization will show documents which have spring_boot.audit_events.document_id field present (documents that have been ingested after upgrading to the latest version). Reindexing can be recommended in case the user wish to see the old information following the change (adoption of document_id) as the new field to store the values presently stored under _id. Please refer to the troubleshooting section of README.

• Salesforce dashboards contains meta field (_id)
  [O11y][Salesforce] Update _id field in Salesforce dashboard #5876
  • Impact : [ Severity : Critical, Workaround : As mentioned in the documentation of _id, the content of _id field can be copied in another field using ingest pipeline and the new field can be used in visualizations.]

  Note: When user will upgrade to the newer version, salesforce.login.document_id field will be added only to the new incoming documents. The data that is already present in indices will not get updated. Hence, the Changes made in the setup [Logs Salesforce] visualization will show documents which have salesforce.login.document_id field present (documents that have been ingested after upgrading to the latest version). Reindexing can be recommended in case the user wish to see the old information following the change (adoption of document_id) as the new field to store the values presently stored under _id. Please refer to the troubleshooting section of README.(https://github.com/elastic/integrations/tree/main/packages/salesforce#readme).

Migration stats

Backlog