Advisories
Advisories are recommendations attached to individual resources in your topology. Each one names the problem, explains why it matters, and states the fix.
What it does
Polylane derives advisories from each resource's configuration, its recent activity, and the quality of the telemetry it emits. Every advisory carries three attributes.
| Attribute | Values | Description |
|---|---|---|
| Category | observability, resilience, security, data protection, lifecycle | What kind of risk the advisory describes. |
| Severity | warning, info | Warnings lead wherever advisories are listed. |
| Fixability | in place, guidance | In place: an agent can change the setting through a provider API call. Guidance: the fix needs a recreate or manual steps. |
Some examples:
| Resource | Advisory | Category | Fixability |
|---|---|---|---|
| Cloudflare Worker | Logs are disabled | observability | in place |
| Amazon RDS database | Automated backups are disabled | resilience | in place |
| Amazon S3 bucket | Public access is not fully blocked | security | in place |
| Amazon RDS database | Storage is not encrypted | data protection | guidance |
| AWS target group | Health checks are disabled | resilience | in place |
| Any resource | Serving traffic but emitting no logs | observability | guidance |
Telemetry-quality advisories such as "Serving traffic but emitting no logs" fire only after the condition persists across three 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. Lifecycle advisories come from the same activity metrics that assign resource tiers.
Where to find it
Open a resource in the topology and its active advisories appear in the node panel, one at a time, warnings first, with a counter to step through the rest. The Advisories page in the console shows the workspace-wide rollup: advisories grouped by rule with the count of affected resources, plus how many resources can be monitored, how many sit at the Minimal tier, and how many have an open observability advisory. Repositories carry advisories too and appear in the same rollup.
Fix or ignore one
Every advisory has a button that starts a thread about it, opened with the resource linked and the advisory's message and remediation as the first prompt. Ask Polylane to fix it appears on advisories fixable in place and asks the agent to apply the fix or walk you through it; Ask Polylane how to fix it appears on guidance advisories and asks for remediation steps.
Click Ignore to dismiss an advisory on one resource. The dismissal records who ignored it and when, and the advisory leaves the node panel and the rollup for an Ignored list on the node, where Restore brings it back. Dismissals prune themselves once the underlying condition clears, so if the same problem returns the advisory fires again instead of staying silently ignored.