[Bug]:why the milvus-dashboard.json storage separate the proxy contention？

[ronghuaihai]

Is there an existing issue for this?

• I have searched the existing issues

Environment

- Milvus version: 2.3.16
- Deployment mode(standalone or cluster):cluster
- MQ type(rocksmq, pulsar or kafka):    pulsar
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

when i download the newest mivlus-dasboard.json and use it in graphna ，it is unnormal 。the storage parition separate the proxy parition 。

but ，when i use milvus.2.2.14.json ，it is normal。as follows：

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

[ronghuaihai]

which one edition should to use when monitor 2.3.16 mivlus version？ the older 2.2.14 or newest dashboar ？

[yanliang567]

@ronghuaihai which link do you download for the newest dashboard? I guess the latest one could be for Milvus 2.4.x. As long as it works, I think you can use the old one unless you are looking for some new metrics.
/assign @ronghuaihai
/unassign

[xiaofan-luan]

/assign @locustbaby
could you help on answer this?