Instana Action History API
The Action History API from Instana — 2 operation(s) for action history.
OpenAPI Specification
openapi: 3.0.1
info:
contact:
email: support@instana.com
name: © Instana
url: http://instana.com
termsOfService: https://www.instana.com/terms-of-use/
title: Instana REST API documentation Action History API
version: 1.307.1417
x-ibm-ahub-try: true
x-logo:
altText: instana logo
backgroundColor: '#FAFBFC'
url: header-logo.svg
description: "Searching for answers and best pratices? Check our [IBM Instana Community](https://community.ibm.com/community/user/aiops/communities/community-home?CommunityKey=58f324a3-3104-41be-9510-5b7c413cc48f).\n\n<div style=\"background-color:#e6f0ff; padding: 12px; border-left: 6px solid #0052cc; font-size: 14px; display: flex; align-items: center;\">\n <img src=\"https://img.icons8.com/ios-filled/50/0052cc/info.png\" width=\"18\" height=\"18\" style=\"margin-right: 8px;\" alt=\"info icon\"/>\n <span>\n <b>Our API documentation is moving to</b> \n <a href=\"https://developer.ibm.com/apis/catalog/instana--instana-rest-api/Introduction\" target=\"_blank\">API Hub</a>\n\t — please update your bookmarks now, as the current site will be deprecated after Release-306.\n </span>\n</div>\n\n## Overview\nThe Instana REST API provides programmatic access to the Instana platform. It can be used to retrieve data available through the Instana UI Dashboard -- metrics, events, traces, etc -- and also to automate configuration tasks such as user management.\n\n### Navigating the API documentation\nThe API endpoints are grouped by product area and functionality. This generally maps to how our UI Dashboard is organized, hopefully making it easier to locate which endpoints you'd use to fetch the data you see visualized in our UI. The [UI sections](https://www.ibm.com/docs/en/instana-observability/current?topic=working-user-interface#navigation-menu) include:\n- Websites & Mobile Apps\n- Applications\n- Infrastructure\n- Synthetic Monitoring\n- Events\n- Automation\n- Service Levels\n- Settings\n- etc\n\n### Rate Limiting\nA rate limit is applied to API usage. Up to 5,000 calls per hour can be made. How many remaining calls can be made and when this call limit resets, can inspected via three headers that are part of the responses of the API server.\n\n- **X-RateLimit-Limit:** Shows the maximum number of calls that may be executed per hour.\n- **X-RateLimit-Remaining:** How many calls may still be executed within the current hour.\n- **X-RateLimit-Reset:** Time when the remaining calls will be reset to the limit. For compatibility reasons with other rate limited APIs, this date is not the date in milliseconds, but instead in seconds since 1970-01-01T00:00:00+00:00.\n\n### Further Reading\nWe provide additional documentation for our REST API in our [product documentation](https://www.ibm.com/docs/en/instana-observability/current?topic=apis-web-rest-api). Here you'll also find some common queries for retrieving data and configuring Instana.\n\n## Getting Started with the REST API\n\n### API base URL\nThe base URL for an specific instance of Instana can be determined using the tenant and unit information.\n- `base`: This is the base URL of a tenant unit, e.g. `https://test-example.instana.io`. This is the same URL that is used to access the Instana user interface.\n- `apiToken`: Requests against the Instana API require valid API tokens. An initial API token can be generated via the Instana user interface. Any additional API tokens can be generated via the API itself.\n\n### Curl Example\nHere is an Example to use the REST API with Curl. First lets get all the available metrics with possible aggregations with a GET call.\n\n```bash\ncurl --request GET \\\n --url https://test-instana.instana.io/api/application-monitoring/catalog/metrics \\\n --header 'authorization: apiToken xxxxxxxxxxxxxxxx'\n```\n\nNext we can get every call grouped by the endpoint name that has an error count greater then zero. As a metric we could get the mean error rate for example.\n\n```bash\ncurl --request POST \\\n --url https://test-instana.instana.io/api/application-monitoring/analyze/call-groups \\\n --header 'authorization: apiToken xxxxxxxxxxxxxxxx' \\\n --header 'content-type: application/json' \\\n --data '{\n \"group\":{\n \"groupbyTag\":\"endpoint.name\"\n },\n \"tagFilters\":[\n \t{\n \t\t\"name\":\"call.error.count\",\n \t\t\"value\":\"0\",\n \t\t\"operator\":\"GREATER_THAN\"\n \t}\n ],\n \"metrics\":[\n \t{\n \t\t\"metric\":\"errors\",\n \t\t\"aggregation\":\"MEAN\"\n \t}\n ]\n }'\n```\n\n### Generating REST API clients\n\nThe API is specified using the [OpenAPI v3](https://github.com/OAI/OpenAPI-Specification) (previously known as Swagger) format.\nYou can download the current specification at our [GitHub API documentation](https://instana.github.io/openapi/openapi.yaml).\n\nOpenAPI tries to solve the issue of ever-evolving APIs and clients lagging behind. Please make sure that you always use the latest version of the generator, as a number of improvements are regularly made.\nTo generate a client library for your language, you can use the [OpenAPI client generators](https://github.com/OpenAPITools/openapi-generator).\n\n#### Go\nFor example, to generate a client library for Go to interact with our backend, you can use the following script; mind replacing the values of the `UNIT_NAME` and `TENANT_NAME` environment variables using those for your tenant unit:\n\n```bash\n#!/bin/bash\n\n### This script assumes you have the `java` and `wget` commands on the path\n\nexport UNIT_NAME='myunit' # for example: prod\nexport TENANT_NAME='mytenant' # for example: awesomecompany\n\n//Download the generator to your current working directory:\nwget https://repo1.maven.org/maven2/org/openapitools/openapi-generator-cli/4.3.1/openapi-generator-cli-4.3.1.jar -O openapi-generator-cli.jar --server-variables \"tenant=${TENANT_NAME},unit=${UNIT_NAME}\"\n\n//generate a client library that you can vendor into your repository\njava -jar openapi-generator-cli.jar generate -i https://instana.github.io/openapi/openapi.yaml -g go \\\n -o pkg/instana/openapi \\\n --skip-validate-spec\n\n//(optional) format the Go code according to the Go code standard\ngofmt -s -w pkg/instana/openapi\n```\n\nThe generated clients contain comprehensive READMEs, and you can start right away using the client from the example above:\n\n```go\nimport instana \"./pkg/instana/openapi\"\n\n// readTags will read all available application monitoring tags along with their type and category\nfunc readTags() {\n\tconfiguration := instana.NewConfiguration()\n\tconfiguration.Host = \"tenant-unit.instana.io\"\n\tconfiguration.BasePath = \"https://tenant-unit.instana.io\"\n\n\tclient := instana.NewAPIClient(configuration)\n\tauth := context.WithValue(context.Background(), instana.ContextAPIKey, instana.APIKey{\n\t\tKey: apiKey,\n\t\tPrefix: \"apiToken\",\n\t})\n\n\ttags, _, err := client.ApplicationCatalogApi.GetApplicationTagCatalog(auth)\n\tif err != nil {\n\t\tfmt.Fatalf(\"Error calling the API, aborting.\")\n\t}\n\n\tfor _, tag := range tags {\n\t\tfmt.Printf(\"%s (%s): %s\\n\", tag.Category, tag.Type, tag.Name)\n\t}\n}\n```\n\n#### Java\nFollow the instructions provided in the official documentation from [OpenAPI Tools](https://github.com/OpenAPITools) to download the [openapi-generator-cli.jar](https://github.com/OpenAPITools/openapi-generator?tab=readme-ov-file#13---download-jar).\n\nDepending on your environment, use one of the following java http client implementations which will create a valid client for our OpenAPI specification:\n```\n//Nativ Java HTTP Client\njava -jar openapi-generator-cli.jar generate -i https://instana.github.io/openapi/openapi.yaml -g java -o pkg/instana/openapi --skip-validate-spec -p dateLibrary=java8 --library native\n\n//Spring WebClient\njava -jar openapi-generator-cli.jar generate -i https://instana.github.io/openapi/openapi.yaml -g java -o pkg/instana/openapi --skip-validate-spec -p dateLibrary=java8,hideGenerationTimestamp=true --library webclient\n\n//Spring RestTemplate\njava -jar openapi-generator-cli.jar generate -i https://instana.github.io/openapi/openapi.yaml -g java -o pkg/instana/openapi --skip-validate-spec -p dateLibrary=java8,hideGenerationTimestamp=true --library resttemplate\n\n```\n"
servers:
- description: Instana Backend
url: https://{unit}-{tenant}.instana.io
variables:
tenant:
default: tenant
description: Customer tenant unit
unit:
default: unit
description: Customer tenant name
- description: Instana Self-Hosted Backend
url: https://{domain}
variables:
domain:
default: example.com
description: Customer Self-Hosted domain
tags:
- name: Action History
paths:
/api/automation/actioninstances:
delete:
description: Deletes the automation action run results from the action run history. The results to delete is filtered by the filter values given in the query parameters. The automation action run result will be deleted only if the action run result was created within the timeframe specified in the `from` and `to` query parameters. This call requires `Deletion of automation action history` permission and, `from` and `to` query parameters.
operationId: deleteActionInstances
parameters:
- description: From date filter in milliseconds (13-digit) to look up the action run results to delete
example: 1706713140000
in: query
name: from
required: true
schema:
type: integer
format: int64
- description: To date filter in milliseconds (13-digit) to look up the action run results to delete
example: 1706713140000
in: query
name: to
required: true
schema:
type: integer
format: int64
- description: Target snapshot ID to look up the action run results to delete
example: aCtEoR6NSPqG61QkIkwwCw
in: query
name: targetSnapshotId
schema:
type: string
- description: Event ID filter to look up the action run results to delete
example: bCtEoR6NSPqG61QkIkwwCw
in: query
name: eventId
schema:
type: string
- description: Event specification ID filter to look up the action run results to delete
example: 1706713140000
in: query
name: eventSpecificationId
schema:
type: string
- description: Text in action run result name, description and event name to filter the action run results to delete
example: 1706713140000
in: query
name: search
schema:
type: string
- description: Action type filter to look up the action run results to delete
example: One or more of the following types HTTP, SCRIPT, ANSIBLE, GITHUB, GITLAB, JIRA
in: query
name: types
schema:
type: array
items:
type: string
- description: Action status filter to look up the action run results to delete
example: One or more of the following status SUBMITTED, IN_PROGRESS, SUCCESS, FAILED, TIMEOUT
in: query
name: actionStatuses
schema:
type: array
items:
type: string
- description: List of action IDs to filter the action run results to delete
example: cCtEoR6NSPqG61QkIkwwCw
in: query
name: actionIds
schema:
type: array
items:
type: string
- description: Policy ID filter to look up the action run results to delete
example: bCtEoR6NSPqG61QkIkwwCw
in: query
name: policyId
schema:
type: string
responses:
'200':
content:
application/json:
example:
deletedDocumentsCount: '2'
description: Automation action run results are deleted.
'400':
description: '`from` date or `to` date query parameter is missing.'
'403':
description: Automation feature is not enabled or Insufficient permissions.
'500':
description: The request do not contain a valid user or API Token.
security:
- ApiKeyAuth:
- canDeleteAutomationActionHistory
summary: Delete automation action run results.
tags:
- Action History
x-ibm-ahub-byok: true
get:
description: Get the details of automation action run results from action run history. The results are filtered by the filters in the query parameters. The automation action run result will be fetched only if the action run results were created within the timeframe specified by the `windowSize` and `to` query parameters. The `windowSize` parameter is used to compute the from date (`from = to - windowSize`) of the timeframe. The default value for `windowSize` is 10 minutes and the default value for `to` is current system time. When using personal access tokens, the user must have at least `Viewer` access for Automation and the automation action run results returned are also filtered based on the access set in `Limited access` permission settings. This API returns paginated result as specified in query parameters `page` and `pageSize`. The response contains list of automation action run results whose contents corresponds to the `page` query parameter and whose size corresponds to the `pageSize` query parameter.
operationId: getActionInstances
parameters:
- description: Window size filter in milliseconds (to compute the from date) to get the action run result details
example: 10000
in: query
name: windowSize
schema:
type: integer
format: int64
- description: To date filter in milliseconds (13-digit) to get the action run result details
example: 1706713140000
in: query
name: to
schema:
type: integer
format: int64
- description: Page to fetch -- used for paging the action run result records
example: 2
in: query
name: page
schema:
type: integer
format: int32
- description: Number of records to return in each page -- used for paging the action run result records
example: 50
in: query
name: pageSize
schema:
type: integer
format: int32
- description: Target snapshot ID filter to get the action run result details
example: nCtEoR6NSPqG61QkIkwwCw
in: query
name: targetSnapshotId
schema:
type: string
- description: Event ID filter to get the action run result details
example: nCtEoR6NSPqG61QkIkwwCw
in: query
name: eventId
schema:
type: string
- description: Event specification ID filter to get the action run result details
example: 1706713140000
in: query
name: eventSpecificationId
schema:
type: string
- description: Text in action run result name, description and event name filter to get the action run result details
example: 1706713140000
in: query
name: search
schema:
type: string
- description: Action type filter to get the action run result details
example: One or more of the following types HTTP, SCRIPT, ANSIBLE, GITHUB, GITLAB, JIRA
in: query
name: types
schema:
type: array
items:
type: string
- description: Action status filter to get the action run result details
example: One or more of the following status SUBMITTED, IN_PROGRESS, SUCCESS, FAILED, TIMEOUT
in: query
name: actionStatuses
schema:
type: array
items:
type: string
- description: Action IDs filter to get the action run result details for only these actions
in: query
name: actionIds
schema:
type: array
items:
type: string
- description: Policy ID filter to get the action run result details
example: nCtEoR6NSPqG61QkIkwwCw
in: query
name: policyId
schema:
type: string
- description: Action run result column to order the result set.
example: Name of the action run result column. Default is action run result start date.
in: query
name: orderBy
schema:
type: string
- description: Sort order direction.
example: asc or desc
in: query
name: orderDirection
schema:
type: string
responses:
'200':
content:
application/json:
example:
items:
- actionInstanceId: fqiH0HOgR1-4Ygoy5EDycw
actionId: d473c1b0-0740-4d08-95fe-31e5d0a9faff
actionName: Hello World
type: SCRIPT
status: SUCCESS
createdDate: 1710162882369
startDate: 1710162882653
endDate: 1710162882826
eventId: M3wuBxuaSDyecZJ7ICioiw
eventSpecificationId: en0FW6XRWu7aRsD4055dbMLAuSU
problemText: Test event
hostSnapshotId: 2nIOVtEW-iPbsEIi89-yDqJHi2g
targetSnapshotId: jfSmhACY-Oa3a8zfjJxvOxJeDSk
metadata: []
page: 1
pageSize: 50
totalHits: 500
schema:
$ref: '#/components/schemas/PaginatedResult'
description: Automation action run result details are returned.
'403':
description: Automation feature is not enabled or Insufficient permissions.
security:
- ApiKeyAuth:
- Default
summary: Get the details of automation action run results from action run history.
tags:
- Action History
x-ibm-ahub-byok: true
post:
description: Submits the automation action for execution on an agent. The automation action to execute and the agent on which to execute the action must be specified as actionId and hostId. For more details on the request payload see the request sample. This call requires `Execution of automation actions` permission.
operationId: addActionInstance
requestBody:
content:
application/json:
example:
hostId: aHostId
actionId: d473c1b0-0740-4d08-95fe-31e5d0a9faff
policyId: 2nIOVtEW-iPbsEIi89-yDqJabc
inputParameters:
- name: name
type: type
value: value
eventId: M3wuBxuaSDyecZJ7ICioiw
async: 'true'
timeout: '600'
schema:
$ref: '#/components/schemas/ActionInstanceRequest'
required: true
responses:
'200':
content:
application/json:
example:
actionInstanceId: fqiH0HOgR1-4Ygoy5EDycw
actionId: d473c1b0-0740-4d08-95fe-31e5d0a9faff
actionName: Hello World
type: SCRIPT
status: SUBMITTED
createdDate: 1710162882369
eventId: M3wuBxuaSDyecZJ7ICioiw
eventSpecificationId: en0FW6XRWu7aRsD4055dbMLAuSU
problemText: Test event
hostSnapshotId: 2nIOVtEW-iPbsEIi89-yDqJHi2g
targetSnapshotId: jfSmhACY-Oa3a8zfjJxvOxJeDSk
inputParameters: []
outputParameters: []
metadata: []
externalSourceType: ''
actorId: 5ee5195fbea6150001758c40
actorName: Stan
actorType: USER
eventEntityType: ''
actionDescription: Simple script action for testing
policyId: 2nIOVtEW-iPbsEIi89-yDqJabc
schema:
$ref: '#/components/schemas/ActionInstance'
description: Automation action submitted for execution on the agent.
'400':
description: The payload in the request body is not valid or the action ID (actionId) in the payload is invalid or the agent host ID (hostId) in the payload is invalid.
'403':
description: Automation feature is not enabled or Insufficient permissions.
security:
- ApiKeyAuth:
- canRunAutomationActions
summary: Run an automation action.
tags:
- Action History
x-ibm-ahub-byok: true
/api/automation/actioninstances/{actionInstanceId}:
delete:
description: Deletes the automation action run result specified in the request path from the action run history. The automation action run result will be deleted only if the action run result was created within the timeframe specified in the `from` and `to` query parameters. To get the automation action run result ID and the created time, you can run `/api/automation/actioninstances` and `/api/automation/actioninstances/<{actionInstanceId}>` REST calls. This call requires `Deletion of automation action history` permission.
operationId: deleteActionInstance
parameters:
- description: Automation action run result ID to delete.
example: nCtEoR6NSPqG61QkIkwwCw
in: path
name: actionInstanceId
required: true
schema:
type: string
- description: From date filter in milliseconds (13-digit) to look up the action run result ID.
example: 1706713140000
in: query
name: from
required: true
schema:
type: integer
format: int64
- description: To date filter in milliseconds (13-digit) to look up the action run result ID.
example: 1706713190000
in: query
name: to
required: true
schema:
type: integer
format: int64
responses:
'200':
content:
application/json:
example:
deletedDocumentsCount: '2'
description: Automation action run result is deleted.
'400':
description: Automation action run result ID is missing in the request path, or `from` date or `to` date is missing in the query parameters.
'403':
description: Automation feature is not enabled or Insufficient permissions.
'500':
description: The request do not contain a valid user or API Token.
security:
- ApiKeyAuth:
- canDeleteAutomationActionHistory
summary: Deletes an automation action run result from the action run history by ID.
tags:
- Action History
x-ibm-ahub-byok: true
get:
description: Get the details of automation action run result specified in the request path from action run history. The automation action run result will be fetched only if the action run result was created within the timeframe specified by the `windowSize` and `to` query parameters. The `windowSize` parameter is used to compute the from date (`from = to - windowSize`) of the timeframe. The default value for `windowSize` is 10 minutes and the default value for `to` is current system time. To get the automation action run result ID and the created time, you can run `/api/automation/actioninstances` REST calls. When using personal access tokens, the user must have at least `Viewer` access for Automation.
operationId: getActionInstance
parameters:
- description: action run result ID to get action run result details
example: nCtEoR6NSPqG61QkIkwwCw
in: path
name: actionInstanceId
required: true
schema:
type: string
- description: Window size in milliseconds. This value is used compute the from date `(from = to - windowSize)` to get the action run result details. The default `windowSize` is set to 10 minutes if this value is not provided.
example: 10000
in: query
name: windowSize
schema:
type: integer
format: int64
- description: To date filter in milliseconds (13-digit) to get the action run result details. The default `to` date is set to `System.currentTimeMillis()` if this value is not provided.
example: 1706713140000
in: query
name: to
schema:
type: integer
format: int64
responses:
'200':
content:
application/json:
example:
actionInstanceId: fqiH0HOgR1-4Ygoy5EDycw
actionId: d473c1b0-0740-4d08-95fe-31e5d0a9faff
actionName: Hello World
type: SCRIPT
status: SUCCESS
returnCode: 0
errorMessage: ''
createdDate: 1710162882369
startDate: 1710162882653
endDate: 1710162882826
eventId: M3wuBxuaSDyecZJ7ICioiw
eventSpecificationId: en0FW6XRWu7aRsD4055dbMLAuSU
problemText: Test event
hostSnapshotId: 2nIOVtEW-iPbsEIi89-yDqJHi2g
inputParameters: []
outputParameters: []
metadata: []
targetSnapshotId: jfSmhACY-Oa3a8zfjJxvOxJeDSk
externalSourceType: ''
actorId: 5ee5195fbea6150001758c40
actorName: Stan
actorType: USER
eventEntityType: ''
actionDescription: Simple script action for testing
policyId: 2nIOVtEW-iPbsEIi89-yDqJabc
output: Hello world!
schema:
$ref: '#/components/schemas/ActionInstance'
description: The automation action run result detail is returned.
'400':
description: Missing automation action run result ID.
'403':
description: Automation feature is not enabled or Insufficient permissions.
security:
- ApiKeyAuth:
- Default
summary: Get the details of an automation action run result by ID from action run history.
tags:
- Action History
x-ibm-ahub-byok: true
components:
schemas:
ActionInstanceMetadataEntry:
type: object
description: List of metadata parameters set to this action run by sensors.
properties:
name:
type: string
description: Metadata name.
value:
type: string
description: Metadata value.
required:
- name
ActionInstanceParameter:
type: object
description: List of input parameters to this action run.
properties:
displayName:
type: string
description: Parameter display name.
name:
type: string
description: Parameter name.
type:
type: string
description: Parameter type. Valid values are `static`, `dynamic` or `vault`
value:
type: string
description: Parameter value.
required:
- displayName
- name
ActionInstanceRequest:
type: object
properties:
actionId:
type: string
description: Action identifier of the action to run.
async:
type: string
description: '`"true"` if the action should be run in asynchronous mode `"false"` otherwise. Default is `"true"`.'
eventId:
type: string
description: Event identifier (incident or issue) associated with the policy.
hostId:
type: string
description: Agent host identifier on which to run the action.
inputParameters:
type: array
description: Action run input parameters.
items:
$ref: '#/components/schemas/ActionInstanceRequestParameters'
policyId:
type: string
description: Policy identifier that associates the action trigger (incident or issue) to the action to run.
timeout:
type: string
description: Action run time out. Default is `30 seconds`.
required:
- actionId
- hostId
ActionInstance:
type: object
properties:
actionDescription:
type: string
description: Action description of the action to run.
actionId:
type: string
description: Action identifier of the action to run.
actionInstanceId:
type: string
description: Action run identifier.
readOnly: true
actionName:
type: string
description: Action name of the action to run.
actionSnapshot:
type: string
description: Snapshot of the action definition.
readOnly: true
actorId:
type: string
description: User identifier, API token or the policy identifier that started the action run.
actorName:
type: string
description: Name of the user, API token or the policy that started the action run.
actorType:
type: string
description: Type of Actor. Valid values are listed in the enum definition.
enum:
- ACTOR_UNKNOWN
- USER
- APITOKEN
- POLICY
createdDate:
type: integer
format: int64
description: Action run created timestamp. The timestamp at which the action run got submitted.
endDate:
type: integer
format: int64
description: Action run end timestamp. The timestamp at which the action run ended on the agent host.
errorMessage:
type: string
description: Error message, if any, of action run on the agent host.
eventEntityType:
type: string
description: Event entity type set in the event that triggered this action run.
eventId:
type: string
description: Event identifier of the event that triggered this action run.
eventSpecificationId:
type: string
description: Event specification identifier of the event that triggered this action run.
externalSourceType:
type: string
description: If the action type is external this field contains the name of the external source.
hostSnapshotId:
type: string
description: Host snapshot identifier of the agent on which the action ran.
inputParameters:
type: array
description: List of input parameters to this action run.
items:
$ref: '#/components/schemas/ActionInstanceParameter'
metadata:
type: array
description: List of metadata parameters set to this action run by sensors.
items:
$ref: '#/components/schemas/ActionInstanceMetadataEntry'
output:
type: string
description: Action run output.
policyId:
type: string
description: Identifier of the policy that triggered this action run.
problemText:
type: string
description: Event problem text of the event that triggered this action run.
returnCode:
type: integer
format: int32
description: Return code of action run on the agent host.
startDate:
type: integer
format: int64
description: Action run start timestamp. The timestamp at which the action run started on the agent host.
status:
type: string
description: Action run status. Valid values are listed in the enum definition.
enum:
- STATUS_UNKNOWN
- SUBMITTED
- IN_PROGRESS
- SUCCESS
- FAILED
- READY
- TIMEOUT
targetSnapshotId:
type: string
description: Action target entity identifier set in the event that triggered this action run. This is the identifier of the entity on which an incident or issue was raised.
type:
type: string
description: Action type. Valid values are listed in the enum definition.
enum:
- SCRIPT
- HTTP
- ANSIBLE
- EXTERNAL
- GITHUB
- GITLAB
- JIRA
- MANUAL
- DOC_LINK
required:
- actionId
- actionName
- type
ActionInstanceRequestParameters:
type: object
description: Action run input parameters.
properties:
name:
type:
# --- truncated at 32 KB (34 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/instana/refs/heads/main/openapi/instana-action-history-api-openapi.yml