System Maintenance, AI & Notification Settings
To ensure the long-term health and efficiency of your CollectorCtrl control plane, administrators must configure AI assistance engines, manage database indexing, track license metrics, and configure alert routers.
1. AI Provider Configuration
CollectorCtrl integrates AI models to power automated dashboard migrations, metric translation parsing, and semantic mapping generation.

Supported AI Providers
You can configure providers in the Settings > AI Settings panel:
- OpenAI (SaaS): Provide your API Key and select models (e.g.
gpt-4oorgpt-3.5-turbo). - Azure OpenAI (Enterprise Private Cloud): Define your API Key, Deployment Name, API Version, and base endpoint URL. This ensures queries are processed inside your corporate boundaries.
- Ollama (Self-Hosted local LLMs): Link to a local Ollama instance (e.g.
http://localhost:11434) running models likellama3orcodegemma.
2. Dynamic Environment Rules
Environment mapping rules assign incoming agents to organizational categories based on their startup attributes.

- Rule Definition: Define mapping patterns (e.g., if host attribute
k8s.cluster.namecontainsprod, assign to environmentProduction). - Evaluation Trigger: The environment engine processes these rules during the initial OpAMP registration handshake, eliminating manual environment classification.
3. Database Maintenance & Operations
Telemetry collection tables store high-frequency audit and status records. Database maintenance prevents performance degradation over time.

SQLite Pruner Tasks
In developer configurations, SQLite runs an automatic background task (StartSandboxPruner) every 5 minutes to delete database records older than 1 hour, preventing SQLite write-lock blocks.
PostgreSQL Production Optimization
For production Postgres backends, configure regular database maintenance:
- Table Indexing: Ensure active indexes on
agent_id,policy_id, andcreated_atare optimized. - VACUUM Operations: Run periodic autovacuum tasks on tables prone to high update frequencies:
config_histories(stores historical YAML edits)policy_snapshots(stores canary and active configurations)telemetry_governor_logs/telemetry_governor_spans(temporary taps)
- pg_cron Setup: We recommend scheduling a nightly vacuum/analyze cron job:
SELECT cron.schedule('0 2 * * *', 'VACUUM ANALYZE config_histories;');
4. Community & Enterprise Licensing Configuration
Under the Licensing tab, you can view the active status of your system license:
- Community Edition (Default): CollectorCtrl operates by default as the Community Edition. This tier is fully unrestricted, allowing you to connect unlimited agent nodes and utilize all features with no expiration or capacity lock-ins.
- Enterprise Upgrades: If your organization requires custom SLA agreements, dedicated support contracts, or custom enterprise signing keys, you can apply an Enterprise license. Paste your new cryptographic license string into the field and click Apply License.
5. Notification Center Architecture
The Notification Center acts as an internal message broker, routing system events to communication targets.
+---------------------------------------------+
| System Event Trigger |
| (Agent Offline / Drift / Config Error) |
+---------------------------------------------+
|
v
+---------------------------------------------+
| Notification Center |
+---------------------------------------------+
/ | \
/ | \
v v v
[SMTP Emails] [Slack Webhooks] [Teams Channels]
Supported Alert Channels
- SMTP Email Digests: Dispatches error and drift reports to system operators.
- Slack & MS Teams Webhooks: Sends real-time notifications to team channels.
- Web Console Alerts: Displays status flags in the Admin UI dashboard.
CollectorCtrl