Configuration Change Report

I am not sure if you are talking about LMConfig or device (resource) settings or something else.  For LMConfig, we had to solve this by using the API to download configurations, then committing to a git repo (local gitlab instance) with post-commit hooks for notifications.  Sadly, this reveals numerous flaws in the LMConfig process, which we have to work around by detecting and skipping bad updates prior to saving for repo commit.  For device settings, we have a similar method where we regularly download devices and other endpoints from the API.  If you mean yet another thing, like actual target device configuration details not handled by LMConfig, then LMConfig may be a good option for tracking those (but may require a custom module or two).