8. 💻 Command Line Interface (CLI) & Maintenance

This section is for developers and system administrators who need to interact with the JaJuMa Real User Monitoring (RUM) extension for Magento 2 programmatically.
The CLI provides tools for manual control and scripting of key functions, while the maintenance section offers direct actions from the backend.

8.1 💻 Command Line Interface (CLI) Commands

The extension includes a comprehensive set of CLI commands to manage data processing and cleanup outside of the scheduled cron jobs.
These are essential for debugging, manual data processing, and integration into deployment workflows.

• jajuma:rum:preprocess_data
  This is the primary command for processing raw RUM data.
  • Parameters:
    • Running without parameters processes the latest data that has not yet been processed.
    • --period="<number>":
      Reprocesses data for a specific number of days prior to the current date.
      (e.g., --period="7" reprocesses the last 7 days).
    • --period="all":
      Reprocesses all available data in the system.
    • --from="<YYYY-MM-DD>" and --to="<YYYY-MM-DD>":
      Reprocesses data for a specific date range.
    • The --to parameter is optional and defaults to the current time.
    • --skip-load-check:
      Bypasses the "Server Load Limit" safeguard. Use this with caution on production environments.

💡 Use Case: Immediate Performance Analysis
You've just deployed a major code change and want to see its impact on LCP immediately.
Instead of waiting for the nightly cron job, you can run bin/magento jajuma:rum:preprocess_data to process the latest user data and see the updated metrics in the RUM Dashboard within minutes.

• jajuma:rum:add_data_to_db
  This command moves the latest collected raw data into the primary RUM/Error Log database tables for processing.

• jajuma:rum:clear_preprocess_data
  Use this command to clear out any preprocessed data.

• jajuma:rum:remove_data_from_db

  ⚠️ Warning:
  This command permanently removes ALL raw and preprocessed RUM data from the database.
  This action cannot be undone.

• jajuma:rum:reset_adding_status

  🛠️ Use Case: Unsticking a Failed Process
  If a data processing job fails midway (e.g., due to a server timeout or error), it can leave a lock in place, preventing future jobs from running. This command is the essential tool to reset that lock, allowing the cron to proceed as normal. It is your primary fix if you notice that new data is no longer appearing in the dashboard.

• jajuma:rum:collect_ip_country

  💡 Use Case: Retroactive Data Enrichment
  You decide to start analyzing performance by country, but you've already collected a month's worth of data without this feature enabled. After configuring the Geocode database, you can run this command to go back and add country information to all your existing records, making your historical data much richer.

8.2 🛠️ Maintenance Tasks

The Maintenance tab within the extension's configuration screen provides access to helpful tools.

• Remove Now
  Click button to delete RUM data older than X days, with X as configured above.

• Clear Rum Dashboard Cache
  Click button to clear the RUM dashboard cache if data seems outdated.

• Download Log File
  From the General configuration section, you can enable logging.
  The log file (var/log/jajuma_rum.log) can then be downloaded directly from the Maintenance section. This provides a convenient way to access debugging information without needing SSH or FTP access to the server.

📞 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.