Frequently Asked Questions

No. DMCloudArchitect Health is a structured infrastructure health reporting platform, not a real-time monitoring dashboard. Metrics are sampled locally every 5 minutes, aggregated into hourly snapshots, and used for trend-based weekly reporting and signal-driven health analysis. This approach reduces alert fatigue and provides long-term visibility without requiring teams to babysit live dashboards.

Datadog, Prometheus, and Zabbix are real-time monitoring platforms designed for continuous metric streaming, dashboards, and threshold-driven alerting. DMCloudArchitect Health focuses on Linux server monitoring and MySQL monitoring through structured health reporting and clean trend analytics. Instead of alert storms and noisy dashboards, you get curated, operationally relevant signals and weekly infrastructure health reports that are easy to consume and act on.

DMCloudArchitect Health is designed for Linux system administrators, MySQL DBAs, and infrastructure engineers who manage production servers and want a simple, reliable way to track infrastructure health over time. It is especially useful for teams that want structured health visibility without operating a complex observability stack.

Not typically. DMCloudArchitect Health is not intended to replace real-time monitoring systems. It complements them by adding structured Linux & MySQL health reporting, trend visibility, and operational risk indicators. Many teams keep their real-time monitoring and use DMCloudArchitect Health for clean weekly reporting and clarity.

The monitoring component is designed to be lightweight. It collects a focused set of Linux and MySQL health signals at a low sampling rate (every 5 minutes) and aggregates them into hourly snapshots. It does not run high-frequency collectors or heavy instrumentation, and it avoids invasive collection patterns.

The weekly report covers the previous 7 days of hourly aggregated data. It includes Linux health (CPU/load trends, memory and swap peaks, disk utilization per mount) and MySQL health (threads running/connected per instance, per-user connection breakdown). It also includes slow query digest analytics (top normalized query patterns) and an infrastructure consistency summary to highlight trends, degradation, and early warning signals.

Raw samples are collected locally every 5 minutes and kept only in a short rolling window on your server. Before upload, the system aggregates those samples into a single hourly snapshot. The reporting platform stores only hourly aggregated numerical values — not raw 5-minute data.

Only hourly aggregated numerical health metrics are uploaded: load averages, memory/swap percentages, disk utilization percentages per mount, and MySQL thread counts. For slow query analysis, only normalized digest identifiers and timing statistics are included. No SQL query text, no table names, no schema information, no row values, and no connection strings ever leave your server.

MySQL credentials are stored encrypted using mysql_config_editor, which creates a ~/.mylogin.cnf file with mode 0600. It is readable only by the dmca_health OS user. No plain-text MySQL passwords are written to configuration files.

Yes. All snapshot uploads use HTTPS. Communication is outbound-only — no inbound ports are required, no firewall rules need to change, and there is no remote shell or remote control capability.

The install script requires root (sudo) to create the dmca_health system user and configure scheduled execution. After installation, data collection and uploads run as the dedicated dmca_health OS user, which has no sudo rights. Root access is only needed once during setup.

No. The system makes outbound HTTPS connections to upload hourly snapshots. No inbound ports are opened and no firewall rules need to be modified.

Yes. Multiple MySQL instances per server are supported. Each instance is configured separately using mysql_config_editor login-paths, and the report shows per-instance MySQL health signals.

DMCloudArchitect Health supports modern MySQL deployments, including MySQL 8.x and MySQL 9.x. If you run a managed MySQL service or custom builds, the key requirement is standard MySQL client compatibility and read-only access for health collection.

The platform collects health signals at the MySQL instance level and works well in environments using replication (source/replica) because each instance can be monitored and reported independently. Cluster topology awareness varies by deployment; if you have a specific MySQL Cluster (NDB) or multi-site topology, contact us and we will confirm the best approach for your environment.

The monitoring component is written in pure bash and uses standard Linux tools (awk, df, /proc). It works on modern Linux distributions including Oracle Linux/RHEL, Debian/Ubuntu, and their derivatives.

Alerts are based on hourly aggregated snapshots — not real-time event streams. This means alerts reflect sustained conditions rather than transient spikes. Examples include missing snapshot detection (a server stops reporting), sustained resource degradation patterns, and slow query growth signals. The system is intentionally opinionated to reduce false positives and monitoring noise.

Traditional monitoring platforms often generate high-frequency threshold alerts that can overwhelm teams and create alert fatigue. DMCloudArchitect Health focuses on structured signal analysis and meaningful operational indicators instead of reacting to every short-lived spike. The goal is clarity and stability — not noise amplification.

Hourly health alerts, missing snapshot detection, and degradation detection are Advanced plan features. The Basic plan includes email notification when your weekly report is ready. The Free plan does not include alerts.

No. The Free tier does not require any payment information.

Metrics exceeding your plan limits will not be processed until you upgrade. You will be notified when limits are reached. Existing data within limits is not affected.

Yes. Plan changes can be made anytime through the Stripe billing portal. Upgrades take effect immediately. Downgrades take effect at the end of the current billing cycle.

Your subscription remains active until the end of your current billing period. After that, your account automatically downgrades to the Free tier. Retention limits adjust accordingly — data beyond the 7-day Free retention window is removed.

Yes. Contact us at [email protected] for enterprise-level reporting, multi-environment coverage (Prod/QA/DR), and custom retention requirements.