If you find some issues that persist after verification of the sizing and resources for your Aura instance, it can be useful to troubleshoot connection or driver behaviour to gather further traces.

Usually, this should be considered after engaging with the support team and should not be the first element to bring within your support ticket.
Instead start with making sure that neither the environment nor the configuration are the source of the issues seen. When issues persist after this check, enabling debug logs would become necessary.
 

The following articles aim to provide sample code to demonstrate enabling debug level 
logging for each of the Neo4j Drivers :

• Go Driver Debug Level Logging
• Javascript Driver Debug Level Logging
• Java Driver Debug Level Logging
• GraphQL Debug Level Logging
• Spring Boot Java Driver Debug Level Logging
• Python Driver Debug Level Logging
• .Net Driver Debug Level Logging

Also See:
Logging Levels and Their Meaning