Operations
Ansible automation against live inventory
Identify a problem with a device in inventory, pick a playbook, and launch remediation in seconds—without leaving ServiceRadar for a separate AWX session.
Execute Ansible playbooks against devices or groups in ServiceRadar inventory through AWX or Red Hat Ansible Automation Platform (AAP), with RBAC, live per-host outcomes, full audit, and playbooks sourced from AWX or your own git repositories.
From signal to fix in one workflow
Most teams discover issues in one tool, then switch to AWX, a spreadsheet of hostnames, and a chat thread to run the fix. ServiceRadar keeps inventory and automation together so operators select ansible-managed devices, choose a playbook, and launch with live status on the same platform.
- Select one device or bulk-select a group from live inventory
- Launch approved playbooks with survey variables and typed inputs
- Watch per-host ok/changed/failed outcomes update as the run progresses
- Search every run and task result in the universal log viewer
Built for AWX and Red Hat Ansible Automation Platform
ServiceRadar does not replace your Ansible controller. It talks to a customer-side AWX or Red Hat Ansible Automation Platform instance through a ServiceRadar agent that already sits on the network path your controller lives on—so private automation stays private. Carver Automation is a Red Hat partner, and this integration is built to meet operators where AAP and AWX already run.
- Register AWX or Red Hat AAP controllers reachable from your edge agents
- Keep machine credentials, vault secrets, and SSH keys inside the controller
- Use purpose-scoped tokens for sync versus execution
- Mark devices ansible-managed as controller inventory syncs into discovery
A Red Hat partnership rooted in open automation
As a Red Hat partner, we invest in the same open automation stack enterprises standardize on: Ansible, AWX, and Ansible Automation Platform. ServiceRadar sits beside that stack—inventory, discovery, and operator workflows on our side; job templates, credentials, and execution environments on yours—so hybrid and edge estates can automate without a second source of truth for what is on the network.
- Aligns with Red Hat Ansible Automation Platform deployments you already operate
- Supports community AWX and enterprise AAP control paths
- Keeps automation policy and secrets in the controller, not copied into monitoring tools
- Gives NOC and platform teams one inventory-driven launch surface
Playbooks from AWX/AAP and from your git repos
Operators browse a unified catalog. AWX and AAP job templates are mirrored automatically. Git repositories—public or private HTTPS, including GitHub—can be registered so playbooks are cataloged, parsed, and bound to job templates before they become launchable.
- Controller-sourced templates appear as ready-to-run playbooks
- Git-sourced playbooks stay under your version control and review process
- Bind git playbooks to job templates when you are ready to execute
- Optional schedules fire the same path as a human-initiated run
RBAC that matches real operations teams
Not everyone who can view inventory should be able to launch playbooks. ServiceRadar gates Ansible actions with dedicated permission keys so viewers can inspect, operators can launch and cancel, and admins can manage controllers, repositories, and schedules.
- Hide Run Task when the user lacks launch permission
- Separate view, launch, cancel, and manage privileges
- Keep operator launches inside ServiceRadar for audit and preflight evidence
- Avoid bypassing policy with freeform controller UI access on automation principals
Audit and search that replace stitched tooling
Every run is a first-class resource with targets, plays, tasks, and outcomes. State transitions and task results also land as structured events operators can search by device, playbook, task name, or failure status—without bolting on a separate ARA-style stack next to AWX or AAP.
- Live run pages for one job, with per-host detail
- Cross-run search across controllers and devices
- Retention controls for detail versus summary history
- Open-source platform you can inspect and self-host
FAQs
Do we have to move AWX or AAP into ServiceRadar's network?
No. Controllers usually stay in your private network. A ServiceRadar agent that can reach AWX or Red Hat Ansible Automation Platform bridges the control path so core never needs direct access to your controller.
Are you a Red Hat partner?
Yes. Carver Automation is a Red Hat partner. ServiceRadar integrates with Red Hat Ansible Automation Platform and community AWX so enterprises can drive playbooks from live inventory without abandoning the automation stack they already run.
Can we use playbooks from GitHub?
Yes. Register HTTPS git repositories (including GitHub) as playbook sources. ServiceRadar catalogs and parses them; bind each git-sourced playbook to an AWX or AAP job template before launch.
How do you secure who can run automation?
Ansible actions use dedicated RBAC keys. Viewers can browse runs and catalog entries; only operators and admins with launch permission can start jobs. Controllers, repositories, and schedules require manage permissions.
Where are the deep technical docs?
Architecture, operator setup, launch workflows, configuration, and the full RBAC matrix live in the Ansible integration docs .