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

[Serverless]: Document the full list of Observability limitations #4645

Open
ppf2 opened this issue Dec 5, 2024 · 8 comments
Open

[Serverless]: Document the full list of Observability limitations #4645

ppf2 opened this issue Dec 5, 2024 · 8 comments

Comments

@ppf2
Copy link
Member

ppf2 commented Dec 5, 2024

Serverless Docs

Elastic Observability

Description

Currently, https://www.elastic.co/guide/en/serverless/current/observability-limitations.html contains a single item specific to max ingest rate. There are definitely more limitations for Observability on Serverless such as universal profiling and RUM not being available yet. We should compile the full list and document accordingly.

Resources and additional context

https://www.elastic.co/guide/en/serverless/current/observability-limitations.html

@ppf2 ppf2 changed the title [Serverless]: Observability has more limitations than just 1 item [Serverless]: Document the full list of Observability limitations Dec 5, 2024
@lucabelluccini
Copy link
Contributor

@alaudazzi FYI

@lucabelluccini
Copy link
Contributor

I have a list which I collected from @chrisdistasio in private

@chrisdistasio
Copy link

thanks for opening.

should move this request to observability-docs.

happy to work with the team there on the content.

cc: @dedemorton

@dedemorton
Copy link
Contributor

Moving this to observability-docs....

@dedemorton dedemorton transferred this issue from elastic/docs-content Dec 9, 2024
@dedemorton
Copy link
Contributor

@chrisdistasio Can you make sure this issue gets populated with the specifics of which limitations need to be documented? Thanks!

@chrisdistasio
Copy link

@lucabelluccini let's sync on this to understand the need for what we want to have documented-- internally and externally-- to ensure it's up to date and accurate

@chrisdistasio
Copy link

related issue: #3394

@chrisdistasio
Copy link

@lucabelluccini and I had a discussion and will plan to take the following actions:

  • itemize an internal list for validation
  • create a kb documenting differences
  • work with docs team to tag stateful docs with an indicator for features that are not available in serverless.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants