Quick Start Guide
Welcome to GlideHubAi. This guide takes you from zero to a fully operational monitoring and automation platform in under 30 minutes. All six modules are available from the moment your deployment is live.
Before starting, ensure your environment meets the
system requirements. For SaaS deployments, skip the installation step and proceed directly to Step 2.
Step 1 — Deploy the Platform
GlideHubAi supports three deployment models: SaaS (recommended), on-premises VM, and Kubernetes helm chart.
helm repo add glidehubai https://charts.glidehubai.com
helm repo update
helm install glidehubai glidehubai/glidehubai \
--namespace glidehubai \
--create-namespace \
--set global.license="YOUR_LICENSE_KEY" \
--set global.domain="glide.yourdomain.com" \
--set persistence.storageClass="standard" \
--values my-values.yaml
kubectl wait --for=condition=ready pod \
-l app.kubernetes.io/instance=glidehubai \
--timeout=300s -n glidehubai
Step 2 — Add Your First Devices
Navigate to Network Monitoring → Hosts → Add Host. Enter the device IP, SNMP community string or credentials, and select a template. GlideHubAi will auto-discover the device type and apply the correct monitoring template.
curl -X POST https://your-glide.domain/api/v3/hosts/import \
-H "Authorization: Bearer YOUR_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"hosts": [
{
"hostname": "core-router-01",
"ip": "10.0.0.1",
"template": "Cisco_IOS_Router",
"snmp_community": "vault:secret/snmp/core",
"groups": ["Core Network", "DC1"]
}
]
}'
Step 3 — Configure Log Collection
Point your log sources at the GlideHubAi collector. Add the following to your server's log forwarding configuration to enable RELP+TLS delivery:
module(load="omrelp")
action(
type="omrelp"
target="collector.glidehubai.internal"
port="2514"
tls="on"
)
Step 4 — Create Your First Automation
Navigate to Automation Engine → Workflows → New Workflow. Choose a trigger (Alert Trigger is recommended for first workflow), drag an action node onto the canvas, connect them, and click Execute to test.
System Requirements
| Component | Minimum | Recommended (Production) |
|---|
| CPU | 8 cores | 16+ cores |
| RAM | 16 GB | 64 GB |
| Storage | 200 GB SSD | 2 TB NVMe (time-series DB) |
| OS | Ubuntu 20.04 / RHEL 8 | Ubuntu 22.04 LTS |
| Kubernetes | v1.24+ | v1.27+ (for Helm deployment) |
| Network | 1 Gbps | 10 Gbps (for 10,000+ devices) |
| Devices supported | Up to 5,000 | 100,000+ (horizontal scale) |
Platform Architecture
GlideHubAi uses a microservices architecture deployed on Kubernetes. Key services include the monitoring collector, syslog ingestion pipeline, time-series database, automation engine, compliance report renderer, and the unified API gateway.
Architecture Diagram — Download the full architecture diagram PDF from your customer portal, or request it from your enterprise architect during onboarding.
REST API v3
GlideHubAi provides a comprehensive REST API at /api/v3/. All endpoints require Bearer token authentication. The API is documented in OpenAPI 3.0 format — importable directly into Postman or Insomnia.
GET /api/v3/alerts?status=active&severity=HIGH,DISASTER
Authorization: Bearer YOUR_TOKEN
{
"total": 3,
"alerts": [
{
"id": "alert-1842",
"host": "db-server-05",
"metric": "system.disk.util",
"severity": "HIGH",
"value": "94%",
"since": "2025-03-22T11:42:00Z",
"acknowledged": false
}
]
}