I now have a dashboard running on track.arynwood.com to support my long-term monitoring goals across Aryncore. The system is operational, but troubleshooting is ongoing.
Today I successfully connected the local dashboard instance and it's quietly working in the background to help me build intuition about site and system behavior. Thanks to the Aryncore server, the backend quietly gathers indicators I’ll use later to deepen my understanding of traffic, automation feedback loops, and long-term system performance. This is the first step in understanding what visitors are doing, how often, and when.
The Matomo instance is self-hosted. It's accessed through track.arynwood.com and now embedded across the top 10 most visited sections of the site. I will expand to others manually until I convert to a layout system. I am asking myself, what is the best way to automate this?
I opted to remain vague in the navigation and UI for the sake of design and clarity, what matters most is that the engine runs.
I encountered a container restart issue due to permissions:
~/tools/matomo$ docker-compose restart
Restarting matomo\_matomo\_1 ... error
Restarting matomo\_db\_1 ... error
ERROR: for matomo\_db\_1 Cannot restart container ... permission denied
ERROR: for matomo\_matomo\_1 Cannot restart container ... permission deniedThis appears related to AppArmor policy interference with Snap-based Docker. I'll resolve it by removing Docker from Snap and reinstalling via apt. But not today, today is reserved for coursework.
I’m now managing this system with timeline-based logs and return points. When I return to this task, I’ll resume with either restarting the containers or reinstalling Docker fully. Everything else is stable and persistent.
This is the start of a deeper arc into cyber systems design, particularly how to monitor behavior, events, and interactions in secure, local-first environments.
—Lorelei Noble