Refer to serverless project feature tiers as such and not as subscription nor features #3249
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
florent-leborgne
requested review from
benironside,
mdbirnstiehl,
nastasha-solomon and
natasha-moore-elastic
mdbirnstiehl
approved these changes
Oct 1, 2025
shainaraskas
approved these changes
Oct 1, 2025
solutions/observability/observability-serverless-feature-tiers.md
Outdated
Show resolved
Hide resolved
natasha-moore-elastic
approved these changes
Oct 2, 2025
mdbirnstiehl
pushed a commit
to mdbirnstiehl/docs-content
that referenced
this pull request
Oct 2, 2025
…tion nor features (elastic#3249) This PR streamlines the way we refer to serverless feature tiers in the docs: - Feature tier names should be written in full form - A feature tier isn't a subscription. This term is reserved on Elastic Cloud, it refers to the Elastic Cloud subscription that determines ECH deployment features and the support level for both ECH deployments and serverless projects. Any non-trial user on Elastic Cloud needs an Elastic Cloud subscription regardless of their usage of ECH or serverless. - we should consistently use "feature tier" when we need this term. Not just feature, not just tier (though just tier sounds more acceptable) - It's fine to say "Security Analytics Essentials project" too. We don't have to overuse "feature tier" Closes: elastic#2768 --------- Co-authored-by: shainaraskas <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR streamlines the way we refer to serverless feature tiers in the docs:
Closes: #2768