What Gildyard reads
Exactly what the two roles let it see, what it never reads, and how it turns numbers into smoke, cobwebs and price tags.
What it reads
- Your resources' names, types, regions, sizes and resource groups, from Azure Resource Graph.
- Activity numbers from Azure Monitor, such as requests, runs, errors and CPU. Numbers only, never contents.
- This month's cost per resource, from Cost Management.
What it never reads or does
- The data inside storage accounts, databases or queues.
- Secrets, keys, connection strings or app settings. Neither role can read them.
- A copy of your tags. They come with the resource list, and Gildyard drops them without storing them.
- Any change to Azure. Both roles are read-only.
What it keeps
For each yard, the latest picture and the recent events, in Azure's Spain Central region, in the EU. Disconnecting a yard deletes all of it. The activity log of your workspace keeps who did what in Gildyard: who connected or disconnected a yard, who joined, who changed roles, who made a TV link.
How a piece gets its look
- Sparks: something happened in the last hour. Requests, executions, transactions, messages; for machines (virtual machines, scale sets, clusters, App Service plans), CPU at 5% or more over the last 15 minutes.
- Smoke: errors in the last hour. 5xx responses, failed runs, server errors.
- Cobwebs: nothing happened for longer than that kind of resource should rest. Two weeks for most things, ninety days for storage and key vaults, thirty for some others, and never longer than the resource has existed.
- A price tag: idle, and Cost Management says it is still billing. The tag shows this month's cost so far; under 1 in your billing currency this month (a euro, a dollar), there is no tag.
- Greyed out: stopped, deallocated, being deleted or failed to deploy, as Azure reports the resource's own state.
- A red gauge on a vault: a database above 85%: its CPU, or for Cosmos DB, its throughput.
- Just the piece: quiet. Nothing happened in the last hour (for machines, CPU under 5% over the last 15 minutes), or there is nothing to read. Gildyard reads no activity for some kinds of resource, such as virtual networks, and when Azure Monitor refuses a read, the piece stays quiet too.
Gildyard reads activity, errors and load from Azure Monitor every five minutes, so sparks, smoke and gauges can take up to ten minutes to appear. When Azure has no data for something, the yard leaves it alone instead of guessing: a quiet piece is never called idle on silence.
The resource list refreshes every minute, so a new, stopped or deleted resource shows within a minute or two. Cost figures refresh a few times a day; when Azure throttles that query, the last good figures stay rather than going blank.