milvus icon indicating copy to clipboard operation
milvus copied to clipboard

[Enhancement]: Support monitoring on standalone

Open xiaofan-luan opened this issue 9 months ago • 6 comments

Is there an existing issue for this?

  • [X] I have searched the existing issues

What would you like to be added?

see discussion https://github.com/milvus-io/milvus/discussions/32962#discussioncomment-9391729.

I don't forsee any reason why we couldn't the monitoring in standalone, maybe some physical metrics can not be seperate, like cpu usage and monitoring

Why is this needed?

No response

Anything else?

No response

xiaofan-luan avatar May 11 '24 07:05 xiaofan-luan

image

it was already supported in standalone

zhuwenxing avatar May 11 '24 07:05 zhuwenxing

@zhuwenxing This monitor is for k8s cluster version. Info such as namespace, instance can't find in standalone milvus metrics.

king1302217 avatar May 11 '24 07:05 king1302217

I think you will need to setup prometheus metrics? it could be still collected but grapfana might need to be modified

xiaofan-luan avatar May 11 '24 08:05 xiaofan-luan

@xiaofan-luan I have already setup prometheus metrics. The problem is that I don't want to modify each grafana panel to standalone milvus metrics...

king1302217 avatar May 11 '24 08:05 king1302217

@zhuwenxing This monitor is for k8s cluster version. Info such as namespace, instance can't find in standalone milvus metrics.

@king1302217

How do you deploy your standalone? k8s or docker?

In my environment, if the instance is deploy by k8s, this panel can be used for standalone and cluster both. image

zhuwenxing avatar May 11 '24 08:05 zhuwenxing

If the instance is deployed through Docker, then we don't actually provide a corresponding monitoring dashboard. So this issue has nothing to do with standalone or cluster, but rather with whether it's a Docker deployment or a Kubernetes deployment.

zhuwenxing avatar May 11 '24 08:05 zhuwenxing

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.

stale[bot] avatar Jun 11 '24 03:06 stale[bot]