This issue can occur because these jobs are logically deleted in the Controller UI while still being retained in the EUM database.
Update the synth_schedule table in the EUM database to re-enable the synthetic jobs.
- Obtain the MySQL root password of the EUM server.
kubectl get secret mysql-secret -n cisco-eum -o jsonpath='{.data.rootPassword}' | base64 -d; echo ""
Note: Copy and save this password to use it in the next steps.
- Run this command to identify the synthetic jobs count that are logically deleted from the UI.
kubectl exec appd-mysql-0 -n mysql -c mysql -- mysql -u root -p'<ROOT_PASSWORD>' -e \
"USE eum_db; SELECT deleted, COUNT(*) as count FROM synth_schedule GROUP BY deleted;"
-
Sample Output
-
- Run this command to enable all synthetic jobs.
Note: Replace the <Root_Password> with the value you copied from the earlier step.
kubectl exec appd-mysql-0 -n mysql -c mysql -- mysql -u root -p'<ROOT_PASSWORD>' -e \
"USE eum_db; UPDATE synth_schedule SET deleted='N' WHERE deleted='Y';"
- Confirm whether the
synth_schedule is updated.
kubectl exec appd-mysql-0 -n mysql -c mysql -- mysql -u root -p'<ROOT_PASSWORD>' -e \
"USE eum_db; SELECT deleted, COUNT(*) as count FROM synth_schedule GROUP BY deleted;"
-
Sample Output
-
Note: Ensure the count matches with the identified count in the Step
2.