# How-to-debug-in-Milvus_686074149
Milvus is a cloud-native **Vector** database, also be treated as search engineer in Aviator.

A lot of difference compared to structured database like postgres and even non-structured database like vertica

## prerequisites

1. Open ticket in PSDC portal to request access for 2 aviator accounts  
	itom-aviator0-ext-stg: 824517076529
	itom-aviator0-ext-prod: 521526956341
2. For emergency case you can reset password for ESM, AK/SK can be picked up from parameter store in US2-Prod

## Steps

1. Check if the pod of attu is enabled, enable it by
	```
	kubectl scale deploy milvus-attu -n milvus --replicas=1
	```
2. Login to the windows bastion of aviator
3. Get the right ip of milvus ingress and map the ip to the host file
	```
	ping internal-k8s-eu30milvusattualb-94bd0407df-29282387.eu-central-1.elb.amazonaws.com
	```
4. Access your fqdn for milvus, e.g. [https://eu30-prod-itomaviator-attu.itsma-ng.com/](https://eu30-prod-itomaviator-attu.itsma-ng.com/), login with your credentials(default is: root/Admin\_1234)
5. Check for all the collections in milvus, there should be two records for each tenant that has enabled Aviator in smax:  
	![](attachments/686074149/686074143.png)
6. Vector search for all documents, first select the entity\_ *tenantid*, and set search by docId > 0 in Advanced Filter
7. Vector search for individual document, first select the entity\_tenantid, and then get the vector from dev  
	![](attachments/686074149/686074146.png)
8. Aviator logs are mainly from code block(not mounted to EFS yet):
	```
	kubectl logs itom-aviator-core-776c74c57d-h92qc -n aviator -c itom-aviator-core -f
	```

## Attachments:

[image2023-12-1\_13-10-40.png](attachments/686074149/686074143.png) (image/png)  
[image2023-12-1\_13-19-11.png](attachments/686074149/686074146.png) (image/png)
