ConHive Agent Modules
The ConHive Agent’s functionality is provided through a set of specialized modules. Each module handles a specific aspect of device management.
(This page can serve as an overview, potentially linking to sub-pages for each module if the documentation becomes very detailed. Alternatively, describe each module here.)
Core Modules
Section titled “Core Modules”🚦 Status Manager
Section titled “🚦 Status Manager”- Purpose: Monitors device operational status (power, internet, resources like CPU/RAM).
- Features: Captures data locally and/or sends to the server. Sends alerts for critical resource usage.
- Configuration:
statusmanager.json
📃 Log Manager
Section titled “📃 Log Manager”- Purpose: Tracks and stores agent and device activity logs.
- Features: Allows filtering by time/severity. Can forward error logs automatically.
- Configuration:
logmanager.json
🎛️ Process Manager
Section titled “🎛️ Process Manager”- Purpose: Provides an overview of active processes.
- Features: Lists process names, PIDs, statuses. Allows process termination via API.
- Configuration:
processmanager.json
🛰️ Twin Manager
Section titled “🛰️ Twin Manager”- Purpose: Manages the device’s digital twin information.
- Features: Extracts and transmits device hardware/software details to the server. Provides local API access for device details.
- Configuration:
twinmanager.json
🖥️ Shell Manager
Section titled “🖥️ Shell Manager”- Purpose: Facilitates secure remote shell access.
- Features: Interactive command-line sessions. Supports shared sessions. Securely logs activity.
- Configuration:
shellmanager.json
🎛️ Control Manager
Section titled “🎛️ Control Manager”- Purpose: Executes commands directly on the device without SSH.
- Features: Runs Bash/Shell commands. Stores output locally or transmits to the server.
- Configuration:
controlmanager.json
📁 File Manager
Section titled “📁 File Manager”- Purpose: Manages files and folders on the device.
- Features: Supports reading, writing, deletion, and file transfers between the device and server.
- Configuration:
filemanager.json
📊 Metric Manager
Section titled “📊 Metric Manager”- Purpose: Monitors agent and device performance metrics.
- Features: Transmits data for analysis. Can integrate with tools like Prometheus.
- Configuration:
metricmanager.json
🛰️ Geo Manager
Section titled “🛰️ Geo Manager”- Purpose: Tracks the device’s geographic location.
- Features: Sends periodic updates to the server. Supports real-time monitoring and geofencing via API.
- Configuration:
geomanager.json
⏰ Cron Manager
Section titled “⏰ Cron Manager”- Purpose: Manages scheduled tasks (cron jobs) on the device.
- Features: Provides local storage and API access for job management.
- Configuration:
cronmanager.json
📦 App Manager
Section titled “📦 App Manager”- Purpose: Oversees application lifecycle management.
- Features: Manages installation, uninstallation, and updates. Supports pre/post-execution scripts.
- Configuration:
appmanager.json
Additional Modules
Section titled “Additional Modules”🔧 Other Modules
Section titled “🔧 Other Modules”- Audio Management: Audio recording, playback, and management.
- Alert Management: Configures custom alerts and dispatches notifications.
- Automation Manager: Automates tasks and manages cron jobs via API.
- Event Dispatcher: Reliable creation and dispatch of events for server notifications.
- UI Management: Simplifies dynamic UI creation/customization for the agent interface.
(Configuration files and details for these should be added as needed)