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

[Request]: Elastic Entity Model ("EEM") Technical Preview docs #4028

Closed
Tracked by #4027
chrisdistasio opened this issue Jun 20, 2024 · 8 comments
Closed
Tracked by #4027

[Request]: Elastic Entity Model ("EEM") Technical Preview docs #4028

chrisdistasio opened this issue Jun 20, 2024 · 8 comments

Comments

@chrisdistasio
Copy link

chrisdistasio commented Jun 20, 2024

Description

What: We are introducing a new concept in observability-- the Elastic Entity Model ("EEM"). EEM is:

  • A conceptual framework to break down silos between observability/security data sources by providing a shared understanding of what the data is about
  • A set of extensible schemas which allow entities and their associated signals to be defined, stored, and queried
  • A set of APIs to empower solution teams to build entity-centric features

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

@chrisdistasio
Copy link
Author

related to #4027

@dedemorton
Copy link
Contributor

@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!

@roshan-elastic
Copy link
Contributor

@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

@dedemorton
Copy link
Contributor

@tommyers-elastic Just realized that I should have included you on my questions here.

@dedemorton
Copy link
Contributor

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.

@chrisdistasio
Copy link
Author

@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.

@chrisdistasio
Copy link
Author

@dedemorton let's iterate here. I'm going to ask the eng team to review as well.

@dedemorton
Copy link
Contributor

Closed by #4062

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

3 participants