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
I had searched in the issues and found no similar feature requirement.
Description
The current index definition for the BanyanDB module in OAP needs optimization to increase efficiency and improve performance. This issue focuses on moving different identifiers from indexRule to Entity in Measure and simplifying the network_address_alias entity.
Details:
Common Metrics: Move service_id from indexRule to Entity in Measure. This change will streamline the process of accessing the service information by centralizing the identifiers into Entity within Measure.
Relation Metrics: Move service_id, instance_id, and endpoint_id to Entity. By moving these identifiers to Entity, we can improve the retrieval of relation metrics and enhance the overall performance of the system.
Network_address_alias: Retain only last_update_time_bucket. Simplifying the network_address_alias will reduce unnecessary complexity and improve efficiency.
The proposed changes are expected to optimize the index definitions, improve the system's performance, and simplify the overall structure of the BanyanDB module in OAP.
Use case
No response
Related issues
No response
Are you willing to submit a pull request to implement this on your own?
Yes I am willing to submit a pull request on my own!
According to the latest discussion, we need to make BanyanDB APIs and implementation support accept multiple series definitions, rather than one. Each series definition could have multiple fields. This could provide better query support in following typical scenarios
Query metrics by ts and entity ID.
Store all query relative fields in one file. Nowadays, some are in series ID files, and others are in the tags family.
Search before asking
Description
The current index definition for the BanyanDB module in OAP needs optimization to increase efficiency and improve performance. This issue focuses on moving different identifiers from
indexRule
toEntity
inMeasure
and simplifying thenetwork_address_alias
entity.Details:
Common Metrics: Move
service_id
fromindexRule
toEntity
inMeasure
. This change will streamline the process of accessing the service information by centralizing the identifiers intoEntity
withinMeasure
.Relation Metrics: Move
service_id
,instance_id
, andendpoint_id
toEntity
. By moving these identifiers toEntity
, we can improve the retrieval of relation metrics and enhance the overall performance of the system.Network_address_alias: Retain only
last_update_time_bucket
. Simplifying thenetwork_address_alias
will reduce unnecessary complexity and improve efficiency.The proposed changes are expected to optimize the index definitions, improve the system's performance, and simplify the overall structure of the BanyanDB module in OAP.
Use case
No response
Related issues
No response
Are you willing to submit a pull request to implement this on your own?
Code of Conduct
The text was updated successfully, but these errors were encountered: