mozzy/drupal-connector

Drupal error, inventory, cron, and queue reporting for Mozzy Assistance.

v1.0.0 2026-08-11 10:37 UTC

Requires

• php: ^8.1
• composer/installers: ^2.3
• drupal/core: ^10.3 || ^11

GPL-2.0-or-later

• Mozzy

Published on Packagist.org on 2026-08-11 10:44 UTC

README

Server-side Drupal 10.3 and 11 module for Mozzy Connector Protocol v1. It reports sanitized application errors, Drupal/module/theme inventory, cron and queue health, and heartbeats without adding browser-side code.

Install

From the Drupal project root, run:

composer require mozzy/drupal-connector
vendor/bin/drush en mozzy -y

If the project does not use Drush, enable Mozzy Connector from Extend in Drupal administration.

Add the private credentials from the Mozzy Assistance setup guide to the server environment:

MOZZY_ENABLED=true
MOZZY_ENDPOINT=https://your-mozzy-host.example/api/v1/assistance/events
MOZZY_ASSISTANCE_TOKEN=mz_live_...
MOZZY_ENVIRONMENT=production

The same values can be set server-side in settings.php when the host cannot expose environment variables to PHP:

$settings['mozzy'] = [
  'enabled' => TRUE,
  'endpoint' => 'https://your-mozzy-host.example/api/v1/assistance/events',
  'token' => 'mz_live_...',
  'environment' => 'production',
];

Keep settings.php and the token out of version control. Rebuild Drupal caches after changing configuration, then visit Configuration → System → Mozzy Connector to test the connection and run the first sync.

Drupal cron queues later syncs. Ensure the site's normal Drupal cron runs regularly; no separate Mozzy cron command is required.

Capabilities

• Heartbeat and sanitized error-level log reporting
• Drupal core, module, and theme inventory
• Drupal cron, Mozzy sync, and database queue health
• Stable event payloads across transport retries

The v1 connector does not provide backups, module updates, protected maintenance, content access, or automatic rollback. It does not transmit request bodies, cookies, sessions, user records, content entities, or environment variables.

Privacy and security

Credentials are read only from Drupal settings.php or the server environment and are never stored in exported Drupal configuration. Sensitive values in messages and structured telemetry are filtered before delivery. Transport failures never interrupt Drupal's own logging pipeline.

License

GPL-2.0-or-later.