Glossary · Architecture, deployment and data
Integrations
The systems REAP reads from and writes to: ITSM (ServiceNow (opens in a new tab), Jira (opens in a new tab), ManageEngine), PAM (CyberArk (opens in a new tab)), collaboration (Slack (opens in a new tab), Teams), identity (Okta (opens in a new tab), Entra ID (opens in a new tab)), cloud and controllers, and multi-vendor network estates; NetBox (opens in a new tab) reconciliation On request; HashiCorp Vault (opens in a new tab), SolarWinds (opens in a new tab), Zabbix (opens in a new tab), PagerDuty (opens in a new tab), Opsgenie (opens in a new tab), Confluence (opens in a new tab) and SharePoint (opens in a new tab) are Planned, not available today.
In REAP
Read-only by default; findings and evidence links written back to the ticket. REAP collects its own telemetry today, including flow records where you configure them; incidents your monitoring raises reach REAP through ServiceNow (opens in a new tab) or Jira (opens in a new tab). See the integrations page for each status.
Related terms
More in architecture, deployment and data
- Air-gapped
- Allow-list
- Connector cluster
- Customer Cloud
- Customer On-Prem
- Data classes
- Data residency
- Deployment models
- gNMI
- Model endpoint
- Model-training policy
- Multi-tenancy
- Read-only credentials and service accounts
- REAP Cloud (SaaS)
- Retention
- Secrets and tokens
- Single sign-on (SSO)
- Telemetry
- Tenant isolation
- TLS and the outbound tunnel
- Topology
- Virtual IP (VIP)
Bring us your last P1.
Keep the root cause to yourself; in a 30-minute session we walk through how REAP would have investigated it, evidence first. The replay on your own network happens inside the proof of value.