6. 🕑 Automation & Data Management

This section covers the automation and data lifecycle management features of the JaJuMa Real User Monitoring (RUM) extension for Magento 2.
By using Magento's native cron job system, the extension can process data, manage storage, and protect your server with minimal manual intervention.

6.1 🔨 Data Processing Cron

This cron job is responsible for processing the raw RUM data collected from your storefront and aggregating it into the reports visible in the RUM Dashboard.

• Enable/Disable:
  A simple Yes/No toggle to enable or disable this cron job.

• Data Processing Schedule:
  A standard cron schedule string that defines how often the processing job runs. For help building a cron schedule, you can use an online tool like crontab.guru.
  A common schedule to run every night at midnight would be 0 0 * * *.

• Server Load Limit
  This setting defines a maximum server load threshold. If the current server load exceeds this value, the data processing cron will automatically pause and wait for the load to decrease.
  The load is calculated as: 1 Minute Load Average / Number of CPU Cores.

🚀 Scenario: Protecting Black Friday Sales
During a major sales event, your server load will naturally be high.
The Server Load Safeguard ensures that the RUM data processing - a non-critical task - will automatically pause, dedicating 100% of your server resources to processing customer orders.
This protects your revenue and ensures a smooth checkout experience during peak traffic.

6.2 📈 Server Load Collection Cron

This cron job periodically collects and stores your server's load metrics.

• Enable/Disable:
  Yes/No toggle to enable or disable this cron job.

  Why this matters:
  The collected server load data is used to enrich the TTFB (Time to First Byte) details chart in the RUM Dashboard. This allows you to visually correlate spikes in your server's response time with high server load, helping you diagnose backend performance issues more effectively.

6.3 🗑️ Data Cleanup Cron

This cron job automatically deletes old RUM data from your database to manage storage space.

• Enable/Disable:
  Yes/No toggle to enable or disable this cron job.
• Data Cleanup Schedule:
  A standard cron schedule string that defines how often the cleanup job runs.
  A typical schedule might be once per day, for example 0 1 * * * (at 1:00 AM).

6.4 📁 Data Retention Policy

These settings define how long data is kept in your system.

• Keep Processed RUM Data For (Days)
  Configure the number of days that processed RUM data should be kept in the database. Data older than this value will be deleted by the cleanup cron.

📁 Use Case: Balancing History and Resources
If you are a data-driven organization that analyzes performance trends quarterly, you might set the retention period to 90 or 180 days.
This allows you to compare performance across seasons. Conversely, if your focus is on immediate, week-over-week improvements and you have limited database storage, a shorter period like 30 days might be more appropriate.

• Keep invalid raw data for (Days)
  This option allows you to keep raw JSON data files that were excluded from processing (e.g., due to filtering). This is primarily for debugging purposes. Set to 0 to discard invalid data immediately.

📞 Need Help?

Still have questions or need help with your configuration? Our expert team is here to assist. Please don't hesitate to contact our support team for personalized assistance.