alloydb-omni-monitor

Query AlloyDB Omni system views to diagnose locks and long-running transactions.

2|1|Updated May 25, 2026
One-click install
npx skills add https://github.com/interflownex/All-in-One --skill alloydb-omni-monitor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: alloydb-omni-monitor
Source: https://github.com/interflownex/All-in-One/tree/main/.gemini/skills/alloydb-omni-monitor
Command: npx skills add https://github.com/interflownex/All-in-One --skill alloydb-omni-monitor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @toolbox-sdk/server, and includes scripts (resource) components.

What problem does it solve?

This Skill provides deep visibility into AlloyDB Omni database instances, allowing administrators to quickly identify performance bottlenecks, locking issues, and resource-heavy transactions.

Core Features & Use Cases

  • Performance Monitoring: Retrieve high-level server state, including uptime, connection limits, and active query counts.
  • Transaction Analysis: Pinpoint long-running transactions and active locks that may be causing system degradation.
  • Configuration Auditing: Inspect PostgreSQL settings and database-level statistics to optimize resource allocation.

Quick Start

Use the alloydb-omni-monitor skill to list the top 20 longest running transactions currently active on the database.

Frequently Asked Questions about alloydb-omni-monitor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check for lock contention and long-running queries in AlloyDB Omni?

To monitor AlloyDB Omni performance, query internal system views to retrieve server state including uptime, connection limits, and active query counts. This identifies resource bottlenecks and configuration issues.

How do I monitor active connections and uptime for an AlloyDB Omni PostgreSQL instance?

To monitor AlloyDB Omni performance, query internal system views to retrieve server state including uptime, connection limits, and active query counts. This identifies resource bottlenecks and configuration issues.

Can I audit PostgreSQL configuration parameters and database statistics in AlloyDB Omni?

Yes, you can audit PostgreSQL settings and database-level statistics in AlloyDB Omni by querying internal system views. This validates configuration parameters to help optimize resource allocation.

Do I need the @toolbox-sdk/server package to troubleshoot AlloyDB Omni database issues?

Yes, the @toolbox-sdk/server package is required to troubleshoot AlloyDB Omni database issues. It executes the administrative commands needed to query internal system views for diagnostic data.

What is the best way to identify performance bottlenecks in an AlloyDB Omni production database?

The best way to identify performance bottlenecks in an AlloyDB Omni production database is querying internal system views to analyze long-running transactions and active locks. This provides deep visibility into resource-heavy operations.