Control types for @turbot/turbot

• Turbot > Active Grant Expiration
• Turbot > Cache
• Turbot > Cache > Health Check
• Turbot > Grant Expiration
• Turbot > Mod > Auto Update
• Turbot > Mod > Event Monitor
• Turbot > Mod > Health
• Turbot > Mod > Installed
• Turbot > Mod > Process Monitor
• Turbot > Mod > Runnable Monitor
• Turbot > Notifications
• Turbot > Policy Setting Expiration
• Turbot > Smart Process Retention
• Turbot > Smart Retention
• Turbot > Type Installed
• Turbot > Webhook Secret Rotation
• Turbot > Workspace
• Turbot > Workspace > Background Tasks
• Turbot > Workspace > Health Control
• Turbot > Workspace > Migration
• Turbot > Workspace > Usage

Turbot > Active Grant Expiration

Ensure that a active grant is deleted on expiration.

Turbot > Cache

Turbot > Cache > Health Check

Check cache health status.

Turbot > Grant Expiration

Ensure that a grant is deleted on expiration.

Turbot > Mod > Auto Update

Check mod health status

Turbot > Mod > Event Monitor

Check controls and policies that have defaultInterval attribute in their definition. Restart these controls and policies if applicable.

Turbot > Mod > Health

Check mod health status

Turbot > Mod > Installed

Ensure that a mod is installed correctly.

Turbot > Mod > Process Monitor

Check running Turbot Processes, terminate if necessary

Turbot > Mod > Runnable Monitor

Check controls and policies that are in error state and re-run if they are not already scheduled for a re-run.

Turbot > Notifications

Turbot notifications.

Turbot > Policy Setting Expiration

Ensure that a policy setting is deleted on expiration.

Turbot > Smart Process Retention

One of the principal design goals of Turbot is to enable change - to help ensure security, reliability, and consistency in dynamic environments.
As a result, capturing change and storing historical information are fundamental to the way Turbot operates.
In fact, Turbot creates a new version for each process run and change of state e.g. a new version when process goes from starting to handling.

While there is some benefit in storing all versions of all entities forever, there is a tradeoff in performance and storage capacity.
Every version must be stored and indexed.

Turbot Smart Retention helps manage the compromise between too much data and too little information.

Turbot > Smart Retention

One of the principal design goals of Turbot is to enable change - to help ensure security, reliability, and consistency in dynamic environments.
As a result, capturing change and storing historical information are fundamental to the way Turbot operates.
In fact, Turbot creates a new version for each resource every time that resource is changed, providing a full history of the resource. Controls, Policy Settings, Policy Values, and Logs are also versioned per resource.

While there is some benefit in storing all versions of all entities forever, there is a tradeoff in performance and storage capacity.
Every version must be stored and indexed. Every version added is another to search through.

Turbot Smart Retention helps manage the compromise between too much data and too little information.

Turbot > Type Installed

Ensure that a control, policy or action is installed correctly. Deploys control and action Lambda functions.

Turbot > Webhook Secret Rotation

Determine whether the Webhook secret requires rotation

Turbot > Workspace

Turbot > Workspace > Background Tasks

The control is used to perform background tasks in turbot.

This ensures the policy values are updated correctly after the resource movement.
It also ensures that policy hierarchy settings are verified and missing records created after smart folder attachment.

Turbot > Workspace > Health Control

Slow queries in idle state - Queries should run quickly and should not be idle for more than a couple of minutes.

Top 5 unused indexes - Indexes are used to ensure good query performance, but sometimes those indexes become unused due to changes in the query patterns or other (competing) indexes. Unused indexes are an opportunity for cleanup and reduced database size / workload. For most workspaces, we expect this list to be empty. If some indexes have a scan frequency (idx_scans) of zero, then they are not being used.

Biggest indexes and tables - Insight into the tables and indexes using the most database space in this workspace. This gives us clarity into opportunities for improvement and the primary drivers of disk space cost.

Last run autovacuum - Autovacuum is an important part of database health which clears out deleted data. It is run periodically based on table sizes and the rate of change. We'd expect autovacuum to run within the last week for most tables.

Live and dead tuples - Deleted data that has not yet been, or cannot be, vacuumed up is reported as dead tuples. For most tables, we expect the ratio of dead tuples to be low compared to live tuples. This gives us insight into the current ratio and effectiveness of autovacuum operations.

Invalid indexes - There should not be any invalid indexes in the database. An invalid index will not be used in queries because they might be incomplete, however it will still consume update overhead hampering update / insert performances.

Bloated indexes - There should not be any bloated indexes in the database.

Turbot > Workspace > Migration

Migration control to perform bulk operations such as large table updates in batches.

Turbot > Workspace > Usage

Log workspace usage to turbot.com.