[{"data":1,"prerenderedAt":2691},["ShallowReactive",2],{"navigation:zh-tw":3,"integrations-catalog":159,"\u002Fzh-tw\u002Ftools":2564,"\u002Fzh-tw\u002Ftools-surround":2668,"\u002Fzh-tw\u002Ftools-alternates":2673},[4],{"title":5,"path":6,"stem":7,"children":8,"page":20},"Zh Tw","\u002Fzh-tw","zh-tw",[9,21,47,65,87,119,142],{"title":10,"path":11,"stem":12,"children":13,"icon":20},"開始使用","\u002Fzh-tw\u002Fgetting-started","zh-tw\u002F1.getting-started\u002F1.index",[14,16],{"title":15,"path":11,"stem":12},"快速入門",{"title":17,"path":18,"stem":19},"Polylane如何運作","\u002Fzh-tw\u002Fgetting-started\u002Fhow-it-works","zh-tw\u002F1.getting-started\u002F2.how-it-works",false,{"title":22,"path":23,"stem":24,"children":25,"icon":20},"連接","\u002Fzh-tw\u002Fconnect","zh-tw\u002F2.connect\u002F1.index",[26,27,31,35,39,43],{"title":22,"path":23,"stem":24},{"title":28,"path":29,"stem":30},"整合","\u002Fzh-tw\u002Fconnect\u002Fintegrations","zh-tw\u002F2.connect\u002F2.integrations",{"title":32,"path":33,"stem":34},"雲端","\u002Fzh-tw\u002Fconnect\u002Fclouds","zh-tw\u002F2.connect\u002F3.clouds",{"title":36,"path":37,"stem":38},"Topology","\u002Fzh-tw\u002Fconnect\u002Ftopology","zh-tw\u002F2.connect\u002F4.topology",{"title":40,"path":41,"stem":42},"儲存庫","\u002Fzh-tw\u002Fconnect\u002Frepositories","zh-tw\u002F2.connect\u002F5.repositories",{"title":44,"path":45,"stem":46},"Memories","\u002Fzh-tw\u002Fconnect\u002Fmemories","zh-tw\u002F2.connect\u002F6.memories",{"title":48,"path":49,"stem":50,"children":51,"icon":20},"偵測","\u002Fzh-tw\u002Fdetect","zh-tw\u002F3.detect\u002F1.index",[52,53,57,61],{"title":48,"path":49,"stem":50},{"title":54,"path":55,"stem":56},"問題","\u002Fzh-tw\u002Fdetect\u002Fissues","zh-tw\u002F3.detect\u002F2.issues",{"title":58,"path":59,"stem":60},"Pull request審查","\u002Fzh-tw\u002Fdetect\u002Fpull-request-reviews","zh-tw\u002F3.detect\u002F3.pull-request-reviews",{"title":62,"path":63,"stem":64},"Advisories","\u002Fzh-tw\u002Fdetect\u002Fadvisories","zh-tw\u002F3.detect\u002F4.advisories",{"title":66,"path":67,"stem":68,"children":69,"icon":20},"調查與修復","\u002Fzh-tw\u002Finvestigate","zh-tw\u002F4.investigate\u002F1.index",[70,71,75,79,83],{"title":66,"path":67,"stem":68},{"title":72,"path":73,"stem":74},"Threads","\u002Fzh-tw\u002Finvestigate\u002Fthreads","zh-tw\u002F4.investigate\u002F2.threads",{"title":76,"path":77,"stem":78},"修復執行","\u002Fzh-tw\u002Finvestigate\u002Ffix-runs","zh-tw\u002F4.investigate\u002F3.fix-runs",{"title":80,"path":81,"stem":82},"Escalations","\u002Fzh-tw\u002Finvestigate\u002Fescalations","zh-tw\u002F4.investigate\u002F4.escalations",{"title":84,"path":85,"stem":86},"Autofix","\u002Fzh-tw\u002Finvestigate\u002Fautofix","zh-tw\u002F4.investigate\u002F5.autofix",{"title":88,"path":89,"stem":90,"children":91,"icon":20},"在你的工具中工作","\u002Fzh-tw\u002Ftools","zh-tw\u002F5.tools\u002F1.index",[92,93,97,115],{"title":88,"path":89,"stem":90},{"title":94,"path":95,"stem":96},"平台MCP伺服器","\u002Fzh-tw\u002Ftools\u002Fplatform-mcp","zh-tw\u002F5.tools\u002F2.platform-mcp",{"title":98,"path":99,"stem":100,"children":101,"icon":20},"CLI","\u002Fzh-tw\u002Ftools\u002Fcli","zh-tw\u002F5.tools\u002F3.cli\u002F1.index",[102,103,107,111],{"title":98,"path":99,"stem":100},{"title":104,"path":105,"stem":106},"驗證","\u002Fzh-tw\u002Ftools\u002Fcli\u002Fauthentication","zh-tw\u002F5.tools\u002F3.cli\u002F2.authentication",{"title":108,"path":109,"stem":110},"指令碼","\u002Fzh-tw\u002Ftools\u002Fcli\u002Fscripting","zh-tw\u002F5.tools\u002F3.cli\u002F3.scripting",{"title":112,"path":113,"stem":114},"設定","\u002Fzh-tw\u002Ftools\u002Fcli\u002Fconfiguration","zh-tw\u002F5.tools\u002F3.cli\u002F4.configuration",{"title":116,"path":117,"stem":118},"Plugins","\u002Fzh-tw\u002Ftools\u002Fplugins","zh-tw\u002F5.tools\u002F5.plugins",{"title":120,"path":121,"stem":122,"children":123,"icon":20},"管理","\u002Fzh-tw\u002Fadministration","zh-tw\u002F6.administration\u002F1.index",[124,126,130,134,138],{"title":125,"path":121,"stem":122},"工作區",{"title":127,"path":128,"stem":129},"通知","\u002Fzh-tw\u002Fadministration\u002Fnotifications","zh-tw\u002F6.administration\u002F2.notifications",{"title":131,"path":132,"stem":133},"AI模型","\u002Fzh-tw\u002Fadministration\u002Fai-models","zh-tw\u002F6.administration\u002F3.ai-models",{"title":135,"path":136,"stem":137},"API金鑰與OAuth客戶端","\u002Fzh-tw\u002Fadministration\u002Fapi-keys-and-oauth","zh-tw\u002F6.administration\u002F4.api-keys-and-oauth",{"title":139,"path":140,"stem":141},"帳務與用量","\u002Fzh-tw\u002Fadministration\u002Fbilling-and-usage","zh-tw\u002F6.administration\u002F5.billing-and-usage",{"title":143,"icon":20,"path":144,"stem":145,"children":146,"page":20},"參考","\u002Fzh-tw\u002Freference","zh-tw\u002F7.reference",[147,151,155],{"title":148,"path":149,"stem":150},"文件MCP伺服器","\u002Fzh-tw\u002Freference\u002Fmcp","zh-tw\u002F7.reference\u002F1.mcp",{"title":152,"path":153,"stem":154},"llms.txt","\u002Fzh-tw\u002Freference\u002Fllms","zh-tw\u002F7.reference\u002F2.llms",{"title":156,"path":157,"stem":158},"API參考","\u002Fzh-tw\u002Freference\u002Fapi","zh-tw\u002F7.reference\u002F3.api",[160,244,318,369,424,486,497,548,595,646,695,729,740,751,1084,1334,1438,1520,1566,1628,1685,1791,1867,1918,1963,2001,2022,2056,2066,2076,2086,2096,2106,2116,2126,2136,2146,2156,2166,2176,2186,2196,2206,2216,2258,2268,2279,2289,2299,2308,2318,2329,2367,2377,2406,2437,2462,2488,2513,2523,2533],{"type":161,"category":162,"subcategory":163,"name":164,"description":165,"longDescription":166,"icon":167,"comingSoon":20,"lifecycle":168,"tools":176,"supportedResources":219,"marketing":220},"github","tool","git","GitHub","Connect GitHub for enhanced codebase context","Give agents access to your GitHub repositories for code search, pull request context, and codebase understanding. Agents can browse files, understand your architecture, and provide more accurate answers grounded in your actual code.","i-octicon-mark-github-16",{"connect":169,"browser":170,"headlessConnect":20,"teardown":171,"residue":172},"app-install",true,"partial",[173,174,175],"polylane\u002Fonboarding\u002F* branch and Set up Polylane PR","autofix branches and PRs","check runs on past commits",[177,180,183,186,189,192,195,198,201,204,207,210,213,216],{"name":178,"summary":179},"githubApi","Read any GitHub REST endpoint that lacks a dedicated tool",{"name":181,"summary":182},"githubFetchFiles","Fetch file contents from a GitHub repository",{"name":184,"summary":185},"githubSearchGithub","Search across GitHub repositories, code, issues, pull requests, users, commits, and topics",{"name":187,"summary":188},"githubCommits","Read commits in a GitHub repository (list\u002FgetDiff)",{"name":190,"summary":191},"githubPullRequests","Read pull requests in a GitHub repository (list\u002Fget)",{"name":193,"summary":194},"githubCreatePullRequest","Create or update a GitHub pull request",{"name":196,"summary":197},"githubMergePullRequest","Merge a pull request",{"name":199,"summary":200},"githubClosePullRequest","Close a pull request Polylane opened",{"name":202,"summary":203},"githubCreateIssue","Create or update a GitHub issue",{"name":205,"summary":206},"githubWorkflowRuns","Read GitHub Actions workflow runs (list\u002Fget)",{"name":208,"summary":209},"githubCreateBranch","Create a new branch in a repository",{"name":211,"summary":212},"githubGetPullRequestDiff","Get the diff for a pull request",{"name":214,"summary":215},"githubCreateReviewComment","Create or update a pull request review comment",{"name":217,"summary":218},"githubSubmitReview","Submit a review for a pull request",[],{"whatPolylaneDoes":221,"howItWorks":234},[222,225,228,231],{"title":223,"body":224},"Your code in the graph","Repositories are indexed for agents to grep and linked to the resources they deploy, so an investigation moves from a failing service to the code behind it without leaving the thread.",{"title":226,"body":227},"Changes become suspects","Pushes, merges, and deployments land on the timeline. When production breaks minutes after a merge, the investigation starts from that merge.",{"title":229,"body":230},"Watches on repo events","A thread can wait on pushes, pull requests, releases, and workflow runs, and pick the investigation back up when they land.",{"title":232,"body":233},"Fixes land where code lives","Investigations that end at a line of code end as a pull request on the repo behind the service, with the evidence trail attached. Your review and CI gate the merge.",[235,238,241],{"title":236,"body":237},"Install","Install the Polylane GitHub App on your organisation and pick the repositories it can see.",{"title":239,"body":240},"Index","Repositories are indexed and matched to the services they deploy, and repo events start landing on the timeline.",{"title":242,"body":243},"Agents work with the code","Mid-investigation they grep it, cite it, and when the root cause is a line of code, open the pull request.",{"type":245,"category":162,"subcategory":246,"name":247,"description":248,"longDescription":249,"icon":250,"comingSoon":20,"lifecycle":251,"tools":256,"supportedResources":293,"marketing":294},"datadog","observability","Datadog","Query metrics, logs, traces, and investigate alerts from Datadog","Connect your Datadog account to let agents query metrics, search logs, trace requests, and investigate alerts. Agents can correlate observability data with your infrastructure to diagnose issues faster.","i-vscode-icons-file-type-datadog",{"connect":252,"browser":20,"headlessConnect":170,"teardown":171,"residue":253},"api-key",[254,255],"@webhook-polylane appended to every monitor message","polylane:managed tag on every monitor",[257,260,263,266,269,272,275,278,281,284,287,290],{"name":258,"summary":259},"datadogApi","Call any Datadog REST endpoint that lacks a dedicated tool",{"name":261,"summary":262},"datadogQueryMetrics","Query time-series metrics from Datadog",{"name":264,"summary":265},"datadogSearchLogs","Search and filter log entries in Datadog",{"name":267,"summary":268},"datadogDashboards","Read or create Datadog dashboards",{"name":270,"summary":271},"datadogMonitors","Read, create, or mute Datadog monitors",{"name":273,"summary":274},"datadogIncidents","Read Datadog incidents",{"name":276,"summary":277},"datadogSLOs","Read or create Datadog Service Level Objectives (SLOs)",{"name":279,"summary":280},"datadogSpans","Query and aggregate Datadog APM spans and traces",{"name":282,"summary":283},"datadogListHosts","List hosts reporting to Datadog",{"name":285,"summary":286},"datadogListEvents","List events from Datadog",{"name":288,"summary":289},"datadogGetServiceDependencies","Get service dependency map from Datadog APM",{"name":291,"summary":292},"datadogCreateDowntime","Schedule a maintenance downtime in Datadog",[],{"whatPolylaneDoes":295,"howItWorks":308},[296,299,302,305],{"title":297,"body":298},"Alerts triaged on arrival","Every monitor that fires lands in Polylane as an issue, and an agent triages it the moment it does: real signal or noise, what it touches, and what changed right before.",{"title":300,"body":301},"Your dashboards become checks","Every query and chart your team saved in Datadog becomes a check: agents run it on a cadence and flag what doesn't look like normal. The curation you already did becomes detection.",{"title":303,"body":304},"Queried mid-investigation","Agents run Datadog metric, log, and trace queries while they work an incident, and every number is cited back to the query behind it.",{"title":306,"body":307},"First-class in the graph","Datadog joins the context graph as a source, so a spike lands next to the deploy, the config change, and the resources behind it.",[309,312,315],{"title":310,"body":311},"Connect","Pick your Datadog region and paste an API key and an application key. Credentials are encrypted before they're stored.",{"title":313,"body":314},"Sync","Monitors, dashboards, and saved queries join the context graph next to the services that emit the telemetry.",{"title":316,"body":317},"Agents take the watch","Alerts get triaged as they fire, your charts run as checks on a cadence, and investigations query Datadog directly.",{"type":319,"category":162,"subcategory":246,"name":320,"description":321,"longDescription":322,"icon":323,"comingSoon":20,"lifecycle":324,"tools":327,"supportedResources":349,"marketing":350},"honeycomb","Honeycomb","Query datasets, monitor triggers, and investigate incidents from Honeycomb","Connect your Honeycomb environment to let agents query datasets, check trigger statuses, and investigate production incidents. Agents use your observability data to understand system behavior and identify root causes.","HoneycombLogo",{"connect":252,"browser":20,"headlessConnect":170,"teardown":325,"residue":326},"complete",[],[328,331,334,337,340,343,346],{"name":329,"summary":330},"honeycombApi","Call any Honeycomb REST endpoint that lacks a dedicated tool",{"name":332,"summary":333},"honeycombRunQuery","Run a query against a Honeycomb dataset",{"name":335,"summary":336},"honeycombDatasets","Read Honeycomb datasets and their columns",{"name":338,"summary":339},"honeycombTriggers","Read or create Honeycomb triggers (alerts)",{"name":341,"summary":342},"honeycombBoards","Read or create Honeycomb boards (dashboards)",{"name":344,"summary":345},"honeycombSLOs","Read or create Honeycomb Service Level Objectives (SLOs)",{"name":347,"summary":348},"honeycombMarkers","List or create markers in a Honeycomb dataset",[],{"whatPolylaneDoes":351,"howItWorks":362},[352,355,358,360],{"title":353,"body":354},"Triggers triaged on arrival","Every Honeycomb trigger that fires lands in Polylane as an issue, and an agent triages it the moment it does, correlated with recent changes across the graph.",{"title":356,"body":357},"Your queries become checks","Every saved query and board becomes a check: agents run it on a cadence and flag what doesn't look like normal for the service behind it.",{"title":303,"body":359},"Agents query your datasets while they work an incident: high-cardinality questions, answered and cited in the thread.",{"title":306,"body":361},"Honeycomb joins the context graph as a source, so a regression in a dataset lands next to the deploy and the resources behind it.",[363,365,367],{"title":310,"body":364},"Pick your Honeycomb region and paste a configuration API key. Credentials are encrypted before they're stored.",{"title":313,"body":366},"Datasets, triggers, and boards join the context graph next to the services that emit the telemetry.",{"title":316,"body":368},"Triggers get triaged as they fire, saved queries run as checks, and investigations query Honeycomb directly.",{"type":370,"category":162,"subcategory":246,"name":371,"description":372,"longDescription":373,"icon":374,"comingSoon":20,"lifecycle":375,"tools":377,"supportedResources":405,"marketing":406},"axiom","Axiom","Run APL queries, monitor alerts, and explore datasets from Axiom","Connect your Axiom organization to let agents run APL queries, monitor alert statuses, and explore your datasets. Agents can analyze your telemetry data to help troubleshoot issues and understand system performance.","AxiomLogo",{"connect":252,"browser":20,"headlessConnect":170,"teardown":325,"residue":376},[],[378,381,384,387,390,393,396,399,402],{"name":379,"summary":380},"axiomApi","Call any Axiom REST endpoint that lacks a dedicated tool",{"name":382,"summary":383},"axiomQueries","Run an Axiom query (APL for logs\u002Ftraces\u002Fevents, MPL for metrics)",{"name":385,"summary":386},"axiomDatasets","Read Axiom datasets and their fields",{"name":388,"summary":389},"axiomDashboards","Read or create Axiom dashboards",{"name":391,"summary":392},"axiomMonitors","Read or create Axiom monitors",{"name":394,"summary":395},"axiomViews","Read or create Axiom saved views",{"name":397,"summary":398},"axiomAnnotations","List or create Axiom annotations",{"name":400,"summary":401},"axiomVirtualFields","List or create Axiom virtual fields",{"name":403,"summary":404},"axiomListNotifiers","List alert notifiers in Axiom",[],{"whatPolylaneDoes":407,"howItWorks":417},[408,410,413,415],{"title":297,"body":409},"Every Axiom monitor that fires lands in Polylane as an issue, and an agent triages it the moment it does, correlated with recent changes across the graph.",{"title":411,"body":412},"APL mid-investigation","Agents run APL queries against your datasets while they work an incident, and every result is cited back to the query behind it.",{"title":356,"body":414},"Every saved query and dashboard becomes a check: agents run it on a cadence and flag results that stray from the service's normal.",{"title":306,"body":416},"Axiom joins the context graph as a source, so a spike in a dataset lands next to the deploy and the resources behind it.",[418,420,422],{"title":310,"body":419},"Paste an Axiom API token. Credentials are encrypted before they're stored.",{"title":313,"body":421},"Datasets, monitors, and dashboards join the context graph next to the services that emit the telemetry.",{"title":316,"body":423},"Alerts get triaged as they fire, saved queries run as checks, and investigations query Axiom directly.",{"type":425,"category":162,"subcategory":246,"name":426,"description":427,"longDescription":428,"icon":429,"comingSoon":20,"lifecycle":430,"tools":434,"supportedResources":465,"marketing":466},"sentry","Sentry","Query errors, monitor alerts, and investigate incidents from Sentry","Connect your Sentry organization to let agents query issues, search error events, check alert statuses, and investigate production incidents. Agents can analyze your error data to help troubleshoot issues, understand error patterns, and identify root causes.","i-simple-icons-sentry",{"connect":431,"browser":170,"headlessConnect":20,"teardown":171,"residue":432},"oauth",[433],"Sentry app installation and tokens",[435,438,441,444,447,450,453,456,459,462],{"name":436,"summary":437},"sentryApi","Call any Sentry REST endpoint that lacks a dedicated tool",{"name":439,"summary":440},"sentryProjects","Read Sentry projects (list, get, stats)",{"name":442,"summary":443},"sentryIssues","Read or update Sentry issues, events, tags, and hashes",{"name":445,"summary":446},"sentryAlertRules","Read or create Sentry alerts (issue alert rules)",{"name":448,"summary":449},"sentryMetricAlerts","Read or create Sentry metric monitors (metric alert rules)",{"name":451,"summary":452},"sentryIncidents","Read Sentry metric alert firings",{"name":454,"summary":455},"sentryReplays","Read Sentry session replays",{"name":457,"summary":458},"sentryDashboards","Read, create, or edit Sentry dashboards",{"name":460,"summary":461},"sentryQueryDiscover","Run a Discover query in Sentry",{"name":463,"summary":464},"sentryQueryTimeseries","Run a Sentry events timeseries query",[],{"whatPolylaneDoes":467,"howItWorks":479},[468,471,473,476],{"title":469,"body":470},"Errors arrive with the exception attached","Sentry issues land in Polylane with the actual exception before triage starts: type, message, top stack frames, and tags.",{"title":297,"body":472},"Every Sentry alert lands as an issue and an agent triages it the moment it fires: real signal or noise, and what changed right before.",{"title":474,"body":475},"Error data mid-investigation","Agents search issues and events while they work an incident, correlating error patterns with deploys and the resources in the blast radius.",{"title":477,"body":478},"From stack trace to fix","When the investigation reaches a line of code, the fix arrives as a pull request on the repo behind the service, with the evidence trail attached.",[480,482,484],{"title":236,"body":481},"Install the Polylane integration on your Sentry organisation and approve it. No keys to create or paste.",{"title":313,"body":483},"Projects and alert rules join the context graph next to the services that raise the errors.",{"title":316,"body":485},"Alerts get triaged as they fire, and investigations pull the exceptions, events, and tags they need directly.",{"type":487,"category":162,"subcategory":246,"name":488,"description":489,"longDescription":490,"icon":491,"comingSoon":170,"lifecycle":492,"tools":495,"supportedResources":496},"honeybadger","Honeybadger","Track errors, monitor uptime, and investigate incidents from Honeybadger","Connect your Honeybadger project to let agents inspect errors, monitor uptime and cron checks, and investigate production incidents. Agents can correlate application failures with recent changes to identify root causes faster.","i-simple-icons-honeybadger",{"connect":493,"browser":20,"headlessConnect":20,"teardown":493,"residue":494},"none",[],[],[],{"type":498,"category":162,"subcategory":246,"name":499,"description":500,"longDescription":501,"icon":502,"comingSoon":20,"lifecycle":503,"tools":505,"supportedResources":527,"marketing":528},"betterstack","Better Stack","Monitor uptime, investigate incidents, and track telemetry from Better Stack","Connect your Better Stack account to let agents check uptime monitors, availability, and heartbeats, investigate incidents, and inspect telemetry sources. Incidents flow into Polylane as alerts for automated triage.","BetterstackLogo",{"connect":252,"browser":20,"headlessConnect":170,"teardown":325,"residue":504},[],[506,509,512,515,518,521,524],{"name":507,"summary":508},"betterstackApi","Call any Better Stack REST endpoint that lacks a dedicated tool",{"name":510,"summary":511},"betterstackMonitors","Read or create Better Stack uptime monitors",{"name":513,"summary":514},"betterstackIncidents","Read Better Stack incidents and their timelines, or acknowledge\u002Fresolve one",{"name":516,"summary":517},"betterstackHeartbeats","List Better Stack heartbeats (cron\u002Fjob check-ins)",{"name":519,"summary":520},"betterstackStatusPages","List Better Stack status pages",{"name":522,"summary":523},"betterstackStatusReports","Read and publish Better Stack status page reports (public incident communication)",{"name":525,"summary":526},"betterstackSources","List Better Stack telemetry sources",[],{"whatPolylaneDoes":529,"howItWorks":541},[530,533,536,539],{"title":531,"body":532},"Incidents triaged on arrival","Every Better Stack incident lands in Polylane as an alert, and an agent triages it the moment it does, correlated with recent changes across the graph.",{"title":534,"body":535},"Uptime mid-investigation","Agents check monitor status, availability, response times, and heartbeats while they work an incident, and every finding is cited back to the monitor behind it.",{"title":537,"body":538},"Availability becomes checks","Monitors, incident volume, and probe latency run as checks on a cadence; agents flag results that stray from the service's normal.",{"title":306,"body":540},"Better Stack joins the context graph as a source, so a failing monitor lands next to the deploy and the resources behind it.",[542,544,546],{"title":310,"body":543},"Paste your Better Stack API tokens. Credentials are encrypted before they're stored.",{"title":313,"body":545},"Monitors, heartbeats, and telemetry sources join the context graph next to the services they watch.",{"title":316,"body":547},"Incidents get triaged as they fire, availability runs as checks, and investigations query Better Stack directly.",{"type":549,"category":162,"subcategory":246,"name":550,"description":551,"longDescription":552,"icon":553,"comingSoon":20,"lifecycle":554,"tools":556,"supportedResources":575,"marketing":576},"openstatus","OpenStatus","Monitor uptime, manage status pages, and publish status reports from OpenStatus","Connect your OpenStatus workspace to let agents check uptime monitors and latency, manage status pages, and publish status reports to your subscribers. Monitor failures and recoveries flow into Polylane as alerts for automated triage.","OpenstatusLogo",{"connect":252,"browser":20,"headlessConnect":170,"teardown":325,"residue":555},[],[557,560,563,566,569,572],{"name":558,"summary":559},"openstatusApi","Call any OpenStatus API endpoint that lacks a dedicated tool",{"name":561,"summary":562},"openstatusMonitors","Read, create, update, or trigger OpenStatus uptime monitors",{"name":564,"summary":565},"openstatusResponseLogs","Read OpenStatus per-check HTTP response logs",{"name":567,"summary":568},"openstatusStatusPages","Read OpenStatus status pages, their components, and their public status",{"name":570,"summary":571},"openstatusStatusReports","Read and publish OpenStatus status reports (public incident communication)",{"name":573,"summary":574},"openstatusMaintenances","Read or schedule OpenStatus maintenance windows",[],{"whatPolylaneDoes":577,"howItWorks":588},[578,581,583,586],{"title":579,"body":580},"Failures triaged on arrival","Every OpenStatus monitor failure, degradation, and recovery lands in Polylane as an alert, and an agent triages it the moment it does, correlated with recent changes across the graph.",{"title":534,"body":582},"Agents check monitor status, uptime, latency percentiles, and per-check response logs while they work an incident, and every finding is cited back to the monitor behind it.",{"title":584,"body":585},"Status pages as incident comms","Agents publish status reports, post progress updates, and resolve them on your status page; notifying subscribers stays off unless you explicitly ask for it.",{"title":306,"body":587},"Monitors and status pages join the context graph as resources, so a failing monitor lands next to the deploy and the services behind it.",[589,591,593],{"title":310,"body":590},"Paste your OpenStatus API key. Credentials are encrypted before they're stored.",{"title":313,"body":592},"Monitors and status pages join the context graph next to the services they watch.",{"title":316,"body":594},"Failures get triaged as they fire, uptime runs as checks, and investigations query OpenStatus directly.",{"type":596,"category":162,"subcategory":246,"name":597,"description":598,"longDescription":599,"icon":600,"comingSoon":20,"lifecycle":601,"tools":603,"supportedResources":622,"marketing":623},"grafana","Grafana Cloud","Query dashboards, metrics, logs, and alerts from Grafana Cloud","Connect your Grafana Cloud stack to let agents query dashboards, explore Prometheus metrics, search Loki logs, and investigate alerts. Agents can correlate observability data across your stack to diagnose issues faster.","i-logos-grafana",{"connect":252,"browser":20,"headlessConnect":170,"teardown":325,"residue":602},[],[604,607,610,613,616,619],{"name":605,"summary":606},"grafanaApi","Call any Grafana HTTP API endpoint that lacks a dedicated tool",{"name":608,"summary":609},"grafanaDashboards","Search Grafana dashboards, read their panel definitions, and list folders",{"name":611,"summary":612},"grafanaDatasources","List Grafana datasources and check their health",{"name":614,"summary":615},"grafanaQuery","Run a datasource query (PromQL, LogQL, and more) through Grafana",{"name":617,"summary":618},"grafanaAlertRules","Read Grafana alert rules, their live state, and firing alerts",{"name":620,"summary":621},"grafanaAnnotations","Read or create Grafana annotations to mark events on charts",[],{"whatPolylaneDoes":624,"howItWorks":637},[625,628,631,634],{"title":626,"body":627},"Alerting state at a glance","Agents check which Grafana-managed alerts are firing and which rules sit in error or NoData, so a silently broken rule surfaces before it hides a real incident.",{"title":629,"body":630},"Your datasources mid-investigation","Agents run PromQL, LogQL, and TraceQL through Grafana's query proxy against the same datasources your dashboards use, and every finding is cited back to the query behind it.",{"title":632,"body":633},"Dashboards as institutional knowledge","Agents read the panels your team already trusts, reuse their queries, and interpret what the numbers mean for the incident at hand.",{"title":635,"body":636},"Context left on the charts","Agents annotate deploys, incident windows, and fixes onto your Grafana charts, so the next person looking at a spike sees what happened.",[638,640,643],{"title":310,"body":639},"Paste your stack URL and a service account token. Credentials are encrypted before they're stored.",{"title":641,"body":642},"Checks take the watch","Firing alerts and unhealthy rules run as checks on a cadence; agents flag results that stray from normal.",{"title":644,"body":645},"Agents investigate","Investigations query your datasources through Grafana, read your dashboards, and annotate what they find.",{"type":647,"category":162,"subcategory":246,"name":648,"description":649,"longDescription":650,"icon":651,"comingSoon":20,"lifecycle":652,"tools":654,"supportedResources":670,"marketing":671},"logfire","Logfire","Query traces, metrics, and logs from Pydantic Logfire","Connect your Pydantic Logfire project to let agents query traces, explore metrics, and search structured logs, and to have its alerts reach Polylane the moment they fire. Agents can analyze your OpenTelemetry data to troubleshoot issues and understand application behavior.","LogfireLogo",{"connect":252,"browser":20,"headlessConnect":170,"teardown":325,"residue":653},[],[655,658,661,664,667],{"name":656,"summary":657},"logfireListServices","List the services that sent spans or logs to Logfire in a time window",{"name":659,"summary":660},"logfireSearchSpans","Search Logfire spans and logs by service, name, route, level, exception, or HTTP status",{"name":662,"summary":663},"logfireGetTrace","Read one Logfire trace as a parent\u002Fchild span tree with durations",{"name":665,"summary":666},"logfireRouteSummary","Per-route request counts, error rates, and p50\u002Fp95 latency from Logfire",{"name":668,"summary":669},"logfireQuery","Run a read-only SQL query against a Logfire project's records and metrics tables",[],{"whatPolylaneDoes":672,"howItWorks":685},[673,676,679,682],{"title":674,"body":675},"Route health in one question","Agents rank your routes by request count, error rate, and p95 latency straight from the spans your services already send to Logfire, so \"what is failing\" gets a numbered answer.",{"title":677,"body":678},"From an error rate to the failing span","Agents pull the requests behind a bad route and open one trace as a parent\u002Fchild tree, naming the child span that threw and what its exception said.",{"title":680,"body":681},"Your traces mid-investigation","Agents search spans and logs by service, route, level, and status while they work an incident, and every finding is cited back to the query behind it.",{"title":683,"body":684},"SQL when the question is unusual","For anything the curated tools do not cover, agents run bounded read-only SQL over your Logfire records and metrics, with the engine's own error messages guiding the next attempt.",[686,688,690,693],{"title":310,"body":687},"Paste a project API key and an organization API key, each created with Read-only access and Manage project and org. Credentials are encrypted before they're stored, and agents only ever query with the project key.",{"title":641,"body":689},"Request error rate, volume, and p95 latency run as checks on a cadence, project-wide and per service; agents flag results that stray from normal.",{"title":691,"body":692},"Agents map your services","Every thread can discover which services report to the project and how each route is behaving right now.",{"title":644,"body":694},"Investigations move from route summaries to individual spans to full trace trees, inside a bounded time window.",{"type":696,"category":162,"subcategory":697,"name":698,"description":699,"longDescription":700,"icon":701,"comingSoon":20,"lifecycle":702,"tools":707,"supportedResources":708,"marketing":709},"slack","communication","Slack","Work with Polylane directly in Slack","Install Polylane in your Slack workspace. Mention @Polylane in any channel or DM to chat with the agent, receive automation summaries, triage alerts, and collaborate with your team through the same agent you use in the console.","i-logos-slack-icon",{"connect":431,"browser":170,"headlessConnect":20,"teardown":171,"residue":703},[704,705,706],"Slack app installation (its bot token is revoked)","#polylane-notifications and #*-polylane channels","bot channel memberships and DMs",[],[],{"whatPolylaneDoes":710,"howItWorks":720},[711,714,717],{"title":712,"body":713},"The agent in your channels","Mention Polylane in any channel or DM to ask about production, and spin an investigation off any message.",{"title":715,"body":716},"Notifications where the team lives","Issues, autofix results, and digests land in the channels you choose, with links back to the full thread and its evidence.",{"title":718,"body":719},"Incidents worked in the open","Investigation updates post as they happen, so the channel follows the same transcript the console shows.",[721,723,726],{"title":236,"body":722},"Add Polylane to your Slack workspace from the console. One approval, no keys to manage.",{"title":724,"body":725},"Choose channels","Pick where issues, autofix results, and digests should land.",{"title":727,"body":728},"Work with it","Mention the agent to ask questions or start investigations without leaving Slack.",{"type":730,"category":162,"subcategory":731,"name":732,"description":733,"longDescription":734,"icon":735,"comingSoon":170,"lifecycle":736,"tools":738,"supportedResources":739},"jira","issue-tracking","Jira","Create and manage Jira issues from Polylane","Connect Jira to let agents create issues, update tickets, and track project progress. Agents can automatically file bugs from investigations and keep your project management tools in sync with your infrastructure.","i-logos-jira",{"connect":493,"browser":20,"headlessConnect":20,"teardown":493,"residue":737},[],[],[],{"type":741,"category":162,"subcategory":742,"name":743,"description":744,"longDescription":745,"icon":746,"comingSoon":170,"lifecycle":747,"tools":749,"supportedResources":750},"pagerduty","incident-management","PagerDuty","Manage incidents and on-call from Polylane","Connect PagerDuty to let agents manage incidents, check on-call schedules, and escalate issues. Agents can correlate infrastructure problems with active incidents to speed up resolution.","i-logos-pagerduty-icon",{"connect":493,"browser":20,"headlessConnect":20,"teardown":493,"residue":748},[],[],[],{"type":752,"category":753,"subcategory":753,"name":754,"description":755,"longDescription":756,"icon":757,"comingSoon":20,"lifecycle":758,"tools":765,"supportedResources":799,"marketing":1062},"aws","cloud","AWS","EC2, Lambda, ECS, RDS, S3, and more","Connect your AWS account to give agents full visibility into your infrastructure. Agents can discover resources, monitor CloudWatch metrics, analyze costs, and help you understand your architecture across EC2, Lambda, ECS, RDS, and more.","i-skill-icons:aws-dark",{"connect":759,"browser":170,"headlessConnect":20,"teardown":171,"residue":760},"cloudformation",[761,762,763,764],"PolylaneEnvironmentRole (DeletionPolicy Retain)","PolylaneEnvironmentPolicies (Retain)","PolylaneS3Bucket (Retain)","EKS access entries",[766,769,772,775,778,781,784,787,790,793,796],{"name":767,"summary":768},"awsApi","Read any AWS API via a SigV4-signed request (read-only escape hatch)",{"name":770,"summary":771},"awsCloudWatchAlarms","Read or manage CloudWatch alarms (list, get, getHistory, create, acknowledge, enableActions)",{"name":773,"summary":774},"awsCloudWatchDashboards","Read or manage CloudWatch dashboards (list, get, create)",{"name":776,"summary":777},"awsCloudWatchLogs","Read CloudWatch logs (listGroups, describeStreams, getEvents, filter, query)",{"name":779,"summary":780},"awsGetCloudWatchQueryResults","Get results of a CloudWatch Insights query",{"name":782,"summary":783},"awsCloudWatchMetrics","Read CloudWatch metrics (list available metrics, get data points)",{"name":785,"summary":786},"awsXRayTraces","Read X-Ray traces (list summaries, get full trace)",{"name":788,"summary":789},"awsXRayInsights","Read X-Ray insights (list, get, getEvents)",{"name":791,"summary":792},"awsXRayServices","Read X-Ray service topology and time-series statistics (graph, timeseries)",{"name":794,"summary":795},"awsGetXRayGroups","List X-Ray groups",{"name":797,"summary":798},"awsEksKubectl","Read and operate on Kubernetes resources on an EKS cluster (get\u002Flist\u002Fdescribe\u002Flogs\u002Fevents\u002Ftop\u002Frollout, plus scale, restart, patch, delete, apply)",[800,804,807,811,815,818,821,824,827,830,833,836,839,843,847,851,855,859,862,865,869,873,877,880,883,887,891,894,898,902,906,909,912,915,919,923,927,930,934,938,942,946,950,953,957,961,964,967,971,974,978,982,986,989,993,996,1000,1004,1008,1011,1014,1017,1020,1023,1026,1030,1033,1036,1040,1044,1047,1050,1053,1056,1059],{"type":801,"name":802,"icon":803},"aws.lambda.function","Lambda Function","AwsLambdaLogo",{"type":805,"name":806,"icon":803},"aws.lambda.layer","Lambda Layer",{"type":808,"name":809,"icon":810},"aws.ec2.instance","EC2 Instance","AwsEc2Logo",{"type":812,"name":813,"icon":814},"aws.ec2.vpc","VPC","AwsVpcLogo",{"type":816,"name":817,"icon":814},"aws.ec2.subnet","Subnet",{"type":819,"name":820,"icon":814},"aws.ec2.security_group","Security Group",{"type":822,"name":823,"icon":814},"aws.ec2.internet_gateway","Internet Gateway",{"type":825,"name":826,"icon":814},"aws.ec2.nat_gateway","NAT Gateway",{"type":828,"name":829,"icon":814},"aws.ec2.route_table","Route Table",{"type":831,"name":832,"icon":814},"aws.ec2.network_acl","Network ACL",{"type":834,"name":835,"icon":810},"aws.ec2.volume","EBS Volume",{"type":837,"name":838,"icon":814},"aws.ec2.eip","Elastic IP",{"type":840,"name":841,"icon":842},"aws.s3.bucket","S3 Bucket","AwsS3Logo",{"type":844,"name":845,"icon":846},"aws.dynamodb.table","DynamoDB Table","AwsDynamodbLogo",{"type":848,"name":849,"icon":850},"aws.rds.instance","RDS Instance","AwsAuroraLogo",{"type":852,"name":853,"icon":854},"aws.cloudfront.distribution","CloudFront Distribution","AwsCloudfrontLogo",{"type":856,"name":857,"icon":858},"aws.apigateway.restapi","API Gateway REST API","AwsApigatewayLogo",{"type":860,"name":861,"icon":858},"aws.apigatewayv2.api","API Gateway v2 API",{"type":863,"name":864,"icon":858},"aws.apigateway.domain","API Gateway Custom Domain",{"type":866,"name":867,"icon":868},"aws.sqs.queue","SQS Queue","AwsSqsLogo",{"type":870,"name":871,"icon":872},"aws.sns.topic","SNS Topic","AwsSnsLogo",{"type":874,"name":875,"icon":876},"aws.ecs.cluster","ECS Cluster","AwsEcsLogo",{"type":878,"name":879,"icon":876},"aws.ecs.service","ECS Service",{"type":881,"name":882,"icon":876},"aws.ecs.task_definition","ECS Task Definition",{"type":884,"name":885,"icon":886},"aws.elasticache.cluster","ElastiCache Cluster","AwsElasticacheLogo",{"type":888,"name":889,"icon":890},"aws.apprunner.service","App Runner Service","AwsApprunnerLogo",{"type":892,"name":893,"icon":890},"aws.apprunner.connection","App Runner Connection",{"type":895,"name":896,"icon":897},"aws.iam.role","IAM Role","AwsIamLogo",{"type":899,"name":900,"icon":901},"aws.kms.key","KMS Key","AwsKmsLogo",{"type":903,"name":904,"icon":905},"aws.kinesis.stream","Kinesis Stream","AwsKinesisLogo",{"type":907,"name":908,"icon":886},"aws.elasticache.replication_group","ElastiCache Replication Group",{"type":910,"name":911,"icon":850},"aws.rds.cluster","RDS Cluster",{"type":913,"name":914,"icon":850},"aws.rds.proxy","RDS Proxy",{"type":916,"name":917,"icon":918},"aws.servicediscovery.service","Service Discovery Service","AwsLogo",{"type":920,"name":921,"icon":922},"aws.secretsmanager.secret","Secrets Manager Secret","AwsSecretsManagerLogo",{"type":924,"name":925,"icon":926},"aws.eventbridge.rule","EventBridge Rule","AwsEventbridgeLogo",{"type":928,"name":929,"icon":926},"aws.eventbridge.bus","EventBridge Bus",{"type":931,"name":932,"icon":933},"aws.states.state_machine","Step Functions State Machine","AwsStepfunctionsLogo",{"type":935,"name":936,"icon":937},"aws.redshift.cluster","Redshift Cluster","AwsRedshiftLogo",{"type":939,"name":940,"icon":941},"aws.kinesis.firehose","Kinesis Firehose","AwsFirehoseLogo",{"type":943,"name":944,"icon":945},"aws.neptune.cluster","Neptune Cluster","AwsNeptuneLogo",{"type":947,"name":948,"icon":949},"aws.cognito.user_pool","Cognito User Pool","AwsCognitoLogo",{"type":951,"name":952,"icon":949},"aws.cognito.identity_pool","Cognito Identity Pool",{"type":954,"name":955,"icon":956},"aws.athena.workgroup","Athena Workgroup","AwsAthenaLogo",{"type":958,"name":959,"icon":960},"aws.glue.database","Glue Database","AwsGlueLogo",{"type":962,"name":963,"icon":960},"aws.glue.crawler","Glue Crawler",{"type":965,"name":966,"icon":960},"aws.glue.job","Glue Job",{"type":968,"name":969,"icon":970},"aws.batch.job_queue","Batch Job Queue","AwsBatchLogo",{"type":972,"name":973,"icon":970},"aws.batch.compute_environment","Batch Compute Environment",{"type":975,"name":976,"icon":977},"aws.mq.broker","Amazon MQ Broker","AwsMqLogo",{"type":979,"name":980,"icon":981},"aws.msk.cluster","MSK Cluster","AwsMskLogo",{"type":983,"name":984,"icon":985},"aws.documentdb.cluster","DocumentDB Cluster","AwsDocumentdbLogo",{"type":987,"name":988,"icon":886},"aws.memorydb.cluster","MemoryDB Cluster",{"type":990,"name":991,"icon":992},"aws.cloudtrail.trail","CloudTrail Trail","AwsCloudtrailLogo",{"type":994,"name":995,"icon":918},"aws.guardduty.detector","GuardDuty Detector",{"type":997,"name":998,"icon":999},"aws.waf.web_acl","WAF Web ACL","AwsWafLogo",{"type":1001,"name":1002,"icon":1003},"aws.acm.certificate","ACM Certificate","AwsCertificateManagerLogo",{"type":1005,"name":1006,"icon":1007},"aws.eks.cluster","EKS Cluster","KubernetesLogo",{"type":1009,"name":1010,"icon":1007},"aws.eks.nodegroup","EKS Node Group",{"type":1012,"name":1013,"icon":1007},"aws.eks.fargate_profile","EKS Fargate Profile",{"type":1015,"name":1016,"icon":1007},"aws.eks.addon","EKS Addon",{"type":1018,"name":1019,"icon":1007},"aws.eks.access_entry","EKS Access Entry",{"type":1021,"name":1022,"icon":1007},"aws.eks.identity_provider_config","EKS Identity Provider",{"type":1024,"name":1025,"icon":1007},"aws.eks.oidc_provider","EKS OIDC Provider",{"type":1027,"name":1028,"icon":1029},"aws.elasticsearch.domain","Elasticsearch Domain","AwsOpenSearchLogo",{"type":1031,"name":1032,"icon":1029},"aws.opensearch.domain","OpenSearch Domain",{"type":1034,"name":1035,"icon":926},"aws.eventbridge.pipe","EventBridge Pipe",{"type":1037,"name":1038,"icon":1039},"aws.amplify.app","Amplify App","AwsAmplifyLogo",{"type":1041,"name":1042,"icon":1043},"aws.elbv2.alb","Application Load Balancer","AwsElbLogo",{"type":1045,"name":1046,"icon":1043},"aws.elbv2.nlb","Network Load Balancer",{"type":1048,"name":1049,"icon":1043},"aws.elbv2.gwlb","Gateway Load Balancer",{"type":1051,"name":1052,"icon":1043},"aws.elbv2.target_group","Target Group",{"type":1054,"name":1055,"icon":1043},"aws.elbv2.listener","Load Balancer Listener",{"type":1057,"name":1058,"icon":1043},"aws.elbv2.listener_rule","Listener Rule",{"type":1060,"name":1061,"icon":960},"aws.glue.table","Glue Table",{"whatPolylaneDoes":1063,"howItWorks":1076},[1064,1067,1070,1073],{"title":1065,"body":1066},"74 resource types in one graph","Lambda, ECS, RDS, DynamoDB, SQS, EventBridge, EKS, VPCs and everything wired into them, with their edges, config, and history.",{"title":1068,"body":1069},"CloudWatch read for you","Agents comb metrics, logs, and X-Ray traces on a cadence and judge them against how each resource normally behaves. No thresholds to tune.",{"title":1071,"body":1072},"Alarms that investigate themselves","Point your CloudWatch Alarms at Polylane and an agent picks each one up as it fires, so the alarm arrives with an explanation attached.",{"title":1074,"body":1075},"Change intelligence","Each sync records what appeared, changed, or disappeared across the account. When something breaks minutes after a change, the investigation starts there.",[1077,1080,1082],{"title":1078,"body":1079},"One CloudFormation stack","Review the open template and create the stack. The cross-account role can read resources and manage alarms and tags so your account can be monitored.",{"title":313,"body":1081},"Your resources land in the graph within minutes, with edges, config, and history.",{"title":316,"body":1083},"Telemetry is combed on a cadence, alarms get investigated as they fire, and code fixes arrive as pull requests for your review.",{"type":1085,"category":753,"subcategory":753,"name":1086,"description":1087,"longDescription":1088,"icon":1089,"comingSoon":20,"lifecycle":1090,"tools":1092,"supportedResources":1135,"marketing":1313},"cloudflare","Cloudflare","Workers, Pages, R2, D1, and edge network","Connect your Cloudflare account to let agents monitor your Workers, Pages, and edge infrastructure. Agents can analyze request patterns, check worker performance, and help troubleshoot issues at the edge.","i-logos-cloudflare-icon",{"connect":252,"browser":20,"headlessConnect":170,"teardown":325,"residue":1091},[],[1093,1096,1099,1102,1105,1108,1111,1114,1117,1120,1123,1126,1129,1132],{"name":1094,"summary":1095},"cloudflareListTelemetryKeys","List available Cloudflare telemetry data keys",{"name":1097,"summary":1098},"cloudflareListTelemetryValues","List values for a Cloudflare telemetry key",{"name":1100,"summary":1101},"cloudflareRunTelemetryQuery","Query Cloudflare Workers \u002F container logs, traces, and AI Gateway request logs",{"name":1103,"summary":1104},"cloudflareTraces","Read Cloudflare traces (list summaries, get full span tree)",{"name":1106,"summary":1107},"cloudflareRunGraphqlQuery","Execute a GraphQL query against the Cloudflare Analytics API",{"name":1109,"summary":1110},"cloudflareGraphqlSchemaSearch","Search the Cloudflare GraphQL schema for matching types, fields, args, and enum values",{"name":1112,"summary":1113},"cloudflareGraphqlSchemaOverview","Fetch a paginated overview of all Cloudflare GraphQL types",{"name":1115,"summary":1116},"cloudflareGraphqlTypeDetails","Fetch fields, args, and enum values for one Cloudflare GraphQL type",{"name":1118,"summary":1119},"cloudflareGraphqlCompleteSchema","Fetch the Cloudflare GraphQL schema with optional root-type details",{"name":1121,"summary":1122},"cloudflareAiGatewayLogs","List Cloudflare AI Gateway logs, or fetch one log's full detail",{"name":1124,"summary":1125},"cloudflareAccessApplicationLogs","List Cloudflare Access authentication events for an Access application",{"name":1127,"summary":1128},"cloudflareWorkflowInstances","List or get Cloudflare Workflows instances",{"name":1130,"summary":1131},"cloudflareApi","Call any Cloudflare REST API endpoint that lacks a dedicated tool",{"name":1133,"summary":1134},"cloudflareDeployments","List Cloudflare Worker\u002FPages deployments or Worker versions",[1136,1140,1144,1148,1152,1156,1160,1164,1168,1171,1174,1178,1182,1186,1190,1193,1197,1200,1204,1208,1212,1216,1220,1223,1226,1229,1233,1236,1240,1244,1248,1252,1256,1260,1264,1268,1272,1275,1278,1282,1285,1289,1293,1297,1301,1305,1309],{"type":1137,"name":1138,"icon":1139},"cf.workers.script","Cloudflare Worker","CloudflareWorkersLogo",{"type":1141,"name":1142,"icon":1143},"cf.ai_gateway.gateway","AI Gateway","CloudflareAiGatewayLogo",{"type":1145,"name":1146,"icon":1147},"cf.containers.application","Cloudflare Container","CloudflareContainerLogo",{"type":1149,"name":1150,"icon":1151},"cf.do.namespace","Durable Object","CloudflareDurableObjectsLogo",{"type":1153,"name":1154,"icon":1155},"cf.d1.database","D1 Database","CloudflareD1Logo",{"type":1157,"name":1158,"icon":1159},"cf.hyperdrive.config","Hyperdrive","CloudflareHyperdriveLogo",{"type":1161,"name":1162,"icon":1163},"cf.kv.namespace","Cloudflare KV","CloudflareKvLogo",{"type":1165,"name":1166,"icon":1167},"cf.pipelines.pipeline","Cloudflare Pipeline","CloudflarePipelinesLogo",{"type":1169,"name":1170,"icon":1167},"cf.pipelines.stream","Pipeline Stream",{"type":1172,"name":1173,"icon":1167},"cf.pipelines.sink","Pipeline Sink",{"type":1175,"name":1176,"icon":1177},"cf.r2.bucket","R2 Bucket","CloudflareR2Logo",{"type":1179,"name":1180,"icon":1181},"cf.r2.custom_domain","R2 Domain","CloudflareDnsLogo",{"type":1183,"name":1184,"icon":1185},"cf.queues.queue","Cloudflare Queue","CloudflareQueuesLogo",{"type":1187,"name":1188,"icon":1189},"cf.secrets.store","Secret Store","CloudflareSecretStoreLogo",{"type":1191,"name":1192,"icon":1189},"cf.secrets.secret","Cloudflare Secret",{"type":1194,"name":1195,"icon":1196},"cf.pages.project","Cloudflare Pages","CloudflarePagesLogo",{"type":1198,"name":1199,"icon":1181},"cf.pages.domain","Domain",{"type":1201,"name":1202,"icon":1203},"cf.ai.ai","AI","CloudflareAiLogo",{"type":1205,"name":1206,"icon":1207},"cf.analytics_engine.dataset","Analytics Engine","CloudflareAnalyticsEngineLogo",{"type":1209,"name":1210,"icon":1211},"cf.browsers.browser","Browser Rendering","CloudflareBrowserRenderingLogo",{"type":1213,"name":1214,"icon":1215},"cf.vectorize.index","Vectorize","CloudflareVectorizeLogo",{"type":1217,"name":1218,"icon":1219},"cf.workflows.workflow","Cloudflare Workflow","CloudflareWorkflowsLogo",{"type":1221,"name":1222,"icon":1181},"cf.zone","Cloudflare Zone",{"type":1224,"name":1225,"icon":1139},"cf.workers.route","Worker Route",{"type":1227,"name":1228,"icon":1181},"cf.workers.custom_domain","Worker Domain",{"type":1230,"name":1231,"icon":1232},"cf.workers.dispatch_namespace","Dispatch Namespace","CloudflareForPlatformsLogo",{"type":1234,"name":1235,"icon":1232},"cf.workers.tenant_script","Tenant Worker",{"type":1237,"name":1238,"icon":1239},"cf.snippet","Snippet","i-lucide-scissors",{"type":1241,"name":1242,"icon":1243},"cf.mtls_certificate","mTLS Certificate","CloudflareSslLogo",{"type":1245,"name":1246,"icon":1247},"cf.tunnel","Cloudflare Tunnel","CloudflareTunnelLogo",{"type":1249,"name":1250,"icon":1251},"cf.access.application","Access Application","CloudflareAccessLogo",{"type":1253,"name":1254,"icon":1255},"cf.spectrum.app","Spectrum App","CloudflareSpectrumLogo",{"type":1257,"name":1258,"icon":1259},"cf.turnstile.widget","Turnstile Widget","CloudflareTurnstileLogo",{"type":1261,"name":1262,"icon":1263},"cf.waiting_room","Waiting Room","CloudflareWaitingRoomLogo",{"type":1265,"name":1266,"icon":1267},"cf.healthcheck","Health Check","CloudflareHealthChecksLogo",{"type":1269,"name":1270,"icon":1271},"cf.load_balancing.load_balancer","Load Balancer","CloudflareLoadBalancingLogo",{"type":1273,"name":1274,"icon":1271},"cf.load_balancing.pool","Load Balancer Pool",{"type":1276,"name":1277,"icon":1271},"cf.load_balancing.monitor","Load Balancer Monitor",{"type":1279,"name":1280,"icon":1281},"cf.logpush.job","Logpush Job","CloudflareLogsLogo",{"type":1283,"name":1284,"icon":1243},"cf.ssl.certificate_pack","SSL Certificate",{"type":1286,"name":1287,"icon":1288},"cf.email_routing.address","Email Address","CloudflareEmailRoutingLogo",{"type":1290,"name":1291,"icon":1292},"cf.stream.live_input","Stream Live Input","CloudflareStreamLogo",{"type":1294,"name":1295,"icon":1296},"cf.images.images","Cloudflare Images","CloudflareImagesLogo",{"type":1298,"name":1299,"icon":1300},"cf.calls.app","Calls App","CloudflareCallsLogo",{"type":1302,"name":1303,"icon":1304},"cf.autorag.rag","AutoRAG","CloudflareAutoragLogo",{"type":1306,"name":1307,"icon":1308},"cf.r2.data_catalog","R2 Data Catalog","CloudflareR2DataCatalogLogo",{"type":1310,"name":1311,"icon":1312},"cf.artifacts.namespace","Artifacts Namespace","CloudflareArtifactsLogo",{"whatPolylaneDoes":1314,"howItWorks":1327},[1315,1318,1321,1324],{"title":1316,"body":1317},"The whole account in one graph","Workers, Durable Objects, D1, R2, KV, Queues, Workflows, zones, and DNS land in one graph with their bindings, config, and history.",{"title":1319,"body":1320},"Analytics read on a cadence","Requests, errors, CPU time, and Durable Object compute, judged against how each resource normally behaves. No thresholds to tune.",{"title":1322,"body":1323},"Rollbacks where you allow them","Off by default. Enabled, agents restore the last known-good Worker version on their own, rate-limited and on the record, and the permanent fix follows.",{"title":1325,"body":1326},"Advisories on every resource","Workers without observability, D1 databases without backups, queues stuck retrying: each one marked fixable in place or with guidance.",[1328,1330,1332],{"title":310,"body":1329},"A guided flow pre-fills the exact API token permissions Polylane needs. You choose read-only or full access when you create it.",{"title":313,"body":1331},"The account lands in the graph with its bindings and history, and every sync after records what changed.",{"title":316,"body":1333},"Analytics are read on a cadence, issues get investigated as they surface, and any write waits for your approval.",{"type":1335,"category":753,"subcategory":753,"name":1336,"description":1337,"longDescription":1338,"icon":1339,"comingSoon":20,"lifecycle":1340,"tools":1344,"supportedResources":1354,"marketing":1416},"vercel","Vercel","Deployments, serverless functions, and edge config","Connect your Vercel account to give agents visibility into your deployments, serverless functions, and edge network. Agents can monitor build performance, analyze traffic patterns, and troubleshoot deployment issues.","VercelLogo",{"connect":431,"browser":170,"headlessConnect":20,"teardown":493,"residue":1341},[1342,1343],"Vercel integration configuration","polylane-* log, analytics and speed-insights drains",[1345,1348,1351],{"name":1346,"summary":1347},"vercelApi","Call any Vercel REST API endpoint that lacks a dedicated tool",{"name":1349,"summary":1350},"vercelGetLogs","Get logs from a Vercel deployment",{"name":1352,"summary":1353},"vercelQueryMetrics","Query Vercel observability metrics (requests, errors, function duration)",[1355,1358,1361,1363,1366,1369,1372,1375,1378,1381,1384,1387,1390,1393,1396,1399,1402,1404,1407,1410,1413],{"type":1356,"name":1357,"icon":1339},"vercel.project","Project",{"type":1359,"name":1360,"icon":1339},"vercel.deployment","Deployment",{"type":1362,"name":1199,"icon":1339},"vercel.domain",{"type":1364,"name":1365,"icon":1339},"vercel.edge_config","Edge Config",{"type":1367,"name":1368,"icon":1339},"vercel.postgres","Postgres",{"type":1370,"name":1371,"icon":1339},"vercel.kv","KV Store",{"type":1373,"name":1374,"icon":1339},"vercel.blob","Blob Store",{"type":1376,"name":1377,"icon":1339},"vercel.log_drain","Log Drain",{"type":1379,"name":1380,"icon":1339},"vercel.custom_environment","Custom Environment",{"type":1382,"name":1383,"icon":1339},"vercel.firewall_config","Firewall",{"type":1385,"name":1386,"icon":1339},"vercel.webhook","Webhook",{"type":1388,"name":1389,"icon":1339},"vercel.integration_config","Integration",{"type":1391,"name":1392,"icon":1339},"vercel.sandbox","Sandbox",{"type":1394,"name":1395,"icon":1339},"vercel.workflow","Workflow",{"type":1397,"name":1398,"icon":1339},"vercel.cron_job","Cron Job",{"type":1400,"name":1401,"icon":1339},"vercel.flag","Feature Flag",{"type":1403,"name":1142,"icon":1339},"vercel.ai_gateway",{"type":1405,"name":1406,"icon":1339},"vercel.microfrontends_group","Microfrontends Group",{"type":1408,"name":1409,"icon":1339},"vercel.access_group","Access Group",{"type":1411,"name":1412,"icon":1339},"vercel.drain","Drain",{"type":1414,"name":1415,"icon":1339},"vercel.container_repository","Container Repository",{"whatPolylaneDoes":1417,"howItWorks":1429},[1418,1421,1424,1426],{"title":1419,"body":1420},"Every deploy, watched","Webhooks keep the graph current the moment you ship, and an agent triages every deployment failure and alert as it lands.",{"title":1422,"body":1423},"Everything you ship, in one graph","Projects, deployments, domains, Edge Config, Postgres, KV, and Blob, with the DNS records on other providers that point at them.",{"title":1322,"body":1425},"Off by default. Enabled, agents restore the last known-good deployment on their own, rate-limited and on the record, and the permanent fix follows.",{"title":1427,"body":1428},"Misconfigurations surfaced early","Domains pointed at the wrong project, certificates about to expire, environments drifting apart: every resource carries its advisories.",[1430,1433,1436],{"title":1431,"body":1432},"Install from the Marketplace","Vercel's OAuth flow, so there are no API keys to create or rotate. Pick the team and the projects Polylane can see.",{"title":1434,"body":1435},"Webhooks keep it current","What deployed, which domain moved, what config changed: the graph knows the moment it happens.",{"title":316,"body":1437},"Failures get triaged on arrival, regressions are judged against each project's normal, and fixes arrive for your review.",{"type":1439,"category":753,"subcategory":753,"name":1440,"description":1441,"longDescription":1442,"icon":1443,"comingSoon":20,"lifecycle":1444,"tools":1446,"supportedResources":1462,"marketing":1499},"render","Render","Web services, databases, and cron jobs","Connect your Render account to give agents visibility into your web services, databases, and cron jobs. Agents can monitor deployments, check service health, and help troubleshoot performance issues.","RenderLogo",{"connect":252,"browser":20,"headlessConnect":170,"teardown":325,"residue":1445},[],[1447,1450,1453,1456,1459],{"name":1448,"summary":1449},"renderApi","Call any Render REST API endpoint that lacks a dedicated tool",{"name":1451,"summary":1452},"renderGetLogs","Get logs for a Render service",{"name":1454,"summary":1455},"renderDeploys","List a Render service's deploys, or get one deploy's full detail",{"name":1457,"summary":1458},"renderGetServiceEvents","Get audit events for a Render service",{"name":1460,"summary":1461},"renderGetMetrics","Get metrics for a Render service",[1463,1465,1468,1471,1474,1477,1480,1482,1484,1487,1490,1493,1496],{"type":1464,"name":1357,"icon":1443},"render.project",{"type":1466,"name":1467,"icon":1443},"render.environment","Environment",{"type":1469,"name":1470,"icon":1443},"render.service.web_service","Web Service",{"type":1472,"name":1473,"icon":1443},"render.service.static_site","Static Site",{"type":1475,"name":1476,"icon":1443},"render.service.private_service","Private Service",{"type":1478,"name":1479,"icon":1443},"render.service.background_worker","Background Worker",{"type":1481,"name":1398,"icon":1443},"render.service.cron_job",{"type":1483,"name":1395,"icon":1443},"render.workflow",{"type":1485,"name":1486,"icon":1443},"render.domain","Custom Domain",{"type":1488,"name":1489,"icon":1443},"render.postgres","Postgres Database",{"type":1491,"name":1492,"icon":1443},"render.key_value","Key-Value Store",{"type":1494,"name":1495,"icon":1443},"render.disk","Persistent Disk",{"type":1497,"name":1498,"icon":1443},"render.env_group","Environment Group",{"whatPolylaneDoes":1500,"howItWorks":1513},[1501,1504,1507,1510],{"title":1502,"body":1503},"Every service in one graph","Web services, private services, background workers, cron jobs, Postgres, and key-value stores, with their environments, edges, and history.",{"title":1505,"body":1506},"The jobs that fail quietly","Background workers and cron jobs don't page anyone when they break; they just stop. Polylane notices, investigates, and tells you before the backlog does.",{"title":1508,"body":1509},"Metrics and logs read on a cadence","Agents comb each service's telemetry and judge it against how that service normally behaves. No thresholds to tune.",{"title":1511,"body":1512},"Rollback, then the permanent fix","Off by default. Enabled, agents restore the last known-good deploy on their own, rate-limited and on the record, and the permanent fix follows.",[1514,1516,1518],{"title":310,"body":1515},"Paste an API key from your Render account settings. It's encrypted before it's stored, and the agent never sees it.",{"title":313,"body":1517},"Services, databases, and domains land in the graph, and every sync after records what changed.",{"title":316,"body":1519},"Telemetry is combed on a cadence, deploy failures get investigated as they land, and fixes arrive for your review.",{"type":1521,"category":753,"subcategory":753,"name":1522,"description":1523,"longDescription":1524,"icon":1525,"comingSoon":20,"lifecycle":1526,"tools":1529,"supportedResources":1536,"marketing":1543},"planetscale","PlanetScale","Databases, branches, and schema changes","Connect your PlanetScale organization to give agents visibility into your databases and branches. Agents can track schema changes, monitor branch state, and correlate database activity with the rest of your infrastructure.","PlanetscaleLogo",{"connect":431,"browser":170,"headlessConnect":170,"teardown":171,"residue":1527},[1528],"OAuth grant",[1530,1533],{"name":1531,"summary":1532},"planetscaleApi","Call any PlanetScale REST API endpoint that lacks a dedicated tool",{"name":1534,"summary":1535},"planetscaleGetQueryInsights","Get PlanetScale Query Insights for a database branch: top queries, query errors, or latency anomalies",[1537,1540],{"type":1538,"name":1539,"icon":1525},"planetscale.database","Database",{"type":1541,"name":1542,"icon":1525},"planetscale.branch","Database Branch",{"whatPolylaneDoes":1544,"howItWorks":1557},[1545,1548,1551,1554],{"title":1546,"body":1547},"Databases and branches in the graph","Every database and branch with its plan, region, schema state, and history. MySQL and Postgres, next to everything else you run.",{"title":1549,"body":1550},"Linked to the services that query them","Polylane matches connection hosts and usernames, so when checkout latency spikes, the graph already knows the database behind it.",{"title":1552,"body":1553},"Query Insights as evidence","Mid-investigation, agents pull the slow queries, the erroring queries, and the latency windows PlanetScale itself flagged.",{"title":1555,"body":1556},"Your rows stay yours","Polylane reads the PlanetScale API and nothing else: it never connects to your databases, never sees your rows, and never holds database credentials.",[1558,1560,1563],{"title":310,"body":1559},"OAuth with read scopes only. Click connect, approve in PlanetScale, and syncing starts.",{"title":1561,"body":1562},"Link","Databases and branches join the graph, matched to the services that query them.",{"title":1564,"body":1565},"Investigations reach the query","A regression traces from the service, to the branch, to the exact query, and the fix arrives for your review.",{"type":1567,"category":753,"subcategory":753,"name":1568,"description":1569,"longDescription":1570,"icon":1571,"comingSoon":20,"lifecycle":1572,"tools":1574,"supportedResources":1587,"marketing":1608},"railway","Railway","Projects, services, deployments, and volumes","Connect your Railway workspace to give agents visibility into your projects, environments, services, and deployments. Agents can track deploy status, watch service resource usage, and correlate Railway activity with the rest of your infrastructure.","RailwayLogo",{"connect":431,"browser":170,"headlessConnect":20,"teardown":171,"residue":1573},[1528],[1575,1578,1581,1584],{"name":1576,"summary":1577},"railwayApi","Run a curated Railway GraphQL operation (reads, restarts, redeploys, scaling)",{"name":1579,"summary":1580},"railwayGetLogs","Get runtime logs for a Railway service or deployment",{"name":1582,"summary":1583},"railwayListDeployments","List recent Railway deployments for a project",{"name":1585,"summary":1586},"railwayQueryMetrics","Query CPU, memory, network, and disk metrics for Railway services",[1588,1590,1592,1595,1597,1600,1602,1605],{"type":1589,"name":1357,"icon":1571},"railway.project",{"type":1591,"name":1467,"icon":1571},"railway.environment",{"type":1593,"name":1594,"icon":1571},"railway.service","Service",{"type":1596,"name":1360,"icon":1571},"railway.deployment",{"type":1598,"name":1599,"icon":1571},"railway.volume","Volume",{"type":1601,"name":1199,"icon":1571},"railway.domain",{"type":1603,"name":1604,"icon":1571},"railway.tcp_proxy","TCP Proxy",{"type":1606,"name":1607,"icon":1571},"railway.notification_rule","Notification Rule",{"whatPolylaneDoes":1609,"howItWorks":1621},[1610,1613,1616,1618],{"title":1611,"body":1612},"Your whole workspace in one graph","Projects, environments, services, deployments, volumes, domains, and TCP proxies, with their edges and history. Template databases next to the services that use them.",{"title":1614,"body":1615},"Deploys watched as they land","Railway webhooks alert on failed and crashed deployments the moment they happen, resolve the alert on the next success, and can trigger an agent to investigate every deploy.",{"title":1508,"body":1617},"Agents comb each service's CPU, memory, and disk against how that service normally behaves, and pull deploy and runtime logs mid-investigation. No thresholds to tune.",{"title":1619,"body":1620},"Your secrets stay yours","Polylane syncs variable names for cross-cloud linking and never reads variable values. Tokens are encrypted before they're stored, and the agent never sees them.",[1622,1624,1626],{"title":310,"body":1623},"OAuth with read scopes only. Click connect, approve in Railway, and syncing starts.",{"title":313,"body":1625},"Projects, services, deployments, and volumes land in the graph, and every sync after records what changed.",{"title":316,"body":1627},"Deploy failures get investigated as they land, resource usage is judged against each service's normal, and fixes arrive for your review.",{"type":1629,"category":753,"subcategory":753,"name":1630,"description":1631,"longDescription":1632,"icon":1633,"comingSoon":20,"lifecycle":1634,"tools":1636,"supportedResources":1649,"marketing":1664},"fly","Fly.io","Machines, volumes, and global edge deployments","Connect your Fly.io account to let agents monitor your machines, volumes, and global deployments. Agents can check app health, analyze regional performance, and help manage your distributed infrastructure.","FlyLogo",{"connect":252,"browser":20,"headlessConnect":170,"teardown":325,"residue":1635},[],[1637,1640,1643,1646],{"name":1638,"summary":1639},"flyApi","Call any Fly.io Machines REST endpoint that lacks a dedicated tool",{"name":1641,"summary":1642},"flyListReleases","List release history for a Fly.io app",{"name":1644,"summary":1645},"flyQueryMetrics","Query Fly.io Prometheus metrics for an app",{"name":1647,"summary":1648},"flyGetLogs","Get logs for a Fly.io app via Prometheus metrics",[1650,1653,1656,1658,1661],{"type":1651,"name":1652,"icon":1633},"fly.app","Fly App",{"type":1654,"name":1655,"icon":1633},"fly.machine","Machine",{"type":1657,"name":1599,"icon":1633},"fly.volume",{"type":1659,"name":1660,"icon":1633},"fly.certificate","Certificate",{"type":1662,"name":1663,"icon":1633},"fly.secret","Secret",{"whatPolylaneDoes":1665,"howItWorks":1678},[1666,1669,1672,1675],{"title":1667,"body":1668},"The whole fleet in one graph","Every app with its machines, volumes, certificates, and secrets, next to whatever else you run on other clouds.",{"title":1670,"body":1671},"Every region at once","Your machines run wherever your users are; your attention can't. Agents see the whole fleet, so one bad region stands out against the ones that are fine.",{"title":1673,"body":1674},"Detection without alert rules","Agents comb app and machine metrics and logs on a cadence and judge them against how each app normally behaves.",{"title":1676,"body":1677},"History for a fleet that churns","Machines deploy, stop, start, and move. Each sync records what appeared, changed, or disappeared, so investigations start from the change.",[1679,1681,1683],{"title":310,"body":1680},"Paste a read-only API token, the most restrictive type Fly offers. It's encrypted before it's stored, and the agent never sees it.",{"title":313,"body":1682},"Apps, machines, and volumes land in the graph with their regions and history.",{"title":316,"body":1684},"The fleet is watched in every region at once, and investigations don't wait for your timezone.",{"type":1686,"category":753,"subcategory":753,"name":1687,"description":1688,"longDescription":1689,"icon":1690,"comingSoon":20,"lifecycle":1691,"tools":1695,"supportedResources":1699,"marketing":1769},"kubernetes","Kubernetes","Pods, Deployments, Nodes, Services, and more","Install the Polylane agent in any Kubernetes cluster to give agents read-only visibility into your workloads. Agents can map your cluster topology, inspect pods, deployments and nodes, read logs and events, and help troubleshoot incidents.","i-logos-kubernetes",{"connect":1692,"browser":20,"headlessConnect":20,"teardown":171,"residue":1693},"helm",[1694],"Helm release and agent pods in the cluster",[1696],{"name":1697,"summary":1698},"kubectl","Read and operate on Kubernetes resources on a connected cluster (get\u002Flist\u002Fdescribe\u002Flogs\u002Fevents\u002Ftop\u002Frollout, plus scale, restart, patch, delete, apply)",[1700,1703,1706,1708,1711,1714,1717,1720,1723,1726,1728,1731,1734,1736,1739,1742,1745,1748,1751,1754,1757,1760,1763,1766],{"type":1701,"name":1702,"icon":1007},"k8s.namespace","Namespace",{"type":1704,"name":1705,"icon":1007},"k8s.node","Node",{"type":1707,"name":1360,"icon":1007},"k8s.deployment",{"type":1709,"name":1710,"icon":1007},"k8s.statefulset","StatefulSet",{"type":1712,"name":1713,"icon":1007},"k8s.daemonset","DaemonSet",{"type":1715,"name":1716,"icon":1007},"k8s.replicaset","ReplicaSet",{"type":1718,"name":1719,"icon":1007},"k8s.job","Job",{"type":1721,"name":1722,"icon":1007},"k8s.cronjob","CronJob",{"type":1724,"name":1725,"icon":1007},"k8s.pod","Pod",{"type":1727,"name":1594,"icon":1007},"k8s.service",{"type":1729,"name":1730,"icon":1007},"k8s.ingress","Ingress",{"type":1732,"name":1733,"icon":1007},"k8s.configmap","ConfigMap",{"type":1735,"name":1663,"icon":1007},"k8s.secret",{"type":1737,"name":1738,"icon":1007},"k8s.service_account","Service Account",{"type":1740,"name":1741,"icon":1007},"k8s.role","Role",{"type":1743,"name":1744,"icon":1007},"k8s.role_binding","Role Binding",{"type":1746,"name":1747,"icon":1007},"k8s.cluster_role","Cluster Role",{"type":1749,"name":1750,"icon":1007},"k8s.cluster_role_binding","Cluster Role Binding",{"type":1752,"name":1753,"icon":1007},"k8s.persistent_volume","Persistent Volume",{"type":1755,"name":1756,"icon":1007},"k8s.persistent_volume_claim","Persistent Volume Claim",{"type":1758,"name":1759,"icon":1007},"k8s.storage_class","Storage Class",{"type":1761,"name":1762,"icon":1007},"k8s.network_policy","Network Policy",{"type":1764,"name":1765,"icon":1007},"k8s.hpa","Horizontal Pod Autoscaler",{"type":1767,"name":1768,"icon":1007},"k8s.pdb","Pod Disruption Budget",{"whatPolylaneDoes":1770,"howItWorks":1783},[1771,1774,1777,1780],{"title":1772,"body":1773},"The full cluster topology","Deployments, StatefulSets, pods, services, ingresses, CronJobs, and 24 resource types in all, alongside the clouds the cluster runs on.",{"title":1775,"body":1776},"The failures Kubernetes hides well","Crashloops, OOM kills, pods stuck pending, rollouts that never converge. The cluster knows; Polylane investigates and writes up what happened.",{"title":1778,"body":1779},"Direct inspection","Agents inspect pods, read logs and events, and map the topology on a cadence. No dashboards in the loop.",{"title":1781,"body":1782},"get, list, watch, and nothing else","The in-cluster agent runs with read-only RBAC, and Polylane only makes read-only Kubernetes API calls.",[1784,1786,1789],{"title":310,"body":1785},"Install the Polylane agent in your cluster with one Helm command. It registers itself over an outbound tunnel, and your cluster credentials never leave the cluster.",{"title":1787,"body":1788},"Map","The cluster topology lands in the graph, and every sync after records what changed.",{"title":316,"body":1790},"Workloads are watched as they churn, failures get investigated as they happen, and manifest fixes arrive for your review.",{"type":1792,"category":753,"subcategory":753,"name":1793,"description":1794,"longDescription":1795,"icon":1796,"comingSoon":20,"lifecycle":1797,"tools":1799,"supportedResources":1812,"marketing":1847},"supabase","Supabase","Database, auth, storage, and edge functions","Connect your Supabase project to let agents monitor your database, auth, storage, and edge functions. Agents can analyze query performance, check auth flows, and help optimize your backend.","SupabaseLogo",{"connect":431,"browser":170,"headlessConnect":170,"teardown":171,"residue":1798},[1528],[1800,1803,1806,1809],{"name":1801,"summary":1802},"supabaseApi","Call any Supabase Management API endpoint that lacks a dedicated tool",{"name":1804,"summary":1805},"supabaseGetLogs","Get Supabase service logs for a project: API gateway, edge functions, Postgres, Auth, Storage, or Realtime",{"name":1807,"summary":1808},"supabaseGetAdvisors","Get Supabase security and performance advisor findings for a project",{"name":1810,"summary":1811},"supabaseGetProjectHealth","Get the live health of a Supabase project's bundled services (database, REST, Auth, Storage, Realtime)",[1813,1815,1817,1820,1823,1825,1828,1831,1834,1837,1840,1842,1844],{"type":1814,"name":1357,"icon":1796},"supabase.project",{"type":1816,"name":1489,"icon":1796},"supabase.database",{"type":1818,"name":1819,"icon":1796},"supabase.pooler","Connection Pooler",{"type":1821,"name":1822,"icon":1796},"supabase.function","Edge Function",{"type":1824,"name":1542,"icon":1796},"supabase.branch",{"type":1826,"name":1827,"icon":1796},"supabase.bucket","Storage Bucket",{"type":1829,"name":1830,"icon":1796},"supabase.auth","Auth Service",{"type":1832,"name":1833,"icon":1796},"supabase.storage","Storage Service",{"type":1835,"name":1836,"icon":1796},"supabase.realtime","Realtime Service",{"type":1838,"name":1839,"icon":1796},"supabase.rest","REST API",{"type":1841,"name":1486,"icon":1796},"supabase.custom_domain",{"type":1843,"name":1663,"icon":1796},"supabase.secret",{"type":1845,"name":1846,"icon":1796},"supabase.network_restrictions","Network Restrictions",{"whatPolylaneDoes":1848,"howItWorks":1860},[1849,1852,1855,1858],{"title":1850,"body":1851},"Projects and their pieces in the graph","Every project with its edge functions, database branches, and storage buckets, next to everything else you run.",{"title":1853,"body":1854},"Linked to the services that use them","Polylane matches Supabase hosts in env vars across your other clouds, so the graph already knows which service talks to which project.",{"title":1856,"body":1857},"Change history per sync","Functions redeploy, branches come and go, buckets appear. Each sync records what changed, so investigations start from the change.",{"title":1555,"body":1859},"Polylane reads the Supabase Management API and nothing else: it never connects to your databases, never sees your rows, and never stores project API keys.",[1861,1863,1865],{"title":310,"body":1862},"OAuth with read scopes, or paste a personal access token. Either way it's encrypted before it's stored, and the agent never sees it.",{"title":313,"body":1864},"Projects, edge functions, branches, and buckets land in the graph with their history.",{"title":644,"body":1866},"A failing function or an unhealthy project traces to the services around it, and the fix arrives for your review.",{"type":1868,"category":753,"subcategory":753,"name":1869,"description":1870,"longDescription":1871,"icon":1872,"comingSoon":20,"lifecycle":1873,"tools":1875,"supportedResources":1891},"modal","Modal","Serverless GPU apps, functions, and sandboxes","Connect your Modal workspace to map its environments, apps, functions, web endpoints, sandboxes, volumes, secrets, queues, and dicts into the context graph. Agents can then reason about what runs where, what each function depends on, and what changed between syncs.","ModalLogo",{"connect":252,"browser":20,"headlessConnect":170,"teardown":325,"residue":1874},[],[1876,1879,1882,1885,1888],{"name":1877,"summary":1878},"modalGetLogs","Get Modal app logs: per-bucket volume by stream plus sampled lines",{"name":1880,"summary":1881},"modalListSandboxes","List Modal sandboxes in an environment, with their state and resource shape",{"name":1883,"summary":1884},"modalListDeployments","List Modal app deployments: version, who deployed, and when",{"name":1886,"summary":1887},"modalDescribeApp","Describe one Modal app: state, deploy provenance, and the functions inside it",{"name":1889,"summary":1890},"modalGetCost","Get metered Modal spend, for one app or broken down across the workspace",[1892,1894,1897,1900,1903,1905,1908,1910,1912,1915],{"type":1893,"name":1467,"icon":1872},"modal.environment",{"type":1895,"name":1896,"icon":1872},"modal.app","App",{"type":1898,"name":1899,"icon":1872},"modal.function","Function",{"type":1901,"name":1902,"icon":1872},"modal.class","Class",{"type":1904,"name":1392,"icon":1872},"modal.sandbox",{"type":1906,"name":1907,"icon":1872},"modal.image","Image",{"type":1909,"name":1599,"icon":1872},"modal.volume",{"type":1911,"name":1663,"icon":1872},"modal.secret",{"type":1913,"name":1914,"icon":1872},"modal.queue","Queue",{"type":1916,"name":1917,"icon":1872},"modal.dict","Dict",{"type":1919,"category":753,"subcategory":753,"name":1920,"description":1921,"longDescription":1922,"icon":1923,"comingSoon":20,"lifecycle":1924,"tools":1926,"supportedResources":1936,"marketing":1941},"convex","Convex","Reactive backend platform with database, functions, and deployments","Connect your Convex team to map its projects and deployments into the context graph. Agents can then reason about which environments exist, where each project's production deployment lives, and what changed between syncs.","ConvexLogo",{"connect":252,"browser":20,"headlessConnect":170,"teardown":325,"residue":1925},[],[1927,1930,1933],{"name":1928,"summary":1929},"convexApi","Call any Convex Management API endpoint that lacks a dedicated tool",{"name":1931,"summary":1932},"convexGetLogs","Get function execution logs for a Convex deployment",{"name":1934,"summary":1935},"convexQueryMetrics","Query function metrics for a Convex deployment",[1937,1939],{"type":1938,"name":1357,"icon":1923},"convex.project",{"type":1940,"name":1360,"icon":1923},"convex.deployment",{"whatPolylaneDoes":1942,"howItWorks":1955},[1943,1946,1949,1952],{"title":1944,"body":1945},"Projects and deployments in the graph","Every project with its production, preview, and development deployments, their regions and URLs, next to everything else you run.",{"title":1947,"body":1948},"Production separated from the noise","Dev and preview deployments stay visible on the map, but only production changes reach change intelligence and incidents.",{"title":1950,"body":1951},"Change history on every sync","New deployments, deleted projects, and re-pointed production deployments land in the change feed with the sync that found them.",{"title":1953,"body":1954},"Your data stays yours","Polylane reads the Convex Management API and nothing else: it never queries your tables and never holds deploy keys.",[1956,1958,1960],{"title":310,"body":1957},"Paste a team access token from your Convex team settings. It's encrypted before it's stored, and the agent never sees it.",{"title":313,"body":1959},"Projects and deployments land in the graph, and every sync after records what changed.",{"title":1961,"body":1962},"Agents use the map","Investigations reach from a service to the Convex deployment behind it, with its region, class, and deploy history in hand.",{"type":1964,"category":753,"subcategory":753,"name":1965,"description":1966,"longDescription":1967,"icon":1968,"comingSoon":20,"lifecycle":1969,"tools":1972,"supportedResources":1988},"triggerdev","Trigger.dev","Background jobs, scheduled tasks, and workflow runs","Connect a Trigger.dev environment to map its tasks, schedules, queues and current deployment into the context graph. Agents can then see which jobs run where, which version defines them, and which queue each one waits on.","TriggerdevLogo",{"connect":252,"browser":20,"headlessConnect":170,"teardown":171,"residue":1970},[1971],"Trigger.dev webhook alert",[1973,1976,1979,1982,1985],{"name":1974,"summary":1975},"triggerdevRuns","List Trigger.dev runs with filters, retrieve one run with its attempts, or read the error groups failed runs fold into",{"name":1977,"summary":1978},"triggerdevRunTelemetry","Read a Trigger.dev run's trace tree or its log events",{"name":1980,"summary":1981},"triggerdevQuery","Query Trigger.dev run history with TRQL, or read its schema and dashboard queries",{"name":1983,"summary":1984},"triggerdevInventory","Read what a Trigger.dev environment is made of: deployments and the current one, bulk actions, schedules, queues and a queue's wait time and depth metrics",{"name":1986,"summary":1987},"triggerdevApi","Read any Trigger.dev REST API endpoint that lacks a dedicated tool",[1989,1991,1994,1997,1999],{"type":1990,"name":1467,"icon":1968},"triggerdev.environment",{"type":1992,"name":1993,"icon":1968},"triggerdev.task","Task",{"type":1995,"name":1996,"icon":1968},"triggerdev.schedule","Schedule",{"type":1998,"name":1914,"icon":1968},"triggerdev.queue",{"type":2000,"name":1360,"icon":1968},"triggerdev.deployment",{"type":2002,"category":753,"subcategory":753,"name":2003,"description":2004,"longDescription":2005,"icon":2006,"comingSoon":20,"lifecycle":2007,"tools":2009,"supportedResources":2019},"clickhouse","ClickHouse","Cloud services, state, and connection endpoints","Connect your ClickHouse Cloud organization to map its services into the context graph, including state, tier, region, version, and replica sizing. Agents can monitor service health, catch stopped or degraded services, and correlate your analytical database with the rest of your infrastructure.","ClickhouseLogo",{"connect":252,"browser":20,"headlessConnect":170,"teardown":325,"residue":2008},[],[2010,2013,2016],{"name":2011,"summary":2012},"clickhouseApi","Call any ClickHouse Cloud API endpoint that lacks a dedicated tool",{"name":2014,"summary":2015},"clickhouseListServices","List ClickHouse Cloud services with state, sizing, version, and endpoints",{"name":2017,"summary":2018},"clickhouseGetMetrics","Read live ClickHouse Cloud service metrics (CPU, memory, connections, queries) from the Prometheus endpoint",[2020],{"type":2021,"name":1594,"icon":2006},"clickhouse.service",{"type":2023,"category":753,"subcategory":753,"name":2024,"description":2025,"longDescription":2026,"icon":2027,"comingSoon":20,"lifecycle":2028,"tools":2030,"supportedResources":2031,"marketing":2037},"turso","Turso","Database groups and edge-hosted libSQL databases","Connect your Turso organization to give agents visibility into your database groups and edge-hosted libSQL databases. Agents can track database placement across locations, monitor branching, and correlate database activity with the rest of your infrastructure.","TursoLogo",{"connect":252,"browser":20,"headlessConnect":170,"teardown":325,"residue":2029},[],[],[2032,2035],{"type":2033,"name":2034,"icon":2027},"turso.group","Database Group",{"type":2036,"name":1539,"icon":2027},"turso.database",{"whatPolylaneDoes":2038,"howItWorks":2049},[2039,2042,2044,2047],{"title":2040,"body":2041},"Groups and databases in the graph","Every database group and libSQL database with its locations, placement, and branching parentage, next to everything else you run.",{"title":1549,"body":2043},"Polylane matches database hostnames, so when a service slows down, the graph already knows the database behind it.",{"title":2045,"body":2046},"Change intelligence on your data layer","New databases, moved groups, and blocked reads or writes show up as changes agents can reason about mid-investigation.",{"title":1555,"body":2048},"Polylane reads the Turso Platform API and nothing else: it never connects to your databases, never sees your rows, and never holds database credentials.",[2050,2052,2054],{"title":310,"body":2051},"Paste a platform API token, pick the organization, and syncing starts.",{"title":1561,"body":2053},"Groups and databases join the graph, matched to the services that query them.",{"title":316,"body":2055},"Every sync records what changed, and investigations trace from the service to the exact database.",{"type":2057,"category":753,"subcategory":753,"name":2058,"description":2059,"longDescription":2060,"icon":2061,"comingSoon":170,"lifecycle":2062,"tools":2064,"supportedResources":2065},"gcp","GCP","Compute Engine, Cloud Run, GKE, and Cloud SQL","Connect your Google Cloud Platform account to give agents visibility into your GCP infrastructure including Compute Engine, Cloud Run, GKE, and Cloud SQL. Agents can monitor resources and help optimize your cloud environment.","i-logos-google-cloud",{"connect":493,"browser":20,"headlessConnect":20,"teardown":493,"residue":2063},[],[],[],{"type":2067,"category":753,"subcategory":753,"name":2068,"description":2069,"longDescription":2070,"icon":2071,"comingSoon":170,"lifecycle":2072,"tools":2074,"supportedResources":2075},"azure","Azure","VMs, App Service, AKS, and Azure SQL","Connect your Azure account to give agents visibility into your Azure infrastructure including Virtual Machines, App Service, AKS, and Azure SQL. Agents can monitor resources and help manage your cloud environment.","i-logos-microsoft-azure",{"connect":493,"browser":20,"headlessConnect":20,"teardown":493,"residue":2073},[],[],[],{"type":2077,"category":753,"subcategory":753,"name":2078,"description":2079,"longDescription":2080,"icon":2081,"comingSoon":170,"lifecycle":2082,"tools":2084,"supportedResources":2085},"runpod","Runpod","On-demand GPU pods, serverless endpoints, and clusters","Connect your Runpod account to give agents visibility into your GPU pods, serverless endpoints, and clusters. Agents can monitor worker health, inspect failed jobs, and help you understand your GPU spend.","RunpodLogo",{"connect":493,"browser":20,"headlessConnect":20,"teardown":493,"residue":2083},[],[],[],{"type":2087,"category":753,"subcategory":753,"name":2088,"description":2089,"longDescription":2090,"icon":2091,"comingSoon":170,"lifecycle":2092,"tools":2094,"supportedResources":2095},"parasail","Parasail","Inference endpoints, batch jobs, and model deployments","Connect your Parasail account to give agents visibility into your inference endpoints and batch jobs. Agents can monitor request latency, check deployment health, and help troubleshoot serving issues.","ParasailLogo",{"connect":493,"browser":20,"headlessConnect":20,"teardown":493,"residue":2093},[],[],[],{"type":2097,"category":753,"subcategory":753,"name":2098,"description":2099,"longDescription":2100,"icon":2101,"comingSoon":170,"lifecycle":2102,"tools":2104,"supportedResources":2105},"baseten","Baseten","Model deployments, inference endpoints, and autoscaling","Connect your Baseten workspace to give agents visibility into your model deployments and inference endpoints. Agents can monitor autoscaling behavior, inspect failed predictions, and help troubleshoot cold starts.","BasetenLogo",{"connect":493,"browser":20,"headlessConnect":20,"teardown":493,"residue":2103},[],[],[],{"type":2107,"category":753,"subcategory":753,"name":2108,"description":2109,"longDescription":2110,"icon":2111,"comingSoon":170,"lifecycle":2112,"tools":2114,"supportedResources":2115},"upstash","Upstash","Serverless Redis, Kafka, and vector databases","Connect your Upstash account to give agents visibility into your serverless Redis, Kafka, and vector databases. Agents can monitor usage, analyze performance, and help troubleshoot your data layer.","UpstashLogo",{"connect":493,"browser":20,"headlessConnect":20,"teardown":493,"residue":2113},[],[],[],{"type":2117,"category":753,"subcategory":753,"name":2118,"description":2119,"longDescription":2120,"icon":2121,"comingSoon":170,"lifecycle":2122,"tools":2124,"supportedResources":2125},"digitalocean","Digital Ocean","Modern cloud provider","Connect your Digital Ocean account to let agents monitor your Digital Ocean infrastructure. Agents can analyze resource usage, check service health, and help troubleshoot infrastructure issues.","i-logos:digital-ocean-icon",{"connect":493,"browser":20,"headlessConnect":20,"teardown":493,"residue":2123},[],[],[],{"type":2127,"category":753,"subcategory":753,"name":2128,"description":2129,"longDescription":2130,"icon":2131,"comingSoon":170,"lifecycle":2132,"tools":2134,"supportedResources":2135},"firebase","Firebase","Firestore, Cloud Functions, hosting, and auth","Connect your Firebase project to give agents visibility into your Firestore database, Cloud Functions, hosting, and authentication. Agents can monitor usage, analyze performance, and help optimize your app.","i-logos-firebase-icon",{"connect":493,"browser":20,"headlessConnect":20,"teardown":493,"residue":2133},[],[],[],{"type":2137,"category":753,"subcategory":753,"name":2138,"description":2139,"longDescription":2140,"icon":2141,"comingSoon":170,"lifecycle":2142,"tools":2144,"supportedResources":2145},"clerk","Clerk","User authentication, sessions, and organizations","Connect your Clerk application to give agents visibility into your authentication stack. Agents can monitor sign-up and sign-in activity, inspect user and organization data, and help troubleshoot authentication issues.","i-simple-icons-clerk",{"connect":493,"browser":20,"headlessConnect":20,"teardown":493,"residue":2143},[],[],[],{"type":2147,"category":753,"subcategory":753,"name":2148,"description":2149,"longDescription":2150,"icon":2151,"comingSoon":170,"lifecycle":2152,"tools":2154,"supportedResources":2155},"workos","WorkOS","SSO, directory sync, and enterprise auth","Connect your WorkOS environment to give agents visibility into your enterprise authentication. Agents can inspect SSO connections, monitor directory sync, and help troubleshoot login and provisioning issues.","i-logos-workos-icon",{"connect":493,"browser":20,"headlessConnect":20,"teardown":493,"residue":2153},[],[],[],{"type":2157,"category":753,"subcategory":753,"name":2158,"description":2159,"longDescription":2160,"icon":2161,"comingSoon":170,"lifecycle":2162,"tools":2164,"supportedResources":2165},"unkey","Unkey","API keys, rate limits, and verification analytics","Connect your Unkey workspace to give agents visibility into your API keys, identities, and rate limits. Agents can monitor key verifications, catch rate-limit spikes, and help troubleshoot API authentication issues.","UnkeyLogo",{"connect":493,"browser":20,"headlessConnect":20,"teardown":493,"residue":2163},[],[],[],{"type":2167,"category":753,"subcategory":753,"name":2168,"description":2169,"longDescription":2170,"icon":2171,"comingSoon":170,"lifecycle":2172,"tools":2174,"supportedResources":2175},"hatchet","Hatchet","Task queues, workflows, and durable execution","Connect your Hatchet tenant to give agents visibility into your task queues and workflow runs. Agents can monitor queue health, inspect failed and stuck runs, and help troubleshoot worker and concurrency issues.","HatchetLogo",{"connect":493,"browser":20,"headlessConnect":20,"teardown":493,"residue":2173},[],[],[],{"type":2177,"category":162,"subcategory":246,"name":2178,"description":2179,"longDescription":2180,"icon":2181,"comingSoon":170,"lifecycle":2182,"tools":2184,"supportedResources":2185},"signoz","SigNoz","Query traces, metrics, and logs from SigNoz","Connect your SigNoz instance to let agents query distributed traces, explore metrics, and search logs. Agents can analyze your OpenTelemetry data to investigate latency, errors, and service health.","SignozLogo",{"connect":493,"browser":20,"headlessConnect":20,"teardown":493,"residue":2183},[],[],[],{"type":2187,"category":162,"subcategory":246,"name":2188,"description":2189,"longDescription":2190,"icon":2191,"comingSoon":170,"lifecycle":2192,"tools":2194,"supportedResources":2195},"langsmith","LangSmith","Trace, evaluate, and monitor LLM applications from LangSmith","Connect your LangSmith organization to let agents query traces, inspect runs, and review evaluation results. Agents can analyze your LLM application telemetry to debug chains, track quality, and understand model behavior.","i-simple-icons-langchain",{"connect":493,"browser":20,"headlessConnect":20,"teardown":493,"residue":2193},[],[],[],{"type":2197,"category":162,"subcategory":246,"name":2198,"description":2199,"longDescription":2200,"icon":2201,"comingSoon":170,"lifecycle":2202,"tools":2204,"supportedResources":2205},"braintrust","Braintrust","Evals, logging, and prompt monitoring from Braintrust","Connect your Braintrust organization to let agents query experiment results, inspect logs, and review evals. Agents can correlate model performance with your infrastructure to catch regressions in AI features.","i-simple-icons-braintrust",{"connect":493,"browser":20,"headlessConnect":20,"teardown":493,"residue":2203},[],[],[],{"type":2207,"category":162,"subcategory":246,"name":2208,"description":2209,"longDescription":2210,"icon":2211,"comingSoon":170,"lifecycle":2212,"tools":2214,"supportedResources":2215},"arize","Arize","LLM observability, evals, and model monitoring from Arize","Connect your Arize space to let agents query traces, monitor model performance, and review evaluation results. Agents can analyze your LLM and ML telemetry to investigate drift, latency, and quality regressions.","ArizeLogo",{"connect":493,"browser":20,"headlessConnect":20,"teardown":493,"residue":2213},[],[],[],{"type":2217,"category":162,"subcategory":731,"name":2218,"description":2219,"longDescription":2220,"icon":2221,"comingSoon":20,"lifecycle":2222,"tools":2224,"supportedResources":2237,"marketing":2238},"linear","Linear","Create and manage Linear issues from Polylane","Connect Linear to let agents create issues, update statuses, and track project progress. Agents can automatically file bugs from investigations and keep your product development workflow in sync with your infrastructure.","i-simple-icons-linear",{"connect":252,"browser":20,"headlessConnect":170,"teardown":325,"residue":2223},[],[2225,2228,2231,2234],{"name":2226,"summary":2227},"linearApi","Run any Linear GraphQL query or mutation that lacks a dedicated tool",{"name":2229,"summary":2230},"linearTeams","List Linear teams, workflow states, and members",{"name":2232,"summary":2233},"linearProjects","List Linear projects and their delivery state",{"name":2235,"summary":2236},"linearIssues","Read, search, create, update, and comment on Linear issues",[],{"whatPolylaneDoes":2239,"howItWorks":2249},[2240,2243,2246],{"title":2241,"body":2242},"Findings become issues","When an investigation ends at something your team has to fix, the agent files it in Linear with the evidence trail in the description, on the right team with the right priority.",{"title":2244,"body":2245},"Issues move with the work","Agents update state, priority, and assignee as the situation changes, and leave comments with what they found, so Linear reflects reality without anyone retyping it.",{"title":2247,"body":2248},"Queried mid-conversation","Ask what is open, in progress, or assigned to someone and the agent reads it straight from Linear, teams, projects, and issues alike.",[2250,2252,2255],{"title":310,"body":2251},"Paste a Linear API key. It's encrypted before it's stored.",{"title":2253,"body":2254},"Agents see your workspace","Teams, projects, workflow states, and issues become queryable in every thread.",{"title":2256,"body":2257},"Issues get filed","When agents create or change an issue, you confirm the action first, and the result links back to the thread.",{"type":2259,"category":162,"subcategory":697,"name":2260,"description":2261,"longDescription":2262,"icon":2263,"comingSoon":170,"lifecycle":2264,"tools":2266,"supportedResources":2267},"microsoft-teams","Microsoft Teams","Work with Polylane directly in Microsoft Teams","Bring Polylane into your Microsoft Teams workspace so your team can interact with agents directly in channels. Get notifications, ask questions, and trigger investigations without leaving your communication tools.","i-logos-microsoft-teams",{"connect":493,"browser":20,"headlessConnect":20,"teardown":493,"residue":2265},[],[],[],{"type":2269,"category":162,"subcategory":2270,"name":2271,"description":2272,"longDescription":2273,"icon":2274,"comingSoon":170,"lifecycle":2275,"tools":2277,"supportedResources":2278},"confluence","knowledge-base","Confluence","Read and write Confluence pages from Polylane","Connect Confluence to let agents search pages, pull context from your documentation, and draft runbooks or postmortems. Agents can ground their answers in your team's knowledge base and keep docs up to date.","i-logos-confluence",{"connect":493,"browser":20,"headlessConnect":20,"teardown":493,"residue":2276},[],[],[],{"type":2280,"category":162,"subcategory":2270,"name":2281,"description":2282,"longDescription":2283,"icon":2284,"comingSoon":170,"lifecycle":2285,"tools":2287,"supportedResources":2288},"notion","Notion","Read and write Notion pages and databases","Connect Notion to let agents search pages, query databases, and create new entries. Agents can pull context from your wikis and runbooks, and capture findings from investigations directly in your workspace.","i-logos-notion-icon",{"connect":493,"browser":20,"headlessConnect":20,"teardown":493,"residue":2286},[],[],[],{"type":2290,"category":162,"subcategory":163,"name":2291,"description":2292,"longDescription":2293,"icon":2294,"comingSoon":170,"lifecycle":2295,"tools":2297,"supportedResources":2298},"gitlab","GitLab","Connect GitLab for enhanced codebase context","Give agents access to your GitLab repositories for code search, merge request context, and codebase understanding. Agents can browse files, understand your architecture, and provide more accurate answers grounded in your actual code.","i-logos-gitlab-icon",{"connect":493,"browser":20,"headlessConnect":20,"teardown":493,"residue":2296},[],[],[],{"type":2300,"category":162,"subcategory":742,"name":2301,"description":744,"longDescription":2302,"icon":2303,"comingSoon":170,"lifecycle":2304,"tools":2306,"supportedResources":2307},"incident-io","incident.io","Connect incident.io to let agents declare incidents, update statuses, and pull context from active response efforts. Agents can correlate infrastructure issues with ongoing incidents to speed up resolution.","i-logos-incident-icon",{"connect":493,"browser":20,"headlessConnect":20,"teardown":493,"residue":2305},[],[],[],{"type":2309,"category":753,"subcategory":753,"name":2310,"description":2311,"longDescription":2312,"icon":2313,"comingSoon":170,"lifecycle":2314,"tools":2316,"supportedResources":2317},"netlify","Netlify","Deployments, serverless functions, and edge handlers","Connect your Netlify account to give agents visibility into your deployments, serverless functions, and edge handlers. Agents can monitor build status, analyze traffic, and help troubleshoot deployment issues.","i-logos-netlify-icon",{"connect":493,"browser":20,"headlessConnect":20,"teardown":493,"residue":2315},[],[],[],{"type":2319,"category":162,"subcategory":2320,"name":2321,"description":2322,"longDescription":2323,"icon":2324,"comingSoon":170,"lifecycle":2325,"tools":2327,"supportedResources":2328},"circleci","ci-cd","CircleCI","Pipelines, workflows, and build insights from CircleCI","Connect CircleCI to let agents inspect pipelines, analyze build failures, and surface workflow trends. Agents can correlate CI signals with your codebase and deployments to speed up debugging.","i-material-icon-theme-circleci",{"connect":493,"browser":20,"headlessConnect":20,"teardown":493,"residue":2326},[],[],[],{"type":2330,"category":162,"subcategory":2331,"name":2332,"description":2333,"longDescription":2334,"icon":2335,"comingSoon":20,"lifecycle":2336,"tools":2338,"supportedResources":2366},"mixpanel","product-analytics","Mixpanel","Product analytics, funnels, and user journeys","Connect Mixpanel to let agents query product analytics, explore funnels, and analyze user journeys. Agents can correlate user behavior with system signals to investigate regressions and understand feature impact.","i-simple-icons-mixpanel",{"connect":252,"browser":20,"headlessConnect":170,"teardown":325,"residue":2337},[],[2339,2342,2345,2348,2351,2354,2357,2360,2363],{"name":2340,"summary":2341},"mixpanelApi","Call any Mixpanel REST endpoint that lacks a dedicated tool",{"name":2343,"summary":2344},"mixpanelSegmentation","Query Mixpanel event volume over time, segmented by a property",{"name":2346,"summary":2347},"mixpanelEvents","Discover Mixpanel event names, properties, and property values",{"name":2349,"summary":2350},"mixpanelFunnels","List Mixpanel funnels or compute a funnel's conversion",{"name":2352,"summary":2353},"mixpanelRetention","Query Mixpanel cohort retention",{"name":2355,"summary":2356},"mixpanelInsights","List Mixpanel saved reports or fetch an Insights report's data",{"name":2358,"summary":2359},"mixpanelAnnotations","List or create Mixpanel chart annotations",{"name":2361,"summary":2362},"mixpanelExportEvents","Sample raw events from Mixpanel",{"name":2364,"summary":2365},"mixpanelLexicon","Read Mixpanel Lexicon schemas (event and property definitions)",[],{"type":2368,"category":162,"subcategory":2331,"name":2369,"description":2370,"longDescription":2371,"icon":2372,"comingSoon":170,"lifecycle":2373,"tools":2375,"supportedResources":2376},"amplitude","Amplitude","Product analytics, funnels, and user behavior","Connect Amplitude to let agents query product analytics, explore funnels, and understand user behavior. Agents can correlate feature usage with system signals to help investigate regressions and growth trends.","i-logos-amplitude-icon",{"connect":493,"browser":20,"headlessConnect":20,"teardown":493,"residue":2374},[],[],[],{"type":2378,"category":162,"subcategory":2331,"name":2379,"description":2380,"longDescription":2381,"icon":2382,"comingSoon":20,"lifecycle":2383,"tools":2386,"supportedResources":2405},"posthog","PostHog","Product analytics, session replays, and feature flags","Connect PostHog to let agents query product analytics, inspect session replays, and check feature flag rollouts. Agents can correlate product data with infrastructure signals to diagnose issues and understand user impact.","i-logos-posthog-icon",{"connect":431,"browser":170,"headlessConnect":20,"teardown":171,"residue":2384},[2385],"PostHog authorized application",[2387,2390,2393,2396,2399,2402],{"name":2388,"summary":2389},"posthogQuery","Query PostHog analytics or discover the event and property vocabulary for a bounded date range",{"name":2391,"summary":2392},"posthogInsights","Read the PostHog insights, dashboards, alerts and notebooks the team watches",{"name":2394,"summary":2395},"posthogChanges","Read PostHog feature flags, experiments, releases, annotations and activity that explain what changed",{"name":2397,"summary":2398},"posthogErrors","Read PostHog error-tracking issues, their events, stack frames and spike history",{"name":2400,"summary":2401},"posthogReplays","Read PostHog session recordings and playlists to understand what users saw",{"name":2403,"summary":2404},"posthogApi","Call an allow-listed PostHog GET endpoint that no dedicated PostHog tool owns",[],{"type":2407,"category":162,"subcategory":2408,"name":2409,"description":2410,"longDescription":2411,"icon":2412,"comingSoon":20,"lifecycle":2413,"tools":2415,"supportedResources":2416,"marketing":2417},"devin","code-agent","Devin","Delegate autofix implementation to Devin cloud agents","Connect your Devin organization to delegate autofix implementation to Devin cloud agents. Polylane investigates and proposes fixes; Devin opens the pull request on your GitHub. Bring your own Devin API key.","DevinLogo",{"connect":252,"browser":20,"headlessConnect":170,"teardown":325,"residue":2414},[],[],[],{"whatPolylaneDoes":2418,"howItWorks":2428},[2419,2422,2425],{"title":2420,"body":2421},"Polylane investigates, Devin implements","The investigation ends with a root cause and an evidence trail; Devin takes the handoff and opens the pull request on your GitHub.",{"title":2423,"body":2424},"PRs that link back","Every pull request links back to the investigation that produced it, so the reviewer sees the evidence, not just the diff.",{"title":2426,"body":2427},"Your key, your account","Bring your own Devin API key. Polylane routes the fix through the agent your team already trusts.",[2429,2431,2434],{"title":310,"body":2430},"Paste your Devin API key. It's encrypted before it's stored.",{"title":2432,"body":2433},"Pick your executor","Choose Devin as the autofix executor for the workspace.",{"title":2435,"body":2436},"Review the PR","Devin implements the fix and opens the pull request; your review and CI gate the merge.",{"type":2438,"category":162,"subcategory":2408,"name":2439,"description":2440,"longDescription":2441,"icon":2442,"comingSoon":20,"lifecycle":2443,"tools":2445,"supportedResources":2446,"marketing":2447},"cursor","Cursor","Delegate autofix implementation to Cursor cloud agents","Connect your Cursor account to delegate autofix implementation to Cursor cloud agents. Polylane investigates and proposes fixes; Cursor opens the pull request on your GitHub. Bring your own Cursor API key.","CursorLogo",{"connect":252,"browser":20,"headlessConnect":170,"teardown":325,"residue":2444},[],[],[],{"whatPolylaneDoes":2448,"howItWorks":2455},[2449,2452,2453],{"title":2450,"body":2451},"Polylane investigates, Cursor implements","The investigation ends with a root cause and an evidence trail; Cursor's cloud agents take the handoff and open the pull request on your GitHub.",{"title":2423,"body":2424},{"title":2426,"body":2454},"Bring your own Cursor API key. Polylane routes the fix through the agent your team already trusts.",[2456,2458,2460],{"title":310,"body":2457},"Paste your Cursor API key. It's encrypted before it's stored.",{"title":2432,"body":2459},"Choose Cursor as the autofix executor for the workspace.",{"title":2435,"body":2461},"Cursor implements the fix and opens the pull request; your review and CI gate the merge.",{"type":2463,"category":162,"subcategory":2408,"name":2464,"description":2465,"longDescription":2466,"icon":2467,"comingSoon":20,"lifecycle":2468,"tools":2470,"supportedResources":2471,"marketing":2472},"factory","Factory","Delegate autofix implementation to Factory droids","Connect your Factory organization to delegate autofix implementation to Factory droids running on managed computers. Polylane investigates and proposes fixes; Factory implements them and pushes the pull request. Bring your own Factory API key.","FactoryLogo",{"connect":252,"browser":20,"headlessConnect":170,"teardown":325,"residue":2469},[],[],[],{"whatPolylaneDoes":2473,"howItWorks":2481},[2474,2477,2479],{"title":2475,"body":2476},"Polylane investigates, Factory implements","The investigation ends with a root cause and an evidence trail; Factory droids take the handoff on managed computers and push the pull request.",{"title":2423,"body":2478},"Every pull request links back to the investigation that produced it, and a PR closed without merging is a tracked outcome, not a mystery.",{"title":2426,"body":2480},"Bring your own Factory API key. Polylane routes the fix through the agent your team already trusts.",[2482,2484,2486],{"title":310,"body":2483},"Paste your Factory API key. It's encrypted before it's stored.",{"title":2432,"body":2485},"Choose Factory as the autofix executor for the workspace.",{"title":2435,"body":2487},"Factory implements the fix and pushes the pull request; your review and CI gate the merge.",{"type":2489,"category":162,"subcategory":2408,"name":2490,"description":2491,"longDescription":2492,"icon":2493,"comingSoon":20,"lifecycle":2494,"tools":2496,"supportedResources":2497,"marketing":2498},"conductor","Conductor","Delegate autofix implementation to Conductor cloud agents","Connect your Conductor account to delegate autofix implementation to coding agents running in Conductor cloud workspaces. Polylane investigates and proposes fixes; Conductor implements them and pushes the pull request. Bring your own Conductor API key.","ConductorLogo",{"connect":252,"browser":20,"headlessConnect":170,"teardown":325,"residue":2495},[],[],[],{"whatPolylaneDoes":2499,"howItWorks":2506},[2500,2503,2504],{"title":2501,"body":2502},"Polylane investigates, Conductor implements","The investigation ends with a root cause and an evidence trail; Conductor agents take the handoff in cloud workspaces and push the pull request.",{"title":2423,"body":2478},{"title":2426,"body":2505},"Bring your own Conductor API key. Polylane routes the fix through the agent your team already trusts.",[2507,2509,2511],{"title":310,"body":2508},"Paste your Conductor API key. It's encrypted before it's stored.",{"title":2432,"body":2510},"Choose Conductor as the autofix executor for the workspace.",{"title":2435,"body":2512},"Conductor implements the fix and pushes the pull request; your review and CI gate the merge.",{"type":2514,"category":162,"subcategory":2408,"name":2515,"description":2516,"longDescription":2517,"icon":2518,"comingSoon":170,"lifecycle":2519,"tools":2521,"supportedResources":2522},"coding_agent","Local coding agent","Map your stack from the coding agent on your machine","Connect the coding agent running on your machine (Claude Code, Cursor, and other MCP-capable agents) as a first-class source. The agent analyzes your repository locally and submits its findings, so your topology reflects the code on your machine alongside your cloud providers.","i-lucide-terminal",{"connect":493,"browser":20,"headlessConnect":20,"teardown":493,"residue":2520},[],[],[],{"type":2524,"category":162,"subcategory":2408,"name":2525,"description":2526,"longDescription":2527,"icon":2528,"comingSoon":170,"lifecycle":2529,"tools":2531,"supportedResources":2532},"amp","Amp","Delegate autofix implementation to Amp agents","Connect your Amp account to delegate autofix implementation to Amp, the coding agent by Sourcegraph. Polylane investigates and proposes fixes; Amp implements them and opens the pull request on your GitHub.","AmpLogo",{"connect":493,"browser":20,"headlessConnect":20,"teardown":493,"residue":2530},[],[],[],{"type":2534,"category":162,"subcategory":2535,"name":2536,"description":2537,"longDescription":2538,"icon":2539,"comingSoon":20,"lifecycle":2540,"tools":2542,"supportedResources":2543,"marketing":2544},"mcp","protocol","MCP Server","Connect any external Model Context Protocol server","Connect your own MCP-compatible server (GitHub MCP, Linear MCP, or any server following the Model Context Protocol). Tools exposed by connected servers become available to the Polylane thread agent automatically.","i-hugeicons:mcp-server",{"connect":252,"browser":20,"headlessConnect":170,"teardown":325,"residue":2541},[],[],[],{"whatPolylaneDoes":2545,"howItWorks":2555},[2546,2549,2552],{"title":2547,"body":2548},"Your tools in the agent's hands","Connect any MCP-compatible server and its tools show up mid-investigation, next to the built-in observability, graph, and code tools.",{"title":2550,"body":2551},"Anything that speaks the protocol","GitHub MCP, Linear MCP, an internal server you wrote last week: if it follows the Model Context Protocol, agents can use it.",{"title":2553,"body":2554},"On the record like everything else","Calls to your MCP tools land in the thread transcript with their results, cited like every other piece of evidence.",[2556,2558,2561],{"title":310,"body":2557},"Point Polylane at your server's URL. OAuth and API-key servers both work.",{"title":2559,"body":2560},"Tools are discovered","The server's tools are enumerated and become available to the thread agent automatically.",{"title":2562,"body":2563},"Agents reach for them","Mid-investigation, your tools sit alongside the built-in ones, and every call is on the record.",{"id":2565,"title":88,"body":2566,"description":2662,"extension":2663,"links":2664,"meta":2665,"navigation":170,"path":89,"seo":2666,"stem":90,"__hash__":2667},"docs_zh_tw\u002Fzh-tw\u002F5.tools\u002F1.index.md",{"type":2567,"value":2568,"toc":2655},"minimark",[2569,2573,2603,2608,2631,2634],[2570,2571,2572],"p",{},"你的程式碼代理可以看到Polylane看到的東西：橫跨每個已連接供應商的遙測資料、拓樸、程式碼與問題。連接後，它不必讓你離開編輯器就能回答像「這個分支所部署的服務在過去一小時內在生產環境出了哪些錯誤？」這類問題。",[2574,2575,2576,2583,2589],"card-group",{},[2577,2578,2580],"card",{"icon":2579,"title":116,"to":117},"i-lucide-puzzle",[2570,2581,2582],{},"Claude Code、Cursor或Codex一次安裝：兩個MCP伺服器、技能，以及你的代理需要的斜線指令。",[2577,2584,2586],{"icon":2585,"title":94,"to":95},"i-lucide-plug",[2570,2587,2588],{},"供任何MCP客戶端使用的單一Model Context Protocol端點。透過瀏覽器登入，或在沒有瀏覽器的地方使用API金鑰。",[2577,2590,2591],{"icon":2518,"title":98,"to":99},[2570,2592,2593,2594,2598,2599,2602],{},"供終端機、指令碼與CI使用的",[2595,2596,2597],"code",{},"polylane","指令。在終端機中輸出文字，管線化時輸出JSON，完整的API則在",[2595,2600,2601],{},"polylane api","背後。",[2604,2605,2607],"h2",{"id":2606},"預設只讀取寫入需經關卡","預設只讀取，寫入需經關卡",[2570,2609,2610,2611,2614,2615,2618,2619,2622,2623,2626,2627,2630],{},"代理工具在MCP伺服器與CLI上預設是唯讀的：遙測查詢、拓樸遍歷與程式碼搜尋不需要額外設定就能運作。在MCP伺服器上，當工作階段以帶有",[2595,2612,2613],{},"agent_tools:write","範圍的憑證送出",[2595,2616,2617],{},"x-polylane-allow-writes: true","標頭時，對供應商資源的寫入才會解鎖；在CLI上，對",[2595,2620,2621],{},"polylane tools run","或",[2595,2624,2625],{},"polylane tools code","傳入",[2595,2628,2629],{},"--write","。安全模型會篩檢每一次寫入，支援確認提示的客戶端會在每一次寫入執行前請你核准。",[2604,2632,2633],{"id":2633},"相關頁面",[2635,2636,2637,2644,2650],"ul",{},[2638,2639,2640,2643],"li",{},[2641,2642,15],"a",{"href":11},"：第一次連接，手動或在你的程式碼代理中完成。",[2638,2645,2646,2649],{},[2641,2647,2648],{"href":136},"API金鑰與OAuth","：範圍、金鑰管理，以及供無瀏覽器環境使用的OAuth客戶端。",[2638,2651,2652,2654],{},[2641,2653,148],{"href":149},"：讓你的代理搜尋並閱讀這些文件。",{"title":2656,"searchDepth":2657,"depth":2658,"links":2659},"",1,2,[2660,2661],{"id":2606,"depth":2658,"text":2607},{"id":2633,"depth":2658,"text":2633},"從你的程式碼代理、終端機或CI詢問生產環境的狀況：一個MCP伺服器、一個CLI，以及一個同時安裝兩者的外掛。","md",null,{},{"title":88,"description":2662},"6WPgYMbHS1L2wFs9nQmoTLXQQW6kOKA2hO73HIHo29U",[2669,2671],{"title":84,"path":85,"stem":86,"description":2670,"children":-1},"代理撰寫的修復以pull request的形式送達你的儲存庫。由你審查與合併；Polylane會提醒你，並清理沒有人碰的東西。",{"title":94,"path":95,"stem":96,"description":2672,"children":-1},"把任何MCP客戶端連接到Polylane，從你的編輯器查詢遙測資料、拓樸、程式碼與問題，只在你選擇加入時才寫入。",[2674,2675,2676,2677,2678,2679,2680,2681,2682,2683,2684,2685,2686,2687,2688,2689,2690],"en","de","es","fr","it","da","pl","ru","uk","ar","nb","pt-br","th","tr","ja","ko","zh-cn",1790660747325]