OpenCart Monitoring with Vigilmon

OpenCart is a lightweight open-source PHP e-commerce platform used by hundreds of thousands of small businesses worldwide. Its MVC architecture, 13,000+ marketplace modules, and minimal hosting requirements make it a popular choice for merchants who want an easy-to-run store without the overhead of Magento or WooCommerce. When your OpenCart store goes down, sales stop — and because OpenCart is often self-hosted on shared or VPS infrastructure, outages can go undetected until customers report them.

This guide covers how to monitor OpenCart with Vigilmon, including storefront availability, the REST API, admin panel health, SSL certificate expiry, and heartbeat monitoring for OpenCart's background scheduled tasks.

What to Monitor in an OpenCart Store

| Layer | URL Pattern | What Failure Means | |-------|-------------|-------------------| | Storefront homepage | https://yourstore.com/ | Customers can't browse or purchase | | REST API login | https://yourstore.com/index.php?route=api/login | API integrations and POS clients broken | | Admin panel | https://yourstore.com/admin/index.php | Merchant can't manage orders or catalog | | SSL certificate | HTTPS on your domain | Browser warnings; checkout trust destroyed | | Cron heartbeat | OpenCart scheduler | Cart abandonment emails, affiliate tracking silently failing |

Prerequisites

• A running OpenCart installation (3.x or 4.x) accessible over HTTPS
• A Vigilmon account
• An OpenCart API key and username (for API endpoint monitoring — configured in Admin → System → Users → API)
• SSH or cPanel access to configure cron jobs (for heartbeat monitoring)

Monitoring the Storefront

Step 1: Homepage Availability Monitor

1. Log in to Vigilmon → Monitors → New Monitor
2. Type: HTTP
3. Method: GET
4. URL: https://yourstore.com/ (or https://yourstore.com/index.php if not using SEO URLs)
5. Interval: 1 minute
6. Keyword check: your store name or a product category visible on the homepage

OpenCart serves the homepage through its PHP front controller. A keyword check detects PHP errors and database connection failures that return a 200 status with an error page rather than your actual storefront.

Step 2: Product Listing Monitor

Add a monitor for a product category page to catch database errors that only appear on listing views:

GET https://yourstore.com/index.php?route=product/category&path=20

Replace path=20 with an actual category ID from your catalog. Add a keyword check for a product name that should always appear in that category.

Monitoring the OpenCart REST API

OpenCart 3.x and 4.x include a built-in REST API used by point-of-sale integrations, mobile apps, and third-party order management systems. The API login endpoint validates credentials and returns a session token.

Step 3: API Login Endpoint Monitor

The API login endpoint accepts a POST request:

POST https://yourstore.com/index.php?route=api/login
Content-Type: application/x-www-form-urlencoded

username=YOUR_API_USERNAME&key=YOUR_API_KEY

Configure Vigilmon:

1. Type: HTTP
2. Method: POST
3. URL: https://yourstore.com/index.php?route=api/login
4. Headers: Content-Type: application/x-www-form-urlencoded
5. Body: username=YOUR_API_USERNAME&key=YOUR_API_KEY
6. Expected status: 200
7. Keyword check: "api_token" (a successful login response contains this field)

A healthy response looks like:

{
  "success": "Success: API session successfully started!",
  "api_token": "a1b2c3d4..."
}

Create an API user in OpenCart Admin → System → Users → API with the minimum necessary permissions for monitoring.

Monitoring the Admin Panel

Step 4: Admin Login Page Monitor

OpenCart's admin is served at /admin/index.php. Monitor its availability to detect server-side failures that prevent merchant access:

1. Type: HTTP
2. Method: GET
3. URL: https://yourstore.com/admin/index.php
4. Expected status: 200
5. Keyword check: OpenCart or Username

If you've renamed the admin directory for security, use your custom path instead of /admin/.

SSL Certificate Monitoring

Customers expect HTTPS on any checkout page. A lapsed SSL certificate causes browsers to display security warnings, breaking customer trust and preventing purchases.

Step 5: SSL Certificate Alert

1. In Vigilmon, open your storefront homepage monitor
2. Navigate to SSL Certificate → Enable SSL monitoring
3. Warn at: 30 days before expiry
4. Critical at: 14 days before expiry

Vigilmon checks the certificate on every monitor cycle. You'll receive alerts with enough lead time to renew through your hosting control panel or Let's Encrypt before any customer-facing disruption occurs.

Heartbeat Monitoring for OpenCart Scheduled Tasks

OpenCart depends on cron jobs or its built-in scheduler for background operations:

• Cart abandonment emails — reminding customers who left items in their cart
• Affiliate commission tracking — processing referral click and sale attribution
• Report generation — rebuilding statistics caches for the admin dashboard
• Google Base feed / data export — keeping product feeds current for shopping channels

If these tasks silently fail — due to PHP errors, file permission issues, or a misconfigured cron daemon — you won't know until a merchant notices missing reports or affiliates report untracked commissions.

Step 6: Create a Heartbeat Monitor

1. In Vigilmon → Monitors → New Monitor
2. Type: Heartbeat
3. Name: OpenCart Scheduled Tasks
4. Interval: 60 minutes (adjust to match your cron frequency — use 55 minutes for an hourly cron to allow for execution time)
5. Copy the generated heartbeat URL:

   https://vigilmon.online/api/heartbeat/your-unique-token
   

Step 7: Ping the Heartbeat from Your Cron Job

In cPanel or via crontab -e on your server, add the heartbeat ping after your OpenCart scheduled task script:

# Run OpenCart's scheduled task handler every hour
0 * * * * /usr/bin/php /var/www/opencart/system/cron.php >> /var/log/opencart-cron.log 2>&1 && curl -fsS --retry 3 https://vigilmon.online/api/heartbeat/your-unique-token > /dev/null

For OpenCart 4.x using its built-in System → Cron job feature, each cron job calls a URL endpoint:

# Call OpenCart's built-in cron endpoint and ping Vigilmon on success
0 * * * * curl -fsS "https://yourstore.com/index.php?route=extension/opencart/cron/index&token=YOUR_CRON_TOKEN" && curl -fsS --retry 3 https://vigilmon.online/api/heartbeat/your-unique-token > /dev/null

Alerting Configuration

Alert Routing

In Vigilmon → Alert Channels, configure:

• Storefront down: alert after 1 failed check — direct revenue impact
• API unavailable: alert after 2 failed checks — transient errors are possible on shared hosting
• Admin panel down: alert after 2 failed checks — urgent but not customer-facing
• Heartbeat missing: alert after the interval passes without a ping — silent failure

Sample Alert (API Down)

🔴 DOWN: OpenCart API Login
Monitor: REST API Login
URL: https://yourstore.com/index.php?route=api/login
Down for: 5 minutes
→ Check PHP-FPM status and OpenCart API configuration

Summary

| Monitor | URL | Check | Alert Threshold | |---------|-----|-------|-----------------| | Storefront homepage | / | Store keyword | 1 failed check | | Product category | /index.php?route=product/category&path=20 | Product keyword | 2 failed checks | | REST API login | /index.php?route=api/login | "api_token" | 2 failed checks | | Admin panel | /admin/index.php | OpenCart keyword | 2 failed checks | | SSL certificate | HTTPS domain | Expiry threshold | 30 days warning | | Cron heartbeat | Vigilmon heartbeat URL | Ping every hour | Missed interval |

With these monitors in place, you'll detect OpenCart outages, API failures, and silently broken scheduled tasks before they affect your customers or your merchant dashboard.

Further Reading

• Laravel Monitoring with Vigilmon
• PHP Application Monitoring with Vigilmon
• PrestaShop Monitoring with Vigilmon