Accessing Logs
Dish LMC logs can be accessed using Kibana. To make further debugging and monitoring easier, a change was implemented to tag Dish Manager logs with specific metadata i.e user tags from the SKA, allowing you to easily filter for user roles and specific devices.
Operator Logs
Dish Manager logs are tagged to differentiate between internal system logs and operator-initiated actions. Logs related specifically to operator actions are tagged with user=operator.
In Kibana, you can filter for these operator logs by entering the following query into the search bar:
ska_tags_field.user : "operator"
Device-Specific Logs
To isolate and filter the logs for a specific Tango device (i.e dish manager SKA001), use the following query:
ska_tags_field.tango-device : "mid-dish/dish-manager/SKA001"
The TRLs below may be used access any one of the other subdevices that may be deployed as part of a DishLMC deployment:
“mid-dish/b5dc-manager/<Dish ID>”
“mid-dish/ds-manager/<Dish ID>”
“mid-dish/simulator-spfrx/<Dish ID>”
“mid-dish/simulator-spf/<Dish ID>”
Combining Filters
You can easily combine these tags using standard boolean operators to narrow down your search. For example, if you want to see only the operator actions that were executed specifically on Dish SKA001, you can run:
ska_tags_field.user : "operator" and ska_tags_field.tango-device : "mid-dish/dish-manager/SKA001"
Filtering by Deployment Namespace
When debugging issues within a specific deployment, you will often need to filter logs by your specific k9s namespace alongside the device name you are checking.
For example, to find the logs for the mid_csp_cbf/ec/bite device strictly within the ci-ska-mid-cbf-deployment-2508911372-amjoshi namespace, you can combine the kubernetes.namespace field with the Tango device tag:
kubernetes.namespace : "ci-ska-mid-cbf-deployment-2508911372-amjoshi" and ska_tags_field.tango-device : "mid_csp_cbf/ec/bite"
Note
Remember to update the namespace string to match your currently active deployment pipeline or Minikube namespace.