Advisories

Advisories are recommendations attached to individual resources in your topology. The platform derives them from each resource's configuration, its recent activity, and the quality of the telemetry it emits. Every advisory names the problem, explains why it matters, and states the fix.

Each advisory carries three attributes:

• Category: observability, resilience, security, data protection, or lifecycle.
• Severity: warning or info.
• Fixability: fixable in place when an agent can change the setting through a provider API call, or guidance when the fix needs a recreate or manual steps.

Some examples:

Telemetry-quality advisories such as "Serving traffic but emitting no logs" fire only after the condition persists across several consecutive checks. They stay silent while a configuration advisory already names the root cause: if logging is disabled on a Worker, you see that advisory, not the symptom on top of it.

Where advisories appear

Open a resource node in the topology and its active advisories appear in the node panel, one at a time. Warnings lead, and a counter lets you step through the rest. A resource with an observability advisory is also marked as an observability gap on the node itself.

The galaxy view shows the workspace-wide rollup: advisories grouped by rule, each with the count of affected resources, warnings first. Repositories carry advisories too and appear in the same rollup.

Fix an advisory with a thread

Every advisory has a button that starts a thread about it:

• Ask Polylane to fix it on advisories fixable in place. The thread opens with the resource linked, the advisory, and its remediation, and asks the agent to apply the fix or walk you through it.
• Ask Polylane how to fix it on guidance advisories. The thread asks the agent for remediation steps instead.

For example, fixing "Logs are disabled" on a Worker named payments-api opens a thread seeded with:

payments-api: Logs are disabled. Logs are disabled on this Worker, so its
invocation logs aren't collected. Polylane can't read this Worker's logs.
Enable logs in the Worker's observability settings. Can you fix this for me,
or walk me through how to turn it on?

Ignore an advisory

Click Ignore to dismiss an advisory on a specific resource. The dismissal records who ignored it and when. Ignored advisories drop out of the node panel stepper and the workspace rollup, and move to an Ignored list on the node. Click Restore to bring one back.

Advisories and resource tiers

Lifecycle advisories (idle, barely used, idle and disconnected) are computed from the same activity metrics agents collect when assigning resource tiers, and only for production resources. The workspace rollup also reports monitoring coverage alongside advisories: how many resources can be monitored, how many of those sit at tier 4 (the Minimal tier), and how many have an open observability advisory.

Try it from your coding agent:

Use Polylane to list the advisories on my most critical resources and tell me which ones can be fixed in place.