Recued
Menu
← Back to recipes

Fly.io machine investigation brief

by recued-core v1 9 views

Use “Fly.io machine investigation brief” in Recued. It provides a read-only investigation brief for one provider record Machine.

How it works 18 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (18 steps)
app_key trim
Trim whitespace from setting app name
machine_key trim
Trim whitespace from setting machine id
machine ?
events_raw ?
processes_raw ?
memory ?
metadata ?
versions_raw ?
defaults defaults
Apply defaults
event_count count
Count items in events
process_count count
Count items in processes
version_count count
Count items in versions
summarize ?
event_rows slice
Take a subset of
process_rows slice
Take a subset of
event_table to_table
Format results as a data table
process_table to_table
Format results as a data table
card to_summary
Format results as a summary card
Settings 6 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

flyio setting =
focus setting = Summarize the Fly.io Machine for state, region, image/config, recent events, process pressure, memory posture, metadata signal, and next checks. Do not invent facts outside the Fly.io data.
app name setting =
row limit setting = 12
machine id setting =
max length setting = 900

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Permissions it requires

Read your Flyio connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

About

Tags

flyio flyiofly.iomachineeventsprocessesmemoryai-summarypack:flyio

Details

18 steps 6 configurable settings recipe_id: machine-investigation-brief-flyio