You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Get entity types API (GET /internal/inventory/entities/types)
Description: This API fetches all entity types available Return type: string[] Replace it by:GET /internal/entities/v2/definitions/types#201470 Where it's/could be used:
It's used to fill up the Entity types filter input in the unified search bar.
Group by API (GET /internal/inventory/entities/group_by/{field})
_Description: Group entities by the provided field (currently only by entity.type is supported). Action: This API can be deleted. Where it's/could be used:
It's used to create the group by page.
Get all entities (GET /internal/inventory/entities)
_Description: Fetches all entities by a given entity type. Return type:InventoryEntity Replace it by:
POST kbn:/internal/entities/v2/_search
{
"type": "service",
"limit": 500,
"metadata_fields": ["data_stream.type"]
}
Notes:
The new API fetches last 5m of data, we can change it by adding a start and end properties. (Should we add a date picker on the ui?)
The API should return the same object as the current api.
The current API sorts entities by entity.last_seen_timestamp field, this should still be the same.
We need to provide a dataview to the KQL bar and to the "Open in discover" button. We can create it ourselves by calling this API GET kibana_entity_definitions/_search and get the field index_patterns. Or EEM could provide it for us. @simianhacker / @elastic/obs-entities
APM changes:
APM fetches the datastream_type from a given service name on the entities latest index. We'll need to update it to call the new API instead: API:GET /internal/apm/entities/services/{serviceName}/summary
/link-to/entity/{serviceName} route:
This link is used to link service names shown on logs explorer and discover, It also uses the summary API GET /internal/apm/entities/services/{serviceName}/summary, and needs to be tested.
Hosts changes:
Like APM, the Hosts page also has a summary API to fetch the datastream_type from a given entity type (host or container) and id. API: /api/infra/entities/{entityType}/{entityId}/summary
Inventory changes:
Get entity types API (
GET /internal/inventory/entities/types
)Description: This API fetches all entity types available
Return type: string[]
Replace it by:
GET /internal/entities/v2/definitions/types
#201470Where it's/could be used:
Notes:
Group by API (
GET /internal/inventory/entities/group_by/{field}
)_Description: Group entities by the provided field (currently only by
entity.type
is supported).Action: This API can be deleted.
Where it's/could be used:
Get all entities (
GET /internal/inventory/entities
)_Description: Fetches all entities by a given
entity type
.Return type: InventoryEntity
Replace it by:
Notes:
start
andend
properties. (Should we add a date picker on the ui?)entity.last_seen_timestamp
field, this should still be the same.entity.display_name
field or fallback toentity.id
field it the first is not available: https://github.com/elastic/elastic-entity-model/issues/207Adhoc data view
We need to provide a dataview to the KQL bar and to the "Open in discover" button. We can create it ourselves by calling this API
GET kibana_entity_definitions/_search
and get the fieldindex_patterns
. Or EEM could provide it for us. @simianhacker / @elastic/obs-entitiesAPM changes:
datastream_type
from a given service name on the entities latest index. We'll need to update it to call the new API instead:API:
GET /internal/apm/entities/services/{serviceName}/summary
GET /internal/apm/entities/services
./link-to/entity/{serviceName}
route:This link is used to link service names shown on
logs explorer
anddiscover
, It also uses the summary APIGET /internal/apm/entities/services/{serviceName}/summary
, and needs to be tested.Hosts changes:
datastream_type
from a given entity type (host
orcontainer
) and id.API:
/api/infra/entities/{entityType}/{entityId}/summary
The text was updated successfully, but these errors were encountered: