ServiceRadar Quickstart
Follow these condensed steps to get ServiceRadar collecting data within an hour. Each phase links to longer-form docs so you can dive deeper when needed.
1. Pick a Deployment Path
- Docker Compose – fastest path for local trials. Follow the Docker setup guide to launch web-ng, core-elx, agent-gateway, and supporting services with pre-baked defaults.
- Kubernetes – production-style clusters or cloud POCs. Use the Helm configuration to install charts and align values with your environment.
- Edge Agents – onboard edge agents with the Edge Agent Onboarding flow.
2. Bootstrap Access
- Generate TLS material with the Self-Signed Certificates guide or import your existing CA chain.
- Sign in with the bootstrapped admin user (Helm/Docker Compose generate this for you) and review Settings -> Authentication to enable Direct SSO or Gateway Proxy if desired.
3. Ingest Device Data
Pick one telemetry channel to validate the pipeline end to end:
- SNMP – configure collectors by following the SNMP ingest playbook.
- Syslog – forward device logs to the ServiceRadar stack via the Syslog ingest guide.
- OTEL – export traces and metrics toward the OTLP endpoint documented in the OTEL integration page.
Once the first data source is healthy, layer on additional protocols through the Get Data In section.
4. Explore the UI
- Sign in to the dashboard at
https://<web-host>and bookmark the SRQL explorer. - Use Tools Pod to sanity check JetStream consumers and CNPG connectivity during debugging.
5. Automate Integrations
When the core deployment is stable, connect inventory and security feeds:
- Sync Armis devices with the Armis integration doc.
- Pull topology from NetBox using the NetBox integration guide.
6. Validate Health
- Run smoketests (or your own synthetic checks) to confirm alerting.
- Review the Troubleshooting Guide for quick fixes to common onboarding blockers.