BanyanDB: fix query getInstance by instance ID. (#13549)

Author: wankai123

docs/en/changes/changes.md

@@ -110,6 +110,7 @@
 * Fix the malfunctioning alarm feature of MAL metrics due to unknown metadata in L2 aggregate worker.
 * Make MAL percentile align with OAL percentile calculation.
 * Update Grafana dashboards for OAP observability.
+* BanyanDB: fix query `getInstance` by instance ID.
 
 #### UI
 

oap-server/server-storage-plugin/storage-banyandb-plugin/src/main/java/org/apache/skywalking/oap/server/storage/plugin/banyandb/measure/BanyanDBMetadataQueryDAO.java

@@ -144,16 +144,14 @@ protected void apply(MeasureQuery query) {
 
     @Override
     public ServiceInstance getInstance(String instanceId) throws IOException {
-        IDManager.ServiceInstanceID.InstanceIDDefinition id = IDManager.ServiceInstanceID.analysisId(instanceId);
         MetadataRegistry.Schema schema = MetadataRegistry.INSTANCE.findMetricMetadata(InstanceTraffic.INDEX_NAME, DownSampling.Minute);
         MeasureQueryResponse resp = query(false, schema,
                 INSTANCE_TRAFFIC_TAGS,
                 Collections.emptySet(),
                 new QueryBuilder<MeasureQuery>() {
                     @Override
                     protected void apply(MeasureQuery query) {
-                        query.and(eq(InstanceTraffic.SERVICE_ID, id.getServiceId()))
-                                .and(eq(InstanceTraffic.NAME, id.getName()));
+                        query.and(eq(ID, instanceId));
                     }
                 });
         return resp.size() > 0 ? buildInstance(resp.getDataPoints().get(0), schema) : null;