The support bundle collects the information for troubleshooting.
The timestamp field for service log allows you to enter a date and time so that service logs of one hour are collected before the specified time. The service log repository is using UTC time zone, the default timestamp is in UTC (Coordinated Universal Time) time zone and specified in yyyy-MM-dd HH:mm format. For example, 2022-05-06 15:45. You can change the timestamp according to your desired time slot.
Note: Only the service logs in the support bundle are affected by the timestamp. However, the Kubernetes cluster information in the support bundle reflects the latest deployment only.
To collect the following information, click
Start Bundle Collection:
- Node details.
- Service details.
- Pod details for VMware Telco Cloud Service Assurance.
- Logs for VMware Telco Cloud Service Assurance.
- Pod details for K8s.
- Pod logs for the services.
- Persistent volume details.
- Config map details.
- K8s service account and corresponding role binding information.
To download the collected bundle, click Download Support Bundle.
Service Logs
Service Logs are collected through ELK pipeline and presented in the Service Logs page. You can search and explore the logs through the embedded Kibana log browser.
On the Service Logs page, you can perform the following operations.
- Customize the fields that you want to view.
- Filter the logs by criteria.
- Search the log by text message.
For more detailed functions, see Kibana Discover documentation.
Service Logs Manager
Service Logs Manager is designed to configure the service logs pipeline. The service logs are collected through Filebeat, Logstash, Elasticsearch, or Kibana (ELK) pipeline. The Service Logs Manager allows you to configure the log retention days.
The service logs are rotated daily which means each day, a new index is created in Elasticsearch for the logs. The default value of retention day is seven, which means by default, the logs older than seven days are deleted. If you wish to increase the retention days, the backend Elasticsearch data nodes must be added to accommodate more log data.
Note: The minimum log retention days is two and maximum retention days is ninty. If you want to increase the retention days, then the backend Elasticsearch data nodes must be added to accommodate more log data.