Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.anomalyarmor.ai/llms.txt

Use this file to discover all available pages before exploring further.

As a platform team, you manage data infrastructure at scale. AnomalyArmor provides unified observability across all your databases with enterprise-grade controls.
Platform Team Journey: Connect All (~10 min) → Unify (~5 min) → Integrate (~10 min) → Scale (ongoing)

​
Your Key Workflows

​
Monitor Multiple Databases

Connect all your data sources from a single pane of glass:
1

Connect All Databases

Add PostgreSQL, Databricks, Snowflake, ClickHouse, and more. Add data sources
2

Configure Discovery Schedules

Set different discovery frequencies based on criticality (hourly for prod, daily for dev).
3

Set Up Unified Alerting

Route all alerts to PagerDuty for on-call escalation. Configure PagerDuty

​
Integrate with Incident Management

Route critical alerts to your existing incident management:
PlatformIntegration
PagerDutyNative integration
OpsgenieVia webhook
ServiceNowVia webhook
Example PagerDuty routing: 
Alert Rule: Schema Change (column removed)
Severity: Critical
Route to: PagerDuty → Data Platform On-Call

​
Manage Team Access

Set up role-based access control:
RolePermissions
AdminFull access, team management, API keys
EditorConfigure alerts, create metrics
ViewerRead-only access to all data
Team management guide

​
Build Custom Integrations

Use the API to integrate AnomalyArmor with your internal tools: 
from anomalyarmor import Client

client = Client(api_key="aa_live_xxx")

# Get all assets across all sources
assets = client.assets.list()

# Export to your internal data catalog
for asset in assets:
    sync_to_internal_catalog(asset)

# Monitor API key usage
keys = client.api_keys.list()
for key in keys:
    print(f"{key.name}: {key.last_used}")
API documentation

​
Security and Compliance

Review our security posture:
  • Read-only access: We only query metadata, never your data
  • Query validation: Open-source Query Gateway validates all SQL
  • Encryption: AES-256 at rest, TLS 1.3 in transit
  • Audit logs: All administrative actions logged
Security overview
FeatureWhy You Need It
Multi-source monitoringUnified view across all databases
PagerDuty integrationIncident escalation
Team managementRole-based access control
API accessCustom integrations

​
Common Tasks

Add Data Source

Connect PostgreSQL, Databricks, Snowflake, and more

Configure PagerDuty

Route critical alerts to on-call

Manage Team

Invite users and set permissions

API Keys

Create and manage API access

​
Common Questions

​
How many databases can I connect to AnomalyArmor?

Every plan supports multiple connections; the limit is set by plan capacity (total tables monitored), not by connection count. Enterprise supports unlimited tables and VPC peering / PrivateLink per source. See Data Sources.

​
Can I route alerts to PagerDuty, Opsgenie, or ServiceNow?

PagerDuty has a native integration. Opsgenie and ServiceNow are supported via webhook destinations. You can route by severity so breaking changes page on-call while low-priority events go to Slack or email. See PagerDuty integration.

​
What RBAC roles are available?

Viewer (read-only), Editor (configure alerts and metrics), Admin (full access plus team and API keys). SSO with SAML 2.0 and SCIM provisioning is available on Enterprise. See Team management.

​
Can I sync AnomalyArmor’s asset inventory to our internal data catalog?

Yes. Use the REST API or Python SDK to pull the asset list (client.assets.list()) and push it into your catalog. Changes are available via schema-change webhooks so syncs stay current. See API overview.

​
How does AnomalyArmor fit our compliance requirements?

Read-only metadata access, AES-256 at rest, TLS 1.3 in transit, audit logs for every admin action, GDPR DPA and HIPAA BAA available. VPC peering and PrivateLink keep traffic off the public internet on Enterprise. See Security Overview.