-
Notifications
You must be signed in to change notification settings - Fork 120
[Observability] Add serverless feature tiers page #2297
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
base: main
Are you sure you want to change the base?
Conversation
🔍 Preview links for changed docs |
@paulb-elastic @chrisdistasio I've added a first draft here. Let me know if you think we need to add/change anything. Previews for the updated pages are in this comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, @mdbirnstiehl! thx!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
approving to unblock, with some structural/placement feedback. hi mike!
@@ -22,6 +25,10 @@ Data volumes for ingest and retention are based on the fully enriched normalized | |||
|
|||
## Synthetics [synthetics-billing] | |||
|
|||
[Synthetic monitoring](/solutions/observability/synthetics/index.md) is an optional add-on to Observability Serverless projects that allows you to periodically check the status of your services and applications. In addition to the core ingest and retention dimensions, there is a charge to execute synthetic monitors on our testing infrastructure. Browser (journey) based tests are charged per-test-run, and ping (lightweight) tests have an all-you-can-use model per location used. | |||
[Synthetic monitoring](/solutions/observability/synthetics/index.md) is an optional add-on to Observability Serverless projects that allows you to periodically check the status of your services and applications as a part of your "Complete" tier subscription. In addition to the core ingest and retention dimensions, there is a charge to execute synthetic monitors on our testing infrastructure. Browser (journey) based tests are charged per-test-run, and ping (lightweight) tests have an all-you-can-use model per location used. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wonder if this would be clearer if we put the tiers up above, like
Tier: Complete
Opt-in only
but won't make you refactor for my sake
deploy-manage/cloud-organization/billing/elastic-observability-billing-dimensions.md
Outdated
Show resolved
Hide resolved
@@ -102,7 +102,7 @@ This table compares Elasticsearch capabilities between {{ech}} deployments and S | |||
|
|||
### Observability | |||
|
|||
This table compares Observability capabilities between {{ech}} deployments and Serverless projects: | |||
This table compares Observability capabilities between {{ech}} deployments and Observability Complete Serverless projects. For more information on Observability Logs Essentials Serverless projects, refer to [Observability subscription tiers](../../../solutions/observability/observability-serverless-feature-tiers.md). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the children yearn for another column
consider changing the title of the column
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changing the column title makes sense. I'm hesitant to add a column for logs essentials here because the comparison here is between ECH and Serverless, not necessarily feature tiers and it might add a little more complexity than we want. I noticed Security doesn't mention specific feature tiers here, but not sure if that's the reason.
- id: observability | ||
--- | ||
|
||
# {{obs-serverless}} feature tiers |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
worried about separating this info from the other licensing info - would you consider keeping it with the other section?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you mean moving this page as a whole to a different section, or breaking up the information across billing dimensions/ech-serverless comparison/project settings?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
moving this page from the observability section to either of the docs in the deploy/manage section.
I realize neither page might be suitable in its current form, but we were asked to keep all of the licensing/tiering info together at some point so this moves away from that. I also am not sure whether it's an obs user decision as much as an admin/evaluator decision
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Gotcha, that makes sense. Let me think about it a little bit. Maybe there's a way we can sync the strategies between o11y/security and not split the information up so much or have it buried too deep.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes @mdbirnstiehl, but I think this requires a bit more thinking, it shouldn't block this PR from moving forward as long as these pages correctly and visibly reference each other. I've been thinking about this too and about more alignment between how we treat similar security and obs topics. We can sync separately on that.
This PR closes #2300 and #2301 adding details about the new Logs Essentials subscription tier in Observability Serverless.