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

Reuse TSVB chart components in Monitoring charts #18310

Closed
Tracked by #65
elasticmachine opened this issue Oct 31, 2017 · 1 comment
Closed
Tracked by #65

Reuse TSVB chart components in Monitoring charts #18310

elasticmachine opened this issue Oct 31, 2017 · 1 comment
Labels
Feature:ElasticCharts Issues related to the elastic-charts library Team:Monitoring Stack Monitoring team

Comments

@elasticmachine
Copy link
Contributor

Original comment by @ycombinator:

I was chatting with @tsullivan yesterday about making some improvements to the Monitoring charts to aid LINK REDACTED. We realized pretty quickly that the improvements we wanted were already implemented in TSVB chart components.

Since the Monitoring charts are a fork of (older) TSVB charts, it probably just makes sense to reuse the (current) TSVB charts in Monitoring. This way users get some consistency and we don't have two slowly diverging codebases both implementing time series chart components.

/cc @pickypg @simianhacker

@elasticmachine elasticmachine added the Team:Monitoring Stack Monitoring team label Apr 25, 2018
@markov00 markov00 added the Feature:ElasticCharts Issues related to the elastic-charts library label Feb 19, 2019
@tsullivan
Copy link
Member

I'll close this as it's not how we need to track updating any of the charts. There is a new chart library under development and they'll roll out the chart to all the apps in their own timeline.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:ElasticCharts Issues related to the elastic-charts library Team:Monitoring Stack Monitoring team
Projects
None yet
Development

No branches or pull requests

3 participants