-
Notifications
You must be signed in to change notification settings - Fork 162
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
[Request]: Elastic Entity Model ("EEM") Technical Preview docs #4028
Comments
related to #4027 |
@roshan-elastic @chrisdistasio Can you provide more detail about what specifically needs to be documented about the EEM for the technical preview? Do we need to document the schemas? How to extend them? What about the APIs? ON-WEEK and planned PTO really shortened my timeline for creating this content. It would help to have some direct pointers to primary source materials that describe this info. (GitHub issues or whatever you have.) Thanks! |
@chrisdistasio Given we won't be linking to this directly in the new UI, wondering where we'll link to this? I assume in any docs which talk explain the new version of things for our new experience? e.g. New services inventory docs |
@tommyers-elastic Just realized that I should have included you on my questions here. |
I've just found this whole repo with more information about EEM, which is useful, but I need guidance on what details about the EEM we want to externalize in the docs. Thanks. |
@dedemorton I'd like to include a high-level overview of EEM for the customer somewhere to reference when "EEM" is used elsewhere. Let me propose something, and we can iterate on it. @roshan-elastic you can link to it from your docs where you are looking to document "What is the Elastic-Entity Model (EEM)?" as pointed out in #4027. |
@dedemorton let's iterate here. I'm going to ask the eng team to review as well. |
Closed by #4062 |
Description
What: We are introducing a new concept in observability-- the Elastic Entity Model ("EEM"). EEM is:
When: The initial release will be a technical preview introduction of a very narrow scope, aligned to support the ECO technical preview for signal-agnostic services from logs. Planned introduction mid-July, 2024
Why: as we evolve into the next era of AI-powered Observability, we will shift toward entity-centric user journeys-- leading customers on a path toward understanding the operational state of the things they care about (entities) and "on rails" experiences toward ensuring customer experiences in the context of those entities.
Resources
tbd
Which documentation set does this change impact?
Stateful and Serverless
Feature differences
This feature will first be introduced in Serverless and later to the next stack release of stateful.
There are no meaningful differences planned across deployment methods.
What release is this request related to?
8.16
Collaboration model
Other (please describe below)
Point of contact.
Shared collaboration model btw docs, product, eng
Main contact: @chrisdistasio , @tommyers-elastic
Stakeholders: @roshan-elastic, @miltonhultgren , @klacabane
The text was updated successfully, but these errors were encountered: