Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[O11y][Oracle WebLogic] Lens Migration #5547

Closed
10 tasks done
harnish-elastic opened this issue Mar 15, 2023 · 4 comments
Closed
10 tasks done

[O11y][Oracle WebLogic] Lens Migration #5547

harnish-elastic opened this issue Mar 15, 2023 · 4 comments
Assignees

Comments

@harnish-elastic
Copy link
Contributor

harnish-elastic commented Mar 15, 2023

Manually migrate Oracle WebLogic visualizations to lens in kibana version 8.4.0.

Preparation of data for testing

  • Use sample_event.json / setup live instance using docker / mock data using mock server to populate dashboards

Migration stats

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

Data stream : Deployed Application

Data stream : ThreadPool

Data stream : Admin Server

Data stream : Managed Server

Data stream : Access

Data stream : Domain

Verification and Validation

  • Verification of functionality remains the same after migration in kibana
  • Verification of data count of after-migrated visualization with before-migrated visualization in kibana
  • Verification of Dashboard are not distorted in supported kibana version (8.4.0)

Related Issues

@agithomas
Copy link
Contributor

What is the reason why 4 viz are not migrated to Lens?

@harnish-elastic
Copy link
Contributor Author

harnish-elastic commented Mar 17, 2023

What is the reason why 4 viz are not migrated to Lens?

Those 4 are markdown visualizations which is already mentioned in the PR itself.

@agithomas
Copy link
Contributor

@harnish-elastic , i recommend you to create smaller PRs going forward - preferably one or two (max) PR / datastream.

@kush-elastic
Copy link
Collaborator

PR is approved and merged, hence closing this issue: #5548

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants