Skip to main content

Asset Management: Metric Reference

This page is the source of truth for the in-app Explain this panels on the Asset Management page (/assets). Each section is written once as a content partial under _explain/assets/ and rendered both here and inside the app's info panel (scripts/build-explain.mjs compiles the registry).

Asset Management requires the ManageDatabases permission, held by Admin, SuperAdmin, and DBA by default. The single-asset detail view is documented separately in the Detail reference, and the registration wizard in the New Asset reference.

Database servers monitored by the Logstag agent — one asset per host, and every database it runs is picked up automatically once the agent connects.

How it's calculated​

  • The page requires the ManageDatabases permission. Admin, SuperAdmin, and DBA hold it by default; anyone else is kept off the route before it loads.
  • The list is backed by a paginated instances endpoint — search text, and the Engine, Environment, Status, Health, and Version filters all round-trip to the server rather than filtering a client-side cache.
  • "Add asset" opens the three-step registration wizard. An asset represents a server, not an individual database — Database Explorer is where per-database operational data lives.

Reading it​

Use the column-header filters to narrow the fleet — by engine, environment, connection status, health range, or version — before opening a row. Click a row to reach the asset's detail view for connection, configuration, and integration management.

Database Instances​

Every registered instance, with its engine, environment, connection status, health, and agent-reported version.

How it's calculated​

  • Instance shows the instance name, falling back to the server's internal name when no instance name is set.
  • Engine shows the database engine icon and label. Environment shows the instance's environment label, or an em dash when none is set.
  • Status is derived from the connection flag, not observed live: Connected when the instance has an active agent connection, Disconnected otherwise. The backend flips a stale connection to Disconnected after roughly 5 minutes without agent traffic.
  • Health shows the latest health score as a percentage, or an em dash when no assessment has run yet. Version shows the agent-reported short version string, truncated with a tooltip for long values.
  • Filters for every column live in that column's header menu — Engine and Status are multi-select, Environment is a searchable combobox built from the instances already in the org, Health is a min/max range, and Version is a text match.

Reading it​

Filter Status to Disconnected to find servers that need agent attention — the table has no sort, only filters. A Connected asset can still show a low Health score: health and connectivity are independent signals, so check both before assuming an asset is healthy.