--- title: "Fetch investigation results by ID (UUID)" method: GET path: "/issues/{id}/results" tags: ["Issues"] --- # Fetch investigation results by ID (UUID) `GET /issues/{id}/results` Retrieves detailed investigation results including root cause analysis and remediation steps ## Path parameters - `id` string, uuid, required ## Query parameters - `version` integer ## Headers - `Antimetal-Version` string ## Response `200` Investigation results - IssueResultsDto - `sessionUuid` string, nullable, required — Session UUID for live investigation - `rootCause` object, nullable, required — Root cause information - `id` string, required — Root cause identifier - `incidentOverview` string, required — Root cause problem overview - `rootCauseSummary` string, required — Root cause analysis summary - `relevantEvidence` object[], required — Relevant evidence supporting the root cause - `title` string, required — Evidence title - `status` 'relevant' | 'irrelevant' | 'inconclusive', required — Evidence status - `description` string, required — Evidence description - `confidence` 'unknown' | 'unclear' | 'probable' | 'likely' | 'confirmed', required — Evidence confidence level - `artifacts` object[], required — Evidence artifacts with document references - `documentId` string, required — Document identifier for artifact fetching - `title` string, required — Artifact title - `description` string, required — Artifact description - `dataType` string, required — Type of data in this artifact - `irrelevantEvidence` object[], required — Irrelevant evidence ruled out during investigation - `title` string, required — Evidence title - `status` 'relevant' | 'irrelevant' | 'inconclusive', required — Evidence status - `description` string, required — Evidence description - `confidence` 'unknown' | 'unclear' | 'probable' | 'likely' | 'confirmed', required — Evidence confidence level - `artifacts` object[], required — Evidence artifacts with document references - `documentId` string, required — Document identifier for artifact fetching - `title` string, required — Artifact title - `description` string, required — Artifact description - `dataType` string, required — Type of data in this artifact - `causalTree` object, required — Causal tree analysis - `nodes` object[], required - `id` string, required — Unique identifier for this node. - `type` 'validated' | 'needs-context' | 'ruled-out', required — Node type indicating its state in the causal analysis - `title` string, required — Short title of the node - `description` string, required — Detailed description of the node - `expandedContent` string — Optional rich text content in Markdown format providing detailed explanation - `edges` object[], required - `id` string, required — Unique identifier for this edge - `source` string, required — ID of the source node - `target` string, required — ID of the target node - `causalTreeV2` object, required — Causal graph V2 with enriched evidence - `nodes` object[], required - `id` string, required — Unique identifier for this node in the causal graph (causal variable) e.g. db_connection_error or deployment_change. - `title` string, required — Brief display name for the causal variable. Use active verbs to show causal flow. CAUSE nodes: action-focused (e.g., 'Flag Activates Bad Store Routing', 'Deployment Introduces Memory Leak'). MEDIATOR nodes: consequence-focused (e.g., 'Requests Routed to Invalid Endpoint', 'Memory Exhaustion Occurs'). OUTCOME nodes: consequence-focused (e.g., 'Service Errors Exceed Threshold', 'Response Times Degrade Beyond SLA'). Keep under 8 words. - `description` string, required — Succinct explanation (1-2 sentences, ~30 words) describing what the underlying evidence shows and the node's role in the incident. Use technical precision: include service names, error codes, field names, file paths. Use direct factual statements without explanations. Skip discovery details - focus on what happened, not how it was found. Include causal mechanism if relevant. Example: 'Configuration shows paymentFailure flag enabled at 12.5% rate, implementing probabilistic failure injection via Math.random() in charge.js:37.' Let evidence documents contain detailed data. - `confidence` 'unknown' | 'unclear' | 'probable' | 'likely' | 'confirmed', required — Confidence in this node's role in the incident (e.g., how certain we are that this factor accurately represents what happened) - `nodeType` 'outcome' | 'cause' | 'confounder' | 'mediator', required — Role in the causal graph: OUTCOME = the problem you're investigating, CAUSE = what triggered it, CONFOUNDER = external factor affecting multiple variables, MEDIATOR = intermediate step in the causal path - `evidence` object[], required - `documentId` string, required — Unique identifier for the document that contains this evidence (e.g., 'log:datadog:a9c1319258284740a7e5704134d90238', 'trace:gcp:abc123', 'file:github:24192d3b6c1292fd29da76ada910c175') - `title` string, required — Human-readable name for this piece of evidence (e.g., 'Unbounded Cache Growth in recommendation_server.py', 'Deployment memory limit configuration','Deploy Script v2.1') - `description` string, required — Direct factual statement about what the evidence shows and why it's relevant to the causal relationship (e.g., 'Shows 300% CPU spike at 14:23, correlating with error rate increase') - `dataType` string, required — Type of artifact extracted from documentId (log, metric, trace, file, etc.) - `edges` object[], required - `from` string, required — Unique identifier for the source node in the causal graph. - `to` string, required — Unique identifier for the target node in the causal graph. - `confidence` number, required — Edge confidence reflects how certain we are about the causal relationship itself (e.g. how confident we are that the deployment caused the memory leak). - `remediation` object, required — Remediation actions and steps - `actions` object[], required — Available remediation actions - `id` string, required — Action identifier - `uuid` string, required — Action UUID - `title` string, required — Action title - `description` string — Optional action description - `category` 'immediate' | 'root_cause' | 'preventative' — Remediation category: immediate (quick stabilization), root_cause (fixes underlying issue), preventative (prevents recurrence) - `steps` union[], required — Array of remediation steps - union - object - `id` string, required — Step identifier - `title` string, required — Step title - `helpMarkdown` string — Optional help text in markdown - `required` boolean, required — Whether this step is required - `label` string — Optional label for the step - `type` 'info', required — Info step type - `content` string, required — Markdown content to display - object - `id` string, required — Step identifier - `title` string, required — Step title - `helpMarkdown` string — Optional help text in markdown - `required` boolean, required — Whether this step is required - `label` string — Optional label for the step - `type` 'code', required — Code step type - `files` object[], required — Array of code files to modify - … - `activeFilename` string — Currently active/selected filename - object - `id` string, required — Step identifier - `title` string, required — Step title - `helpMarkdown` string — Optional help text in markdown - `required` boolean, required — Whether this step is required - `label` string — Optional label for the step - `type` 'cli', required — CLI step type - `command` string, required — Shell command to execute - `markdownPrompt` string — Markdown prompt describing the suggested steps - `timeline` object[], required — Timeline events - `id` string, required - `type` 'outcome' | 'cause' | 'confounder' | 'mediator', nullable, required - `timestamp` string, date-time, nullable, required - `title` string, required - `description` string, required - `evidence` object[], required - `artifactId` string, nullable, required - `timestamp` string, date-time, nullable, required - `title` string, required - `description` string, required ## Other responses - `400` — Validation error or bad request - `401` — Authentication required - `403` — Insufficient permissions - `404` — Resource not found - `429` — Rate limit exceeded - `500` — Internal server error --- [API](https://skmtc.net/antimetal/apis/antimetal-external-api.md) · [All operations](https://skmtc.net/antimetal/apis/antimetal-external-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/antimetal/antimetal-external-api/versions/0539acd362bf/schema)