👀 Monitoring

https://git.coopcloud.tech/coop-cloud/monitoring-ng/ provides a dashboard to view multiple abra deployments in one place. Administrators can see performance over time on multiple machines, spot memory leaks and upgrade needs, and receive alerts for issues requiring attention.

Unfortunately, the recipe is complex: 6 containers from different upstream sources all need to work together. So upgrades are work-intensive. We discussed dividing the work: multiple maintainers could split responsibilities into three areas while supporting each other.

(🧵 2/4)

🌱 Why choose Coop Cloud for your collective?

A creature from Datakollektivet.no joined us, wondering if they should move from ansible to coop cloud. Here's some of our reasons for joining:
- Coop Cloud helps reduce skill silos, allowing more people in your org to share infrastructure responsibilities.
- Deploying new services is more cost-effective, because many interactions are preconfigured: e.g. centralized configuration, SSO, health checks, and upgrades.
- When you do have to perform work setting up a service, others in the community will benefit and may contribute to your efforts.
- Creating a new recipe involves following guidelines which ensure stable and robust deployments.
- Offboarding is easy. You can stop using abra at any time and manage your deployment using another tool.
- Maybe most importantly, the community around coop cloud is valuable to its members, as a place to get together with other tech cooperatives and collectives.

(🧵 3/4)