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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rename Cluster to Deployment #43119

Open
ycombinator opened this issue Aug 12, 2019 · 2 comments
Open

Rename Cluster to Deployment #43119

ycombinator opened this issue Aug 12, 2019 · 2 comments
Labels
discuss enhancement New value added to drive a business result Team:Monitoring Stack Monitoring team

Comments

@ycombinator
Copy link
Contributor

In #27595 (comment) we started a discussion about renaming Cluster to Deployment in the Stack Monitoring UI. This would align with the terminology used in Elastic Cloud as well.

Please 馃憤 if you're in favor of this change or 馃憥 and comment as to why if you're not.

@ycombinator ycombinator added enhancement New value added to drive a business result Team:Monitoring Stack Monitoring team labels Aug 12, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/stack-monitoring

@skearns64
Copy link

+1 here.

One reason I'm in favor of this is that it better prepares the terminology for solution-first deployments, where the user doesn't think about an "ES cluster," they think in terms of an "enterprise search deployment" or "app search" or "APM/Observability" where the fact that it's an ES cluster under the covers is important, but not the first thing the user thinks about. On the Stack Monitoring side, we'll eventually want to grapple with what it means to monitor each solution - are there just extra tabs in the existing UI? A more tailored experience? Lots to think about here, though it's a longer term question.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss enhancement New value added to drive a business result Team:Monitoring Stack Monitoring team
Projects
None yet
Development

No branches or pull requests

3 participants