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][InfluxDb] Lens Migration #5505

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

[O11y][InfluxDb] Lens Migration #5505

rajvi-patel-22 opened this issue Mar 10, 2023 · 3 comments
Assignees

Comments

@rajvi-patel-22
Copy link
Contributor

rajvi-patel-22 commented Mar 10, 2023

Manually migrate InfluxDb visualizations to lens in current Kibana version 8.3.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

InfluxDB Dashboards Before Migration   After Migration  
  Lens Visualization Lens Visualization
[InfluxDB Metrics] Advanced Status Metrics 0 9 9 0
[InfluxDB Metrics] Status Metrics 0 18 18 0
  0 27 27 0

Data stream: Advstatus

Data stream : Status

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

Issues Identified

@kush-elastic kush-elastic added dashboard Relates to a Kibana dashboard bug, enhancement, or modification. Integration:influxdb InfluxDb labels Mar 10, 2023
@kush-elastic kush-elastic removed release-pending dashboard Relates to a Kibana dashboard bug, enhancement, or modification. Integration:influxdb InfluxDb labels Mar 13, 2023
@agithomas
Copy link
Contributor

@rajvi-elastic , can we close this issue?

@rajvi-patel-22
Copy link
Contributor Author

@rajvi-elastic , can we close this issue?

The PR has not been approved yet by the code owners! Can you approve it? Once we get the approval I'll go ahead and after merging the PR I'll close the issue.

@rajvi-patel-22
Copy link
Contributor Author

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

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