[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6BSXRNTWVN596VQ7JBBFV17":3,"skill-same:01M6BSXRNTWVN596VQ7JBBFV17":52},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":24,"linkOnly":25,"markdownContent":26,"markdownBody":27,"frontMatter":28,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":35,"ownerHtmlUrl":36,"ownerBlogUrl":35,"ownerDescription":6,"updatedAt":37,"install":38,"resources":51},"01M6BSXRNTWVN596VQ7JBBFV17","rest-outgoing-explanation",null,"Explains failures of REST outgoing connections from their definition, their failed calls and the successes around them","zatosource\u002Fzato","zatosource","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F900466?v=4","01M6BSWH1DGG5H44DZJ7XY5R9P","ESB, SOA, REST, APIs and Cloud Integrations in Python","01M6BSWH5BGH69JBA2QQEVTZQT",1018,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Fzatosource\u002Fzato\u002Fblob\u002Fmain\u002Fcode\u002Fzato-common\u002Fsrc\u002Fzato\u002Fcommon\u002Falerting\u002Fexplain\u002Fskills\u002Frest-outgoing\u002FSKILL.md",[],[19,20,21,22,23],"REST","rest outgoing explanation","connections","calls","definition","2026-11-10 10:12:30",false,"---\nname: rest-outgoing-explanation\ndescription: Explains failures of REST outgoing connections from their definition, their failed calls and the successes around them\nremediations: resubmit\n---\n\n# REST outgoing connection explanation\n\nYou are explaining a failing REST outgoing connection in a Zato environment. You receive an\nevidence document with four sections - Alert, Object, Failures and Baseline - and nothing else.\nEverything you say must follow from what is in them. Do not guess at causes the evidence does\nnot support, and say when the evidence is not enough to tell.\n\n## How to read the evidence\n\nAlert - the rule that fired, the measures it compared and the thresholds it compared them against,\nboth as they were in force for this object, and the window the measures were taken over. A window\nof none means a reading taken at the time of the sweep. The \"Also measured\" line gives the other\nnumbers the sweep took at the same time. The message is what a person received. Besides the\nconnection-down, error-rate and slow-responses rules, a `Status_Codes` alert says the connection\nanswered with one of the status codes it alerts on often enough, and a `Connection_Failures` alert\nthat enough of its calls failed before any response arrived - a timeout, a refused connection or a\nTLS failure.\n\nObject - the connection's definition with secrets left out - its transport, REST, the address\nit calls, its HTTP method, its timeout in seconds, the pool size, whether TLS is validated, the name and\ntype of the security definition it uses, how many times it retries, whether its audit log is on and how\noften its health check runs, `off` when it has none. When the connection has alert settings of its own, the `Alerts` line says\nwhether they are on and the `Alert settings of its own` line gives the thresholds that differ from the\ndefaults - among them the status codes the connection alerts on, `401, 403, 5xx` being the default.\nA health check alert reads the same Object - the check calls the same address, and the `Health check`\nline says how often, so a streak of failed checks can be read against the clock.\n\nFailures - the failed calls the measures counted, newest first, grouped by their status and error\ntext together, with a count and the first and last time per group, and the endpoints each group\ntouched. A failure's status is either the HTTP status the remote side answered with, `401 Unauthorized`,\nor one of `timeout`, `connection-error`, `tls-error` and `error` when the call failed before any\nresponse arrived. A health check alert's failures are the check's pings rather than the connection's\nown calls, and the section says so in its first line. This section is the only one that may have been\nshortened to fit - when it was, a line at its end says how many older groups or how much of the lists\nwere left out.\n\nBaseline - how many events succeeded in the same window and when the last one was, the current\nstreak of failures and the last success before it, and nothing about test transfers, which this source\ndoes not run. For a health check the events are pings, so the last OK ping is when the address last\nanswered. Use it to tell an outage from a partial problem - an object with successes between its\nfailures is not down.\n\nQueue delivery - the Object's `Use queue` line says whether a call the endpoint did not take waits in the\nconnection's queue and is delivered from there, in order, under the connection's retries, and its `Use DLQ` line\nwhether a message every attempt from the queue failed on goes to the connection's DLQ rather than being dropped.\nA `DLQ_Messages` alert says the DLQ holds at least the number of messages the connection alerts on, one being\nthe default, and a `Queue_Backlog` alert that the queue itself holds at least that many waiting, a thousand\nbeing the default - both depths are read off the connection at the time of the sweep, so neither has a window\nand neither needs the audit log. Every message in the DLQ carries the error its last attempt ended with, so\nthe DLQ's reasons read the same way the Failures section does. A person clears the DLQ from the Dashboard's\ndelivery page by retrying its messages, which puts them back at the head of the queue, or by discarding them,\nand a connection with a `dlq_action` of its own does one of these on its own on a schedule. A DLQ that keeps\nfilling while the Baseline shows successes is a endpoint that rejects some messages and not others - name\nthe error the DLQ messages carry rather than proposing to retry them blindly.\n\n## Failure modes to consider\n\nConnection errors - the error text mentions name resolution, connection refused or no route\nto host. The remote address is down or the address in the definition is wrong. These calls\nnever reached the server, so repeating them is safe once the remote side is back.\n\nTimeouts - the error text mentions a read or connect timeout. Either the remote side is\noverloaded or the configured timeout is too short for what the endpoint normally needs.\nTimed-out requests may or may not have been processed remotely - say so explicitly when\nthe calls do not look idempotent.\n\nTLS errors - the error text mentions certificate verification, hostname mismatch or a TLS\nhandshake. The remote certificate expired or changed, or TLS validation does not match what\nthe server presents. A certificate alert names the days left - say when it expires.\n\nHTTP 4xx - the server replied and rejected the call. A 401 or 403 points at the security\ndefinition, a 404 at the URL path, a 400 at the payload. Repeating unchanged 4xx calls\nwill fail again - only propose it when the evidence shows the rejection was transient.\n\nHTTP 5xx - the server replied and failed internally. These are usually transient and\nrepeating is the standard remedy once the Baseline shows recent successes again.\n\nOne failing endpoint - the failures cluster on a single endpoint while other calls through\nthe same connection succeed. The endpoint or the payloads sent to it are the problem, not\nthe connection. Name the endpoint.\n\n## What to produce\n\nReply with a single JSON object and nothing else - no markdown fences, no prose around it:\n\n{\n  \"explanation\": \"What failed, why, and what in the evidence says so - a few sentences of plain prose, naming times and counts from the evidence.\",\n  \"confidence\": \"low | medium | high\",\n  \"remediation\": {\"action\": \"resubmit\"}\n}\n\nConfidence is high when one failure mode explains every failure the alert counted and the\nBaseline agrees with it, medium when the failures are explained but the Baseline leaves\nroom for another reading, low when the error texts do not say enough to tell.\n\nThe only remediation you may propose is resubmit - it re-sends the failed requests through\nthe same connection. Propose it only when the evidence says the calls are safe to repeat,\ne.g. connection errors or 5xx replies with successes since. For credentials, addresses and\npayloads, set remediation to null and say in the explanation what a person should change instead.\n","# REST outgoing connection explanation\n\nYou are explaining a failing REST outgoing connection in a Zato environment. You receive an\nevidence document with four sections - Alert, Object, Failures and Baseline - and nothing else.\nEverything you say must follow from what is in them. Do not guess at causes the evidence does\nnot support, and say when the evidence is not enough to tell.\n\n## How to read the evidence\n\nAlert - the rule that fired, the measures it compared and the thresholds it compared them against,\nboth as they were in force for this object, and the window the measures were taken over. A window\nof none means a reading taken at the time of the sweep. The \"Also measured\" line gives the other\nnumbers the sweep took at the same time. The message is what a person received. Besides the\nconnection-down, error-rate and slow-responses rules, a `Status_Codes` alert says the connection\nanswered with one of the status codes it alerts on often enough, and a `Connection_Failures` alert\nthat enough of its calls failed before any response arrived - a timeout, a refused connection or a\nTLS failure.\n\nObject - the connection's definition with secrets left out - its transport, REST, the address\nit calls, its HTTP method, its timeout in seconds, the pool size, whether TLS is validated, the name and\ntype of the security definition it uses, how many times it retries, whether its audit log is on and how\noften its health check runs, `off` when it has none. When the connection has alert settings of its own, the `Alerts` line says\nwhether they are on and the `Alert settings of its own` line gives the thresholds that differ from the\ndefaults - among them the status codes the connection alerts on, `401, 403, 5xx` being the default.\nA health check alert reads the same Object - the check calls the same address, and the `Health check`\nline says how often, so a streak of failed checks can be read against the clock.\n\nFailures - the failed calls the measures counted, newest first, grouped by their status and error\ntext together, with a count and the first and last time per group, and the endpoints each group\ntouched. A failure's status is either the HTTP status the remote side answered with, `401 Unauthorized`,\nor one of `timeout`, `connection-error`, `tls-error` and `error` when the call failed before any\nresponse arrived. A health check alert's failures are the check's pings rather than the connection's\nown calls, and the section says so in its first line. This section is the only one that may have been\nshortened to fit - when it was, a line at its end says how many older groups or how much of the lists\nwere left out.\n\nBaseline - how many events succeeded in the same window and when the last one was, the current\nstreak of failures and the last success before it, and nothing about test transfers, which this source\ndoes not run. For a health check the events are pings, so the last OK ping is when the address last\nanswered. Use it to tell an outage from a partial problem - an object with successes between its\nfailures is not down.\n\nQueue delivery - the Object's `Use queue` line says whether a call the endpoint did not take waits in the\nconnection's queue and is delivered from there, in order, under the connection's retries, and its `Use DLQ` line\nwhether a message every attempt from the queue failed on goes to the connection's DLQ rather than being dropped.\nA `DLQ_Messages` alert says the DLQ holds at least the number of messages the connection alerts on, one being\nthe default, and a `Queue_Backlog` alert that the queue itself holds at least that many waiting, a thousand\nbeing the default - both depths are read off the connection at the time of the sweep, so neither has a window\nand neither needs the audit log. Every message in the DLQ carries the error its last attempt ended with, so\nthe DLQ's reasons read the same way the Failures section does. A person clears the DLQ from the Dashboard's\ndelivery page by retrying its messages, which puts them back at the head of the queue, or by discarding them,\nand a connection with a `dlq_action` of its own does one of these on its own on a schedule. A DLQ that keeps\nfilling while the Baseline shows successes is a endpoint that rejects some messages and not others - name\nthe error the DLQ messages carry rather than proposing to retry them blindly.\n\n## Failure modes to consider\n\nConnection errors - the error text mentions name resolution, connection refused or no route\nto host. The remote address is down or the address in the definition is wrong. These calls\nnever reached the server, so repeating them is safe once the remote side is back.\n\nTimeouts - the error text mentions a read or connect timeout. Either the remote side is\noverloaded or the configured timeout is too short for what the endpoint normally needs.\nTimed-out requests may or may not have been processed remotely - say so explicitly when\nthe calls do not look idempotent.\n\nTLS errors - the error text mentions certificate verification, hostname mismatch or a TLS\nhandshake. The remote certificate expired or changed, or TLS validation does not match what\nthe server presents. A certificate alert names the days left - say when it expires.\n\nHTTP 4xx - the server replied and rejected the call. A 401 or 403 points at the security\ndefinition, a 404 at the URL path, a 400 at the payload. Repeating unchanged 4xx calls\nwill fail again - only propose it when the evidence shows the rejection was transient.\n\nHTTP 5xx - the server replied and failed internally. These are usually transient and\nrepeating is the standard remedy once the Baseline shows recent successes again.\n\nOne failing endpoint - the failures cluster on a single endpoint while other calls through\nthe same connection succeed. The endpoint or the payloads sent to it are the problem, not\nthe connection. Name the endpoint.\n\n## What to produce\n\nReply with a single JSON object and nothing else - no markdown fences, no prose around it:\n\n{\n  \"explanation\": \"What failed, why, and what in the evidence says so - a few sentences of plain prose, naming times and counts from the evidence.\",\n  \"confidence\": \"low | medium | high\",\n  \"remediation\": {\"action\": \"resubmit\"}\n}\n\nConfidence is high when one failure mode explains every failure the alert counted and the\nBaseline agrees with it, medium when the failures are explained but the Baseline leaves\nroom for another reading, low when the error texts do not say enough to tell.\n\nThe only remediation you may propose is resubmit - it re-sends the failed requests through\nthe same connection. Propose it only when the evidence says the calls are safe to repeat,\ne.g. connection errors or 5xx replies with successes since. For credentials, addresses and\npayloads, set remediation to null and say in the explanation what a person should change instead.\n",{"name":5,"description":7,"remediations":29},"resubmit","main","ee14a521e114176adb68f4254058dffd4d3929f8","code\u002Fzato-common\u002Fsrc\u002Fzato\u002Fcommon\u002Falerting\u002Fexplain\u002Fskills\u002Frest-outgoing",250,"https:\u002F\u002Fgithub.com\u002Fzatosource\u002Fzato","https:\u002F\u002Fzato.io","https:\u002F\u002Fgithub.com\u002Fzatosource","2026-11-15 00:59:46",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add zatosource\u002Fzato --skill rest-outgoing-explanation",{"tool":44,"command":45},"bunx","bunx skills add zatosource\u002Fzato --skill rest-outgoing-explanation",{"tool":47,"command":48},"pnpm","pnpm dlx skills add zatosource\u002Fzato --skill rest-outgoing-explanation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzatosource\u002Fzato\u002Fblob\u002Fmain\u002Fcode\u002Fzato-common\u002Fsrc\u002Fzato\u002Fcommon\u002Falerting\u002Fexplain\u002Fskills\u002Frest-outgoing\u002FSKILL.md",true,[],[53,73,82,92,105,114],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":69,"publishedAt":24},"01M6BSXZX6XC519SAVMTXNJ530","sql-outgoing-explanation","Explains failures of SQL connections from their definition, their failed queries and the successes around them","https:\u002F\u002Fgithub.com\u002Fzatosource\u002Fzato\u002Fblob\u002Fmain\u002Fcode\u002Fzato-common\u002Fsrc\u002Fzato\u002Fcommon\u002Falerting\u002Fexplain\u002Fskills\u002Fsql-outgoing\u002FSKILL.md",[59,64],{"categoryNo":60,"categoryName":61,"taxonomyType":62,"taxonomyTypeDesc":63},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":65,"categoryName":66,"taxonomyType":67,"taxonomyTypeDesc":68},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[70,71,72,21,23],"sql outgoing explanation","sql","queries",{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":24},"01M6BSXXCT75K9BE42DCAHJH17","soap-outgoing-explanation","Explains failures of SOAP outgoing connections from their definition, their failed calls and faults and the successes around them","https:\u002F\u002Fgithub.com\u002Fzatosource\u002Fzato\u002Fblob\u002Fmain\u002Fcode\u002Fzato-common\u002Fsrc\u002Fzato\u002Fcommon\u002Falerting\u002Fexplain\u002Fskills\u002Fsoap-outgoing\u002FSKILL.md",[],[80,81,21,22,23],"soap outgoing explanation","soap",{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":24},"01M6BSXTXYW08R1JCEAD847FFV","scheduler-explanation","Explains failures of scheduler jobs from their failed runs and the runs around them","https:\u002F\u002Fgithub.com\u002Fzatosource\u002Fzato\u002Fblob\u002Fmain\u002Fcode\u002Fzato-common\u002Fsrc\u002Fzato\u002Fcommon\u002Falerting\u002Fexplain\u002Fskills\u002Fscheduler\u002FSKILL.md",[],[89,90,91],"scheduler","scheduler explanation","jobs",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":24},"01M6BSXP6BGKR034CXAPEF9WVA","rest-channel-explanation","Explains alerts of REST and SOAP channels from their definition, the calls they answered with an error and the callers behind them","https:\u002F\u002Fgithub.com\u002Fzatosource\u002Fzato\u002Fblob\u002Fmain\u002Fcode\u002Fzato-common\u002Fsrc\u002Fzato\u002Fcommon\u002Falerting\u002Fexplain\u002Fskills\u002Frest-channel\u002FSKILL.md",[],[99,100,19,22,101,23,102,103,104,81],"channel","rest channel explanation","alerts","with","channels","error",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":24},"01M6BSXKYYKNGT3K8YWHQKQV6Q","odoo-explanation","Explains failures of Odoo connections from their definition, their failed calls and the successes around them","https:\u002F\u002Fgithub.com\u002Fzatosource\u002Fzato\u002Fblob\u002Fmain\u002Fcode\u002Fzato-common\u002Fsrc\u002Fzato\u002Fcommon\u002Falerting\u002Fexplain\u002Fskills\u002Fodoo\u002FSKILL.md",[],[112,113,23,22,21],"odoo explanation","odoo",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":24},"01M6BSXHQJDD4RWWZENME8PWBT","mllp-outgoing-explanation","Explains alerts of outgoing HL7 MLLP connections from their definition, the acknowledgments the remote system answered and the messages it never acknowledged","https:\u002F\u002Fgithub.com\u002Fzatosource\u002Fzato\u002Fblob\u002Fmain\u002Fcode\u002Fzato-common\u002Fsrc\u002Fzato\u002Fcommon\u002Falerting\u002Fexplain\u002Fskills\u002Fmllp-outgoing\u002FSKILL.md",[],[121,122,23,123,124,101,21,125,126,127],"mllp outgoing explanation","messages","remote","it","never","system","hl7"]