Previously, Logrotate was simple to find. Welcome systemctl timers and RHEL9!
Previously, cron jobs used to live in /var/spool/cron, and the world was simple.
Much later new folk thought this was too simple, and cron jobs were split up into /etc/crontab, /etc/cron.d /etc/cron.daily, /etc/cron.weekly, and /etc/cron.monthly. Overly complicated but with good intentions ( road to hell ). But /var/spool/cron was left for posterity and crontab -e works.
A bit later, new folk decided they had a better idea, and moved some of the system cron programmes from cron to systemctl triggers. I quite like it because it is new and pretty and shiny.
Now we have three related cron systems:
crond -> /var/spool/cron + /etc/cron*
systemd timers
Where is logrotate? It's called from here:
systemctl status logrotate.timers
If this enabled, and active, then you are good to go.
See what it has been up to with:
journalctl -u logrotate.timers
But really crond with /var/spool/cron/ was far simpler, and less error prone. Yes, you have to actually be able to write a basic shell script, but one had to be proficient in writing in C and in Shell scripts to consider a career in UNIX/Linux administration. ( rant over )
Nevertheless, I like systemd.