Check evaluations recorded on every resource and account
Every check evaluation is recorded
Every check Polylane runs on a resource, cloud account or integration is now recorded and listed, for teams that want to see what was checked when nothing opened an issue.
What changed
Each time Polylane runs a check on a resource, a cloud account or an integration, the result is recorded. Resource pages list their recent evaluations, and the issues page of each cloud account and integration shows the evaluations of its checks. An evaluation that finds a real problem opens an issue; the others stay on record.
More of
AWS in the context graph
Kinesis streams, KMS keys, Secrets Manager secrets and service discovery services from your AWS accounts join the context graph. Each KMS key is linked to the resources it encrypts, such as Secrets Manager secrets.
Why it matters
A quiet issues list can mean nothing is wrong or that nothing was checked. Recorded evaluations show which checks ran on a resource and what they concluded, so you can tell the difference and see why a problem did or did not open an issue.
How to use it
- Open a resource in the context graph and select its Problems tab to see its recent check evaluations.
- For a cloud account or integration, open its page in the console to see the evaluations of its checks.
- Ask a thread, for example "Which checks ran on the
ordersqueue today, and what did they find?".
Related
Improvements
- Repositories Polylane finds the GitHub repositories that deploy to a cloud account and links them to it
- Onboarding Connecting an account or integration ends on a page that suggests what to connect next
Fixes
- Context graph An empty or failed read from a provider no longer removes resources from the context graph. A resource is removed once it has been missing for a day
- Integrations Calls to provider APIs are rate limited and shared between requests, so investigations and checks stay under provider limits