As mentioned in the KB - Can’t retrieve Config Server logs when using Spring Cloud Services (SCS) 3.2.5, you would encounter below error if you are using the "Service Instance Logging CLI Plugin" to retrieve service-instance logs as there was a bug in previous SCS versions.
$ cf service-logs scs-standard --recent
Retrieving logs for service instance scs-standard in org example_org / space example_space as admin...
FAILED
/v2/services did not contain a service instance logs endpoint: maybe the broker version is too old
This bug has been fixed in the SCS v3.2.6. Thus if you still encounter issues like below even after upgrading to the SCS v3.2.6+, then there is a possibility of plugin compatibility issue.
$ cf sil config-server --recent
Retrieving logs for service instance scs-standard in org example_org / space example_space as admin...
FAILED
Error dialing trafficcontroller server: Get "https://scs-service-broker.example.com/logs/SOME-DIGITS/recentlogs": context deadline exceeded (Client.Timeout exceeded while awaiting headers).
Please ask your Cloud Foundry Operator to check the platform configuration (trafficcontroller endpoint is https://scs-service-broker.example.com/logs/).
First try if you are able to use the cf logs command to get the SCS backend app logs displayed.
$ cf service --guid scs-standard
####
$ cf t -o p-spring-cloud-services -s ####
$ cf logs config-server --recent
If the SCS backend app logs are able to be retrieved by the cf logs command, then it suggests there might be a plugin compatibility issue.
Try reinstalling the service-instance-logging plugin as follows:
$ cf uninstall-plugin service-instance-logging
$ cf install-plugin -r CF-Community "Service Instance Logging"
If it's still failing to retrieve the service-instance logs after the plugin reinstallation, then please create a Tanzu support ticket to investigate the issue further.