While implementing Sentry for cron job monitoring in a Kotlin/Spring application, I encountered an issue where the advisor was not being registered as a bean, which caused the monitoring to fail silently. This was due to the missing aspectjweaver dependency.
I propose the following solutions to prevent this issue for other users:
Update Documentation: Clearly state in the Sentry documentation that org.aspectj:aspectjweaver needs to be included as a dependency for proper operation of AOP-based features like cron job monitoring.
Module Dependency: Include org.aspectj:aspectjweaver directly within the Sentry module dependencies, ensuring it is automatically available when the Sentry module is used.
Problem Statement
While implementing Sentry for cron job monitoring in a Kotlin/Spring application, I encountered an issue where the advisor was not being registered as a bean, which caused the monitoring to fail silently. This was due to the missing
aspectjweaver
dependency.I propose the following solutions to prevent this issue for other users:
Update Documentation: Clearly state in the Sentry documentation that
org.aspectj:aspectjweaver
needs to be included as a dependency for proper operation of AOP-based features like cron job monitoring.Module Dependency: Include
org.aspectj:aspectjweaver
directly within the Sentry module dependencies, ensuring it is automatically available when the Sentry module is used.Solution Brainstorm
No response