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.

An asset is any data object that AnomalyArmor discovers and monitors. When you connect a database, we catalog all tables, views, and their columns.

​
Asset Hierarchy

Assets are organized in a hierarchy that mirrors your database structure:
Asset hierarchy: Data Source → Schema → Table/View → Columns
For example: snowflake.analytics.orders represents the orders table in the analytics schema of your Snowflake connection.

​
What We Track

Each asset stores:
PropertyDescriptionUse For
SchemaColumn names, types, constraintsDrift detection
FreshnessLast update timestampSLA monitoring
MetricsRow counts, null percentagesData quality
TagsAuto and custom classificationsOrganization
HistoryAll changes over timeDebugging

​
Asset Lifecycle

Assets move through states as you use AnomalyArmor:
Asset lifecycle: Discovered → Monitored → Archived
  1. Discovered: Found during discovery, no monitoring configured
  2. Monitored: Has freshness SLAs, metrics, or alert rules attached
  3. Archived: Table no longer exists in database (kept for history)

​
Finding Assets

Three ways to find assets: UI, API, or Intelligence

​
In the UI

Assets page shows your full catalog. Use filters:
  • Data Source: Filter by database connection
  • Schema: Filter by namespace
  • Tags: Filter by classification (e.g., pii:email)
  • Status: Filter by freshness state

​
Via API

from anomalyarmor import Client

client = Client()
assets = client.assets.list(schema="analytics", limit=100)

​
Via Intelligence

Ask in plain English: “Where is customer data?” or “Show me tables updated today.”

​
Asset Details

Click any asset to see:
  • Overview: Basic info, tags, description
  • Schema: Current columns with types
  • History: All schema changes over time
  • Freshness: Update timeline and SLA status
  • Metrics: Configured data quality checks

​
Common Questions

​
What counts as an asset in AnomalyArmor?

Any table or view that AnomalyArmor discovers in your connected databases. System catalogs and internal tables are excluded. Materialized views count as assets; temporary tables don’t.

​
What happens to an asset when the underlying table is dropped?

The asset moves to Archived state - removed from active monitoring but retained for history (schema snapshots, freshness timeline, past alerts). You can restore an asset if the table comes back, or delete it permanently to free a monitored-table slot.

​
Can I monitor views the same way I monitor tables?

Yes. Views are first-class assets. Schema drift, freshness (if the view has a timestamp column), and metrics all work. Note that freshness on views reflects the underlying base table’s update, not the view’s definition.

​
How do I find assets across multiple databases?

The Assets page aggregates every asset across all connected data sources. Filter by data source, schema, tag, or freshness status. You can also use the API (client.assets.list()) or ask in natural language via Intelligence (“show me tables with PII tags updated today”).

​
Next Steps

Set Up Discovery

Configure how AnomalyArmor finds your assets

Connect a Data Source

Add your first database to start discovering assets