[Lens Migration] Migrate visualizations for Cassandra, CouchBase, Oracle WebLogic and Salesforce to lens

[kush-elastic]

• Enhancement

What does this PR do?

• Migrate visualizations to lens for following integrations:
  • Cassandra
  • CouchBase
  • Oracle WebLogic
  • Salesforce

Below are the statistics for Cassandra Lens migration:

	Before Migration		After Migration
	Lens	Visualization	Lens	Visualization
[Metrics Cassandra] Overview	0	18	2	16
[Logs Cassandra] System Logs	0	2	1	1
	0	20	3	17

Below are the statistics for CouchBase Lens migration:

	Before Migration		After Migration
	Lens	Visualization	Lens	Visualization
[Metrics Couchbase] Sync Gateway Overview	18	0	18	0
[Metrics Couchbase] Node Overview	0	4	4	0
[Metrics Couchbase] Metrics Overview	0	7	7	0
[Metrics Couchbase] XDCR Overview	7	0	7	0
	25	11	36	0

Below are the statistics for Oracle WebLogic Lens migration:

	Before Migration		After Migration
	Lens	Visualization	Lens	Visualization
[Metrics Oracle WebLogic] Deployed Application	5	2	7	0
[Logs Oracle WebLogic] Logs Overview	3	8	6	5
[Metrics Oracle WebLogic] ThreadPool	8	1	9	0
	16	11	22	5

Below are the statistics for Salesforce Lens migration:

	Before Migration		After Migration		Notes
	Lens	Visualization	Lens	Visualization
[Logs Salesforce] Login Dashboard	9	1	10	0
[Logs Salesforce] Apex Dashboard	11	2	12	1	Timelion chart
[Logs Salesforce] Logout Dashboard	4	1	5	0
[Logs Salesforce] Setup Audit Trail Dashboard	4	0	4	0
	28	4	31	1

Checklist

• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that panels are populated with data.
• I have verified that panels are not distorted after being migrated to lens.
• I have updated screenshots of dashboard.
• I have verified that data count are matching and panel aggregations are same as before.

Author's Checklist

• I have added an entry to my package's changelog.yml file.
• I have verified an Kibana version is set to ^8.6.0.
• Migrated panels should be removed from visualization folder.

Related issues

• Relates Lens Migration of OBS integrations #5221

Known issues

• Input Controls visualization is deprecated in Kibana and many of the dashboards contain these visualizations. Also, support for Input Controls has been stopped because of the new Input Controls. Hence, to replicate dashboard-level filters old Input Controls are replaced with new ones.
• Split chart functionality is not supported in Lens. [https://github.com/[Lens] Support for multiple breakdown by kibana#82208]
• While migrating the visualizations from TSVB to the lens, the colors are getting default ones instead of the configured ones.
• In the lens migrated metric visualizations, values are displayed in the bottom right corner. [https://github.com/[Lens] Add metric Viz config options, title position and sizing kibana#124124#discussion_r804476235]
• Panel titles are not displayed in lens metric visualization for Kibana 8.6.x version. [https://github.com/[Lens] Hide the edit panel title for new metric visualizations kibana#148563]
• Pie or Donut charts that have more than three slices are not supported in Lens.

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-02-17T09:03:27.883+0000

• Duration: 26 min 12 sec

Test stats 🧪

Test	Results
Failed	0
Passed	131
Skipped	0
Total	131

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (19/19)	💚
Files	100.0% (19/19)	💚
Classes	100.0% (19/19)	💚
Methods	100.0% (178/178)	💚
Lines	98.449% (2349/2386)	👍 2.206
Conditionals	100.0% (0/0)	💚

[kush-elastic]

/test

[botelastic]

Hi! We just realized that we haven't looked into this PR in a while. We're sorry! We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!

[botelastic]

Hi! This PR has been stale for a while and we're going to close it as part of our cleanup procedure. We appreciate your contribution and would like to apologize if we have not been able to review it, due to the current heavy load of the team. Feel free to re-open this PR if you think it should stay open and is worth rebasing. Thank you for your contribution!