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][ActiveMQ] Lens Migration #5516

Closed
9 tasks done
rajvi-patel-22 opened this issue Mar 13, 2023 · 6 comments
Closed
9 tasks done

[O11y][ActiveMQ] Lens Migration #5516

rajvi-patel-22 opened this issue Mar 13, 2023 · 6 comments
Assignees

Comments

@rajvi-patel-22
Copy link
Contributor

rajvi-patel-22 commented Mar 13, 2023

Manually migrate ActiveMQ visualizations to lens in current Kibana version 8.2.0 itself.

Preparation of data for testing

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

Migration stats

  Before Migration   After Migration  
  Lens Visualization Lens Visualization
[Logs ActiveMQ] Audit 0 2 2 0
[Logs ActiveMQ] Broker 0 6 6 0
[Logs ActiveMQ] Log 0 2 2 0
[Logs ActiveMQ] Queues 0 8 8 0
[Logs ActiveMQ] Topics 0 8 8 0
  0 26 26 0

Data stream: Audit

Data stream : Broker

Data stream : Log

Data stream : Queue

Data stream : Topic

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.2.0)

Issues Identified

@rajvi-patel-22
Copy link
Contributor Author

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

@agithomas
Copy link
Contributor

@rajvi-elastic , I do not fully understand the issue

"Splitting a chart into multiple smaller charts by a breakdown dimension is not supported in lens"

Does it lead to user seeing less amount of data after lens migration compared to the old visualisation ?

@agithomas
Copy link
Contributor

Can you please share share the snippet of the screenshot displaying the impact of the panel data before and after lens migration ?

@agithomas agithomas reopened this Mar 22, 2023
@rajvi-patel-22
Copy link
Contributor Author

@rajvi-elastic , I do not fully understand the issue

"Splitting a chart into multiple smaller charts by a breakdown dimension is not supported in lens"

Does it lead to user seeing less amount of data after lens migration compared to the old visualisation ?

@agithomas , splitting chart functionality splits the visualization into multiple charts based on the provided field.

For example, below is the donut chart which shows user total count of records based on log.level.
image

Now if user wants to have this visualization for each datastream then he can split this chart into multiple using split chart functionality. Below is the visualization which splits the chart into multiple charts based on datastream.dataset field. So that user can have individual charts for each datastream which shows you total count of records based on log.level.
image

In our case, user won't see less amount of data or panel won't be affected even if we will remove the split chart functionality.

In the below panel (from which we have removed the split chart layer), event.dataset: activemq.audit filter is applied at the top level and then the entire visualization is also splitted based on the same filter. User won't see multiple charts in this case because of the top level filter. Hence, removing split chart functionality won't affect the functionality in this particular case.
image

@rajvi-patel-22
Copy link
Contributor Author

Can you please share share the snippet of the screenshot displaying the impact of the panel data before and after lens migration ?

Please find the below screenshot before migration (with split chart functionality and without split chart functionality)
image

image

The below screenshot is after migration without split chart functionality in lens:
image

In all of the three cases you will find the same count (3042).

@agithomas
Copy link
Contributor

Thanks for providing the clarification

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