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

Change license level wording to accomodate "enterprise" #53038

Closed
peterschretlen opened this issue Dec 13, 2019 · 3 comments · Fixed by #53858
Closed

Change license level wording to accomodate "enterprise" #53038

peterschretlen opened this issue Dec 13, 2019 · 3 comments · Fixed by #53858

Comments

@peterschretlen
Copy link
Contributor

#49474 will add support for the enterprise license type. Currently this license is only used by ECE and ECK, but is not yet recognized in the stack.

In the Kibana docs, we have a few areas that mention a specific list of licenses like

If you are using a Gold or Platinum license, enable reporting in your config/kibana.yml file.

Do we want to consider changing the wording to something like "Gold license or above"

I see the wording "gold or platinum" in at least the following
https://github.com/elastic/kibana/blob/master/docs/canvas/canvas-share-workpad.asciidoc
https://github.com/elastic/kibana/blob/master/docs/management/managing-licenses.asciidoc

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-docs (Team:Docs)

@lcawl
Copy link
Contributor

lcawl commented Dec 16, 2019

In general, we've tried to move away from having license-specific information in our documentation. Rather, we should direct folks to the subscriptions page as the source of truth.

In the case of the Canvas docs, I think that entire section about creating a PDF is only applicable if you have a license that enables the reporting features. So I think maybe the first step should be removed and instead that section could be qualified with something like this:
"If you have a license that supports the {report-features}, you can create a PDF copy of your workpad that you can save and share outside of Kibana..."

In the case of the "Managing licenses" page, I think that paragraph could benefit from some clarification. I think the reasons for that requirement are more clearly stated here: https://www.elastic.co/guide/en/elasticsearch/reference/master/bootstrap-checks-xpack.html#bootstrap-checks-tls As a quick stop-gap, however, I don't think it hurts to have "gold or higher" or "gold or later" there.

@peterschretlen
Copy link
Contributor Author

Thanks @lcawl for the suggestions, I like the idea of not mentioning the specific licenses. Those were the only two files I could find that seem affected, I'll make those updates.

peterschretlen pushed a commit to peterschretlen/kibana that referenced this issue Dec 30, 2019
@KOTungseth KOTungseth self-assigned this Jan 10, 2020
gmmorris added a commit to gmmorris/kibana that referenced this issue Jan 20, 2020
* upstream/master: (83 commits)
  [Reporting] Fix map tiles not loading by using Chrome's Remote Protocol (elastic#55137)
  [Data Plugin] combine autocomplete provider and suggestions provider (elastic#54451)
  resolves elastic#53038 - remove references to specific license levels (elastic#53858)
  highlighting rules should still know about url parts when in sql state (elastic#55200)
  [Metric] convert mocha tests to jest (elastic#54054)
  [skip-ci] Update vector styling docs for 7.6 UI changes and new features (elastic#55087)
  Fix enable API to schedule task after alert is updated (elastic#55095)
  chore(NA): add 7.6 branch to the list of backport branches (elastic#54998)
  Convert tests to jest in vis_type_timeseries/public & common folders (elastic#55023)
  [ML] Accessibility fix for structural markup on table rows (elastic#55075)
  [Mappings editor] include/exclude fields only support custom options (elastic#54949)
  [Vis] Move Timelion Vis to vis_type_timelion (elastic#52069)
  Deprecate `chrome.navlinks.update` and add documentation (elastic#54893)
  [ML] Single Metric Viewer: Fix time bounds with custom strings. (elastic#55045)
  [Vis: Default editor] EUIficate and Reactify the sidebar (elastic#49864)
  [Mappings editor] Fix cannot set boolean value for "null_value" param (elastic#55015)
  [SIEM] Adds support for apm-* to the network map (elastic#54876)
  [Reporting] Define shims of legacy dependencies (elastic#54082)
  Resolver is overflow: hidden to prevent obscured elements from showing up (elastic#55076)
  Upgraded EUI to 18.2.1 (elastic#55090)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants