instana-client 1.0.0__py3-none-any.whl → 1.0.1__py3-none-any.whl

instana_client/api/service_levels_objective_slo_report_api.py

@@ -3,9 +3,9 @@
 """
     Instana REST API documentation
 
-    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).  ## Overview The 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.  ### Navigating the API documentation The 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: - Websites & Mobile Apps - Applications - Infrastructure - Synthetic Monitoring - Events - Automation - Service Levels - Settings - etc  ### Rate Limiting A 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.  - **X-RateLimit-Limit:** Shows the maximum number of calls that may be executed per hour. - **X-RateLimit-Remaining:** How many calls may still be executed within the current hour. - **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.  ### Further Reading We 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.  ## Getting Started with the REST API  ### API base URL The base URL for an specific instance of Instana can be determined using the tenant and unit information. - `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. - `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.  ### Curl Example Here is an Example to use the REST API with Curl. First lets get all the available metrics with possible aggregations with a GET call.  ```bash curl --request GET \\   --url https://test-instana.instana.io/api/application-monitoring/catalog/metrics \\   --header 'authorization: apiToken xxxxxxxxxxxxxxxx' ```  Next 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.  ```bash curl --request POST \\   --url https://test-instana.instana.io/api/application-monitoring/analyze/call-groups \\   --header 'authorization: apiToken xxxxxxxxxxxxxxxx' \\   --header 'content-type: application/json' \\   --data '{   \"group\":{       \"groupbyTag\":\"endpoint.name\"   },   \"tagFilters\":[    {     \"name\":\"call.error.count\",     \"value\":\"0\",     \"operator\":\"GREATER_THAN\"    }   ],   \"metrics\":[    {     \"metric\":\"errors\",     \"aggregation\":\"MEAN\"    }   ]   }' ```  ### Generating REST API clients  The API is specified using the [OpenAPI v3](https://github.com/OAI/OpenAPI-Specification) (previously known as Swagger) format. You can download the current specification at our [GitHub API documentation](https://instana.github.io/openapi/openapi.yaml).  OpenAPI 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. To generate a client library for your language, you can use the [OpenAPI client generators](https://github.com/OpenAPITools/openapi-generator).  #### Go For 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:  ```bash #!/bin/bash  ### This script assumes you have the `java` and `wget` commands on the path  export UNIT_NAME='myunit' # for example: prod export TENANT_NAME='mytenant' # for example: awesomecompany  //Download the generator to your current working directory: wget 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}\"  //generate a client library that you can vendor into your repository java -jar openapi-generator-cli.jar generate -i https://instana.github.io/openapi/openapi.yaml -g go \\     -o pkg/instana/openapi \\     --skip-validate-spec  //(optional) format the Go code according to the Go code standard gofmt -s -w pkg/instana/openapi ```  The generated clients contain comprehensive READMEs, and you can start right away using the client from the example above:  ```go import instana \"./pkg/instana/openapi\"  // readTags will read all available application monitoring tags along with their type and category func readTags() {  configuration := instana.NewConfiguration()  configuration.Host = \"tenant-unit.instana.io\"  configuration.BasePath = \"https://tenant-unit.instana.io\"   client := instana.NewAPIClient(configuration)  auth := context.WithValue(context.Background(), instana.ContextAPIKey, instana.APIKey{   Key:    apiKey,   Prefix: \"apiToken\",  })   tags, _, err := client.ApplicationCatalogApi.GetApplicationTagCatalog(auth)  if err != nil {   fmt.Fatalf(\"Error calling the API, aborting.\")  }   for _, tag := range tags {   fmt.Printf(\"%s (%s): %s\\n\", tag.Category, tag.Type, tag.Name)  } } ```  #### Java Follow 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).  Depending on your environment, use one of the following java http client implementations which will create a valid client for our OpenAPI specification: ``` //Nativ Java HTTP Client java -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  //Spring WebClient java -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  //Spring RestTemplate java -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  ``` 
+    Documentation for INSTANA REST API
 
-    The version of the OpenAPI document: 1.291.1002
+    The version of the OpenAPI document: 1.306.1368
     Contact: support@instana.com
     Generated by OpenAPI Generator (https://openapi-generator.tech)
 
@@ -46,6 +46,8 @@ class ServiceLevelsObjectiveSLOReportApi:
         slo_id: Annotated[StrictStr, Field(description="Service Levels Objective(SLO) Configuration ID")],
         var_from: Annotated[Optional[StrictStr], Field(description="Starting point for the data retrieval, specified as 13 digit Unix Timestamp milliseconds")] = None,
         to: Annotated[Optional[StrictStr], Field(description="Ending point for the data retrieval, specified as 13 digit Unix Timestamp milliseconds")] = None,
+        exclude_correction_id: Annotated[Optional[List[StrictStr]], Field(description="IDs of Correction Configurations to be Excluded from the result")] = None,
+        include_correction_id: Annotated[Optional[List[StrictStr]], Field(description="IDs of Correction Configurations to be Included in the result")] = None,
         _request_timeout: Union[
             None,
             Annotated[StrictFloat, Field(gt=0)],
@@ -68,6 +70,10 @@ class ServiceLevelsObjectiveSLOReportApi:
         :type var_from: str
         :param to: Ending point for the data retrieval, specified as 13 digit Unix Timestamp milliseconds
         :type to: str
+        :param exclude_correction_id: IDs of Correction Configurations to be Excluded from the result
+        :type exclude_correction_id: List[str]
+        :param include_correction_id: IDs of Correction Configurations to be Included in the result
+        :type include_correction_id: List[str]
         :param _request_timeout: timeout setting for this request. If one
                                  number provided, it will be total request
                                  timeout. It can also be a pair (tuple) of
@@ -94,6 +100,8 @@ class ServiceLevelsObjectiveSLOReportApi:
             slo_id=slo_id,
             var_from=var_from,
             to=to,
+            exclude_correction_id=exclude_correction_id,
+            include_correction_id=include_correction_id,
             _request_auth=_request_auth,
             _content_type=_content_type,
             _headers=_headers,
@@ -121,6 +129,8 @@ class ServiceLevelsObjectiveSLOReportApi:
         slo_id: Annotated[StrictStr, Field(description="Service Levels Objective(SLO) Configuration ID")],
         var_from: Annotated[Optional[StrictStr], Field(description="Starting point for the data retrieval, specified as 13 digit Unix Timestamp milliseconds")] = None,
         to: Annotated[Optional[StrictStr], Field(description="Ending point for the data retrieval, specified as 13 digit Unix Timestamp milliseconds")] = None,
+        exclude_correction_id: Annotated[Optional[List[StrictStr]], Field(description="IDs of Correction Configurations to be Excluded from the result")] = None,
+        include_correction_id: Annotated[Optional[List[StrictStr]], Field(description="IDs of Correction Configurations to be Included in the result")] = None,
         _request_timeout: Union[
             None,
             Annotated[StrictFloat, Field(gt=0)],
@@ -143,6 +153,10 @@ class ServiceLevelsObjectiveSLOReportApi:
         :type var_from: str
         :param to: Ending point for the data retrieval, specified as 13 digit Unix Timestamp milliseconds
         :type to: str
+        :param exclude_correction_id: IDs of Correction Configurations to be Excluded from the result
+        :type exclude_correction_id: List[str]
+        :param include_correction_id: IDs of Correction Configurations to be Included in the result
+        :type include_correction_id: List[str]
         :param _request_timeout: timeout setting for this request. If one
                                  number provided, it will be total request
                                  timeout. It can also be a pair (tuple) of
@@ -169,6 +183,8 @@ class ServiceLevelsObjectiveSLOReportApi:
             slo_id=slo_id,
             var_from=var_from,
             to=to,
+            exclude_correction_id=exclude_correction_id,
+            include_correction_id=include_correction_id,
             _request_auth=_request_auth,
             _content_type=_content_type,
             _headers=_headers,
@@ -196,6 +212,8 @@ class ServiceLevelsObjectiveSLOReportApi:
         slo_id: Annotated[StrictStr, Field(description="Service Levels Objective(SLO) Configuration ID")],
         var_from: Annotated[Optional[StrictStr], Field(description="Starting point for the data retrieval, specified as 13 digit Unix Timestamp milliseconds")] = None,
         to: Annotated[Optional[StrictStr], Field(description="Ending point for the data retrieval, specified as 13 digit Unix Timestamp milliseconds")] = None,
+        exclude_correction_id: Annotated[Optional[List[StrictStr]], Field(description="IDs of Correction Configurations to be Excluded from the result")] = None,
+        include_correction_id: Annotated[Optional[List[StrictStr]], Field(description="IDs of Correction Configurations to be Included in the result")] = None,
         _request_timeout: Union[
             None,
             Annotated[StrictFloat, Field(gt=0)],
@@ -218,6 +236,10 @@ class ServiceLevelsObjectiveSLOReportApi:
         :type var_from: str
         :param to: Ending point for the data retrieval, specified as 13 digit Unix Timestamp milliseconds
         :type to: str
+        :param exclude_correction_id: IDs of Correction Configurations to be Excluded from the result
+        :type exclude_correction_id: List[str]
+        :param include_correction_id: IDs of Correction Configurations to be Included in the result
+        :type include_correction_id: List[str]
         :param _request_timeout: timeout setting for this request. If one
                                  number provided, it will be total request
                                  timeout. It can also be a pair (tuple) of
@@ -244,6 +266,8 @@ class ServiceLevelsObjectiveSLOReportApi:
             slo_id=slo_id,
             var_from=var_from,
             to=to,
+            exclude_correction_id=exclude_correction_id,
+            include_correction_id=include_correction_id,
             _request_auth=_request_auth,
             _content_type=_content_type,
             _headers=_headers,
@@ -266,6 +290,8 @@ class ServiceLevelsObjectiveSLOReportApi:
         slo_id,
         var_from,
         to,
+        exclude_correction_id,
+        include_correction_id,
         _request_auth,
         _content_type,
         _headers,
@@ -275,6 +301,8 @@ class ServiceLevelsObjectiveSLOReportApi:
         _host = None
 
         _collection_formats: Dict[str, str] = {
+            'excludeCorrectionId': 'multi',
+            'includeCorrectionId': 'multi',
         }
 
         _path_params: Dict[str, str] = {}
@@ -298,6 +326,14 @@ class ServiceLevelsObjectiveSLOReportApi:
             
             _query_params.append(('to', to))
             
+        if exclude_correction_id is not None:
+            
+            _query_params.append(('excludeCorrectionId', exclude_correction_id))
+            
+        if include_correction_id is not None:
+            
+            _query_params.append(('includeCorrectionId', include_correction_id))
+            
         # process the header parameters
         # process the form parameters
         # process the body parameter

instana_client/api/session_settings_api.py

@@ -3,9 +3,9 @@
 """
     Instana REST API documentation
 
-    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).  ## Overview The 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.  ### Navigating the API documentation The 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: - Websites & Mobile Apps - Applications - Infrastructure - Synthetic Monitoring - Events - Automation - Service Levels - Settings - etc  ### Rate Limiting A 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.  - **X-RateLimit-Limit:** Shows the maximum number of calls that may be executed per hour. - **X-RateLimit-Remaining:** How many calls may still be executed within the current hour. - **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.  ### Further Reading We 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.  ## Getting Started with the REST API  ### API base URL The base URL for an specific instance of Instana can be determined using the tenant and unit information. - `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. - `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.  ### Curl Example Here is an Example to use the REST API with Curl. First lets get all the available metrics with possible aggregations with a GET call.  ```bash curl --request GET \\   --url https://test-instana.instana.io/api/application-monitoring/catalog/metrics \\   --header 'authorization: apiToken xxxxxxxxxxxxxxxx' ```  Next 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.  ```bash curl --request POST \\   --url https://test-instana.instana.io/api/application-monitoring/analyze/call-groups \\   --header 'authorization: apiToken xxxxxxxxxxxxxxxx' \\   --header 'content-type: application/json' \\   --data '{   \"group\":{       \"groupbyTag\":\"endpoint.name\"   },   \"tagFilters\":[    {     \"name\":\"call.error.count\",     \"value\":\"0\",     \"operator\":\"GREATER_THAN\"    }   ],   \"metrics\":[    {     \"metric\":\"errors\",     \"aggregation\":\"MEAN\"    }   ]   }' ```  ### Generating REST API clients  The API is specified using the [OpenAPI v3](https://github.com/OAI/OpenAPI-Specification) (previously known as Swagger) format. You can download the current specification at our [GitHub API documentation](https://instana.github.io/openapi/openapi.yaml).  OpenAPI 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. To generate a client library for your language, you can use the [OpenAPI client generators](https://github.com/OpenAPITools/openapi-generator).  #### Go For 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:  ```bash #!/bin/bash  ### This script assumes you have the `java` and `wget` commands on the path  export UNIT_NAME='myunit' # for example: prod export TENANT_NAME='mytenant' # for example: awesomecompany  //Download the generator to your current working directory: wget 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}\"  //generate a client library that you can vendor into your repository java -jar openapi-generator-cli.jar generate -i https://instana.github.io/openapi/openapi.yaml -g go \\     -o pkg/instana/openapi \\     --skip-validate-spec  //(optional) format the Go code according to the Go code standard gofmt -s -w pkg/instana/openapi ```  The generated clients contain comprehensive READMEs, and you can start right away using the client from the example above:  ```go import instana \"./pkg/instana/openapi\"  // readTags will read all available application monitoring tags along with their type and category func readTags() {  configuration := instana.NewConfiguration()  configuration.Host = \"tenant-unit.instana.io\"  configuration.BasePath = \"https://tenant-unit.instana.io\"   client := instana.NewAPIClient(configuration)  auth := context.WithValue(context.Background(), instana.ContextAPIKey, instana.APIKey{   Key:    apiKey,   Prefix: \"apiToken\",  })   tags, _, err := client.ApplicationCatalogApi.GetApplicationTagCatalog(auth)  if err != nil {   fmt.Fatalf(\"Error calling the API, aborting.\")  }   for _, tag := range tags {   fmt.Printf(\"%s (%s): %s\\n\", tag.Category, tag.Type, tag.Name)  } } ```  #### Java Follow 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).  Depending on your environment, use one of the following java http client implementations which will create a valid client for our OpenAPI specification: ``` //Nativ Java HTTP Client java -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  //Spring WebClient java -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  //Spring RestTemplate java -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  ``` 
+    Documentation for INSTANA REST API
 
-    The version of the OpenAPI document: 1.291.1002
+    The version of the OpenAPI document: 1.306.1368
     Contact: support@instana.com
     Generated by OpenAPI Generator (https://openapi-generator.tech)
 

instana_client/api/sli_report_api.py

@@ -3,9 +3,9 @@
 """
     Instana REST API documentation
 
-    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).  ## Overview The 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.  ### Navigating the API documentation The 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: - Websites & Mobile Apps - Applications - Infrastructure - Synthetic Monitoring - Events - Automation - Service Levels - Settings - etc  ### Rate Limiting A 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.  - **X-RateLimit-Limit:** Shows the maximum number of calls that may be executed per hour. - **X-RateLimit-Remaining:** How many calls may still be executed within the current hour. - **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.  ### Further Reading We 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.  ## Getting Started with the REST API  ### API base URL The base URL for an specific instance of Instana can be determined using the tenant and unit information. - `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. - `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.  ### Curl Example Here is an Example to use the REST API with Curl. First lets get all the available metrics with possible aggregations with a GET call.  ```bash curl --request GET \\   --url https://test-instana.instana.io/api/application-monitoring/catalog/metrics \\   --header 'authorization: apiToken xxxxxxxxxxxxxxxx' ```  Next 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.  ```bash curl --request POST \\   --url https://test-instana.instana.io/api/application-monitoring/analyze/call-groups \\   --header 'authorization: apiToken xxxxxxxxxxxxxxxx' \\   --header 'content-type: application/json' \\   --data '{   \"group\":{       \"groupbyTag\":\"endpoint.name\"   },   \"tagFilters\":[    {     \"name\":\"call.error.count\",     \"value\":\"0\",     \"operator\":\"GREATER_THAN\"    }   ],   \"metrics\":[    {     \"metric\":\"errors\",     \"aggregation\":\"MEAN\"    }   ]   }' ```  ### Generating REST API clients  The API is specified using the [OpenAPI v3](https://github.com/OAI/OpenAPI-Specification) (previously known as Swagger) format. You can download the current specification at our [GitHub API documentation](https://instana.github.io/openapi/openapi.yaml).  OpenAPI 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. To generate a client library for your language, you can use the [OpenAPI client generators](https://github.com/OpenAPITools/openapi-generator).  #### Go For 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:  ```bash #!/bin/bash  ### This script assumes you have the `java` and `wget` commands on the path  export UNIT_NAME='myunit' # for example: prod export TENANT_NAME='mytenant' # for example: awesomecompany  //Download the generator to your current working directory: wget 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}\"  //generate a client library that you can vendor into your repository java -jar openapi-generator-cli.jar generate -i https://instana.github.io/openapi/openapi.yaml -g go \\     -o pkg/instana/openapi \\     --skip-validate-spec  //(optional) format the Go code according to the Go code standard gofmt -s -w pkg/instana/openapi ```  The generated clients contain comprehensive READMEs, and you can start right away using the client from the example above:  ```go import instana \"./pkg/instana/openapi\"  // readTags will read all available application monitoring tags along with their type and category func readTags() {  configuration := instana.NewConfiguration()  configuration.Host = \"tenant-unit.instana.io\"  configuration.BasePath = \"https://tenant-unit.instana.io\"   client := instana.NewAPIClient(configuration)  auth := context.WithValue(context.Background(), instana.ContextAPIKey, instana.APIKey{   Key:    apiKey,   Prefix: \"apiToken\",  })   tags, _, err := client.ApplicationCatalogApi.GetApplicationTagCatalog(auth)  if err != nil {   fmt.Fatalf(\"Error calling the API, aborting.\")  }   for _, tag := range tags {   fmt.Printf(\"%s (%s): %s\\n\", tag.Category, tag.Type, tag.Name)  } } ```  #### Java Follow 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).  Depending on your environment, use one of the following java http client implementations which will create a valid client for our OpenAPI specification: ``` //Nativ Java HTTP Client java -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  //Spring WebClient java -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  //Spring RestTemplate java -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  ``` 
+    Documentation for INSTANA REST API
 
-    The version of the OpenAPI document: 1.291.1002
+    The version of the OpenAPI document: 1.306.1368
     Contact: support@instana.com
     Generated by OpenAPI Generator (https://openapi-generator.tech)
 

instana_client/api/sli_settings_api.py

@@ -3,9 +3,9 @@
 """
     Instana REST API documentation
 
-    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).  ## Overview The 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.  ### Navigating the API documentation The 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: - Websites & Mobile Apps - Applications - Infrastructure - Synthetic Monitoring - Events - Automation - Service Levels - Settings - etc  ### Rate Limiting A 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.  - **X-RateLimit-Limit:** Shows the maximum number of calls that may be executed per hour. - **X-RateLimit-Remaining:** How many calls may still be executed within the current hour. - **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.  ### Further Reading We 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.  ## Getting Started with the REST API  ### API base URL The base URL for an specific instance of Instana can be determined using the tenant and unit information. - `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. - `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.  ### Curl Example Here is an Example to use the REST API with Curl. First lets get all the available metrics with possible aggregations with a GET call.  ```bash curl --request GET \\   --url https://test-instana.instana.io/api/application-monitoring/catalog/metrics \\   --header 'authorization: apiToken xxxxxxxxxxxxxxxx' ```  Next 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.  ```bash curl --request POST \\   --url https://test-instana.instana.io/api/application-monitoring/analyze/call-groups \\   --header 'authorization: apiToken xxxxxxxxxxxxxxxx' \\   --header 'content-type: application/json' \\   --data '{   \"group\":{       \"groupbyTag\":\"endpoint.name\"   },   \"tagFilters\":[    {     \"name\":\"call.error.count\",     \"value\":\"0\",     \"operator\":\"GREATER_THAN\"    }   ],   \"metrics\":[    {     \"metric\":\"errors\",     \"aggregation\":\"MEAN\"    }   ]   }' ```  ### Generating REST API clients  The API is specified using the [OpenAPI v3](https://github.com/OAI/OpenAPI-Specification) (previously known as Swagger) format. You can download the current specification at our [GitHub API documentation](https://instana.github.io/openapi/openapi.yaml).  OpenAPI 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. To generate a client library for your language, you can use the [OpenAPI client generators](https://github.com/OpenAPITools/openapi-generator).  #### Go For 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:  ```bash #!/bin/bash  ### This script assumes you have the `java` and `wget` commands on the path  export UNIT_NAME='myunit' # for example: prod export TENANT_NAME='mytenant' # for example: awesomecompany  //Download the generator to your current working directory: wget 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}\"  //generate a client library that you can vendor into your repository java -jar openapi-generator-cli.jar generate -i https://instana.github.io/openapi/openapi.yaml -g go \\     -o pkg/instana/openapi \\     --skip-validate-spec  //(optional) format the Go code according to the Go code standard gofmt -s -w pkg/instana/openapi ```  The generated clients contain comprehensive READMEs, and you can start right away using the client from the example above:  ```go import instana \"./pkg/instana/openapi\"  // readTags will read all available application monitoring tags along with their type and category func readTags() {  configuration := instana.NewConfiguration()  configuration.Host = \"tenant-unit.instana.io\"  configuration.BasePath = \"https://tenant-unit.instana.io\"   client := instana.NewAPIClient(configuration)  auth := context.WithValue(context.Background(), instana.ContextAPIKey, instana.APIKey{   Key:    apiKey,   Prefix: \"apiToken\",  })   tags, _, err := client.ApplicationCatalogApi.GetApplicationTagCatalog(auth)  if err != nil {   fmt.Fatalf(\"Error calling the API, aborting.\")  }   for _, tag := range tags {   fmt.Printf(\"%s (%s): %s\\n\", tag.Category, tag.Type, tag.Name)  } } ```  #### Java Follow 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).  Depending on your environment, use one of the following java http client implementations which will create a valid client for our OpenAPI specification: ``` //Nativ Java HTTP Client java -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  //Spring WebClient java -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  //Spring RestTemplate java -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  ``` 
+    Documentation for INSTANA REST API
 
-    The version of the OpenAPI document: 1.291.1002
+    The version of the OpenAPI document: 1.306.1368
     Contact: support@instana.com
     Generated by OpenAPI Generator (https://openapi-generator.tech)
 
@@ -60,7 +60,6 @@ class SLISettingsApi:
     ) -> SliConfigurationWithLastUpdated:
         """(Deprecated) Create SLI Config
 
-        This endpoint creates the Service Level Indicator Configuration  ## Mandatory Parameters:  - **id** A unique identifier for each SLI configuration  - **sliName:** Name for the SLI configuration  - **sliEntity:** Entity of the SLI configuration  ### SLI Entity specific parameters  Depending on the chosen `sliType` in the `sliEntity`, there are further required parameters:  #### Application SLI entity  This option can be used to create a Time-Based SLI  - **sliEntity.applicationId:** The Id of the Application Perspective  - **sliEntity.boundaryScope:** Boundary scope of the Application Perspective  - **metricConfiguration.metricName:** The metric name on which to compute the SLI  - **metricConfiguration.metricAggregation:** The aggregation of the metric  - **metricConfiguration.threshold:** Threshold for the metric  #### Availability SLI entity  This opetion can be used to create an Event-Based SLI  - **sliEntity.applicationId:** The Id of the Application Perspective  - **sliEntity.boundaryScope:** Boundary scope of the Application Perspective  ## Deprecated Parameters for Availability SLI entity:  - **sliEntity.serviceId:** The ID if the Service in he context of an Application Perspective  - **sliEntity.endpointId:** The ID of an Endpoint belonging to a Service  - **sliEntity.goodEventFilters:** The list of TagFilters to match good events / calls  - **sliEntity.badEventFilters:** The list of TagFilters to match bad events / calls  All of these filters can be included using the list of TagFilterExpressions via **sliEntity.goodEventFilterExpression** and **sliEntity.badEventFilterExpression**. These parameters will be removed in the upcoming releases. 
 
         :param sli_configuration: (required)
         :type sli_configuration: SliConfiguration
@@ -128,7 +127,6 @@ class SLISettingsApi:
     ) -> ApiResponse[SliConfigurationWithLastUpdated]:
         """(Deprecated) Create SLI Config
 
-        This endpoint creates the Service Level Indicator Configuration  ## Mandatory Parameters:  - **id** A unique identifier for each SLI configuration  - **sliName:** Name for the SLI configuration  - **sliEntity:** Entity of the SLI configuration  ### SLI Entity specific parameters  Depending on the chosen `sliType` in the `sliEntity`, there are further required parameters:  #### Application SLI entity  This option can be used to create a Time-Based SLI  - **sliEntity.applicationId:** The Id of the Application Perspective  - **sliEntity.boundaryScope:** Boundary scope of the Application Perspective  - **metricConfiguration.metricName:** The metric name on which to compute the SLI  - **metricConfiguration.metricAggregation:** The aggregation of the metric  - **metricConfiguration.threshold:** Threshold for the metric  #### Availability SLI entity  This opetion can be used to create an Event-Based SLI  - **sliEntity.applicationId:** The Id of the Application Perspective  - **sliEntity.boundaryScope:** Boundary scope of the Application Perspective  ## Deprecated Parameters for Availability SLI entity:  - **sliEntity.serviceId:** The ID if the Service in he context of an Application Perspective  - **sliEntity.endpointId:** The ID of an Endpoint belonging to a Service  - **sliEntity.goodEventFilters:** The list of TagFilters to match good events / calls  - **sliEntity.badEventFilters:** The list of TagFilters to match bad events / calls  All of these filters can be included using the list of TagFilterExpressions via **sliEntity.goodEventFilterExpression** and **sliEntity.badEventFilterExpression**. These parameters will be removed in the upcoming releases. 
 
         :param sli_configuration: (required)
         :type sli_configuration: SliConfiguration
@@ -196,7 +194,6 @@ class SLISettingsApi:
     ) -> RESTResponseType:
         """(Deprecated) Create SLI Config
 
-        This endpoint creates the Service Level Indicator Configuration  ## Mandatory Parameters:  - **id** A unique identifier for each SLI configuration  - **sliName:** Name for the SLI configuration  - **sliEntity:** Entity of the SLI configuration  ### SLI Entity specific parameters  Depending on the chosen `sliType` in the `sliEntity`, there are further required parameters:  #### Application SLI entity  This option can be used to create a Time-Based SLI  - **sliEntity.applicationId:** The Id of the Application Perspective  - **sliEntity.boundaryScope:** Boundary scope of the Application Perspective  - **metricConfiguration.metricName:** The metric name on which to compute the SLI  - **metricConfiguration.metricAggregation:** The aggregation of the metric  - **metricConfiguration.threshold:** Threshold for the metric  #### Availability SLI entity  This opetion can be used to create an Event-Based SLI  - **sliEntity.applicationId:** The Id of the Application Perspective  - **sliEntity.boundaryScope:** Boundary scope of the Application Perspective  ## Deprecated Parameters for Availability SLI entity:  - **sliEntity.serviceId:** The ID if the Service in he context of an Application Perspective  - **sliEntity.endpointId:** The ID of an Endpoint belonging to a Service  - **sliEntity.goodEventFilters:** The list of TagFilters to match good events / calls  - **sliEntity.badEventFilters:** The list of TagFilters to match bad events / calls  All of these filters can be included using the list of TagFilterExpressions via **sliEntity.goodEventFilterExpression** and **sliEntity.badEventFilterExpression**. These parameters will be removed in the upcoming releases. 
 
         :param sli_configuration: (required)
         :type sli_configuration: SliConfiguration
@@ -337,7 +334,6 @@ class SLISettingsApi:
     ) -> SliConfigurationWithLastUpdated:
         """Create SLI Config
 
-        This endpoint creates the Service Level Indicator Configuration  ## Mandatory Parameters:  - **id** A unique identifier for each SLI configuration  - **sliName:** Name for the SLI configuration  - **sliEntity:** Entity of the SLI configuration  ### SLI Entity specific parameters  Depending on the chosen `sliType` in the `sliEntity`, there are further required parameters:  #### Application SLI entity  This option can be used to create a Time-Based SLI  - **sliEntity.applicationId:** The Id of the Application Perspective  - **sliEntity.boundaryScope:** Boundary scope of the Application Perspective  - **metricConfiguration.metricName:** The metric name on which to compute the SLI  - **metricConfiguration.metricAggregation:** The aggregation of the metric  - **metricConfiguration.threshold:** Threshold for the metric  #### Availability SLI entity  This opetion can be used to create an Event-Based SLI  - **sliEntity.applicationId:** The Id of the Application Perspective  - **sliEntity.boundaryScope:** Boundary scope of the Application Perspective  ## Deprecated Parameters for Availability SLI entity:  - **sliEntity.serviceId:** The ID if the Service in he context of an Application Perspective  - **sliEntity.endpointId:** The ID of an Endpoint belonging to a Service  - **sliEntity.goodEventFilters:** The list of TagFilters to match good events / calls  - **sliEntity.badEventFilters:** The list of TagFilters to match bad events / calls  All of these filters can be included using the list of TagFilterExpressions via **sliEntity.goodEventFilterExpression** and **sliEntity.badEventFilterExpression**. These parameters will be removed in the upcoming releases. 
 
         :param sli_configuration: (required)
         :type sli_configuration: SliConfiguration
@@ -374,6 +370,7 @@ class SLISettingsApi:
         _response_types_map: Dict[str, Optional[str]] = {
             '200': "SliConfigurationWithLastUpdated",
             '400': "str",
+            '422': "str",
         }
         response_data = self.api_client.call_api(
             *_param,
@@ -405,7 +402,6 @@ class SLISettingsApi:
     ) -> ApiResponse[SliConfigurationWithLastUpdated]:
         """Create SLI Config
 
-        This endpoint creates the Service Level Indicator Configuration  ## Mandatory Parameters:  - **id** A unique identifier for each SLI configuration  - **sliName:** Name for the SLI configuration  - **sliEntity:** Entity of the SLI configuration  ### SLI Entity specific parameters  Depending on the chosen `sliType` in the `sliEntity`, there are further required parameters:  #### Application SLI entity  This option can be used to create a Time-Based SLI  - **sliEntity.applicationId:** The Id of the Application Perspective  - **sliEntity.boundaryScope:** Boundary scope of the Application Perspective  - **metricConfiguration.metricName:** The metric name on which to compute the SLI  - **metricConfiguration.metricAggregation:** The aggregation of the metric  - **metricConfiguration.threshold:** Threshold for the metric  #### Availability SLI entity  This opetion can be used to create an Event-Based SLI  - **sliEntity.applicationId:** The Id of the Application Perspective  - **sliEntity.boundaryScope:** Boundary scope of the Application Perspective  ## Deprecated Parameters for Availability SLI entity:  - **sliEntity.serviceId:** The ID if the Service in he context of an Application Perspective  - **sliEntity.endpointId:** The ID of an Endpoint belonging to a Service  - **sliEntity.goodEventFilters:** The list of TagFilters to match good events / calls  - **sliEntity.badEventFilters:** The list of TagFilters to match bad events / calls  All of these filters can be included using the list of TagFilterExpressions via **sliEntity.goodEventFilterExpression** and **sliEntity.badEventFilterExpression**. These parameters will be removed in the upcoming releases. 
 
         :param sli_configuration: (required)
         :type sli_configuration: SliConfiguration
@@ -442,6 +438,7 @@ class SLISettingsApi:
         _response_types_map: Dict[str, Optional[str]] = {
             '200': "SliConfigurationWithLastUpdated",
             '400': "str",
+            '422': "str",
         }
         response_data = self.api_client.call_api(
             *_param,
@@ -473,7 +470,6 @@ class SLISettingsApi:
     ) -> RESTResponseType:
         """Create SLI Config
 
-        This endpoint creates the Service Level Indicator Configuration  ## Mandatory Parameters:  - **id** A unique identifier for each SLI configuration  - **sliName:** Name for the SLI configuration  - **sliEntity:** Entity of the SLI configuration  ### SLI Entity specific parameters  Depending on the chosen `sliType` in the `sliEntity`, there are further required parameters:  #### Application SLI entity  This option can be used to create a Time-Based SLI  - **sliEntity.applicationId:** The Id of the Application Perspective  - **sliEntity.boundaryScope:** Boundary scope of the Application Perspective  - **metricConfiguration.metricName:** The metric name on which to compute the SLI  - **metricConfiguration.metricAggregation:** The aggregation of the metric  - **metricConfiguration.threshold:** Threshold for the metric  #### Availability SLI entity  This opetion can be used to create an Event-Based SLI  - **sliEntity.applicationId:** The Id of the Application Perspective  - **sliEntity.boundaryScope:** Boundary scope of the Application Perspective  ## Deprecated Parameters for Availability SLI entity:  - **sliEntity.serviceId:** The ID if the Service in he context of an Application Perspective  - **sliEntity.endpointId:** The ID of an Endpoint belonging to a Service  - **sliEntity.goodEventFilters:** The list of TagFilters to match good events / calls  - **sliEntity.badEventFilters:** The list of TagFilters to match bad events / calls  All of these filters can be included using the list of TagFilterExpressions via **sliEntity.goodEventFilterExpression** and **sliEntity.badEventFilterExpression**. These parameters will be removed in the upcoming releases. 
 
         :param sli_configuration: (required)
         :type sli_configuration: SliConfiguration
@@ -510,6 +506,7 @@ class SLISettingsApi:
         _response_types_map: Dict[str, Optional[str]] = {
             '200': "SliConfigurationWithLastUpdated",
             '400': "str",
+            '422': "str",
         }
         response_data = self.api_client.call_api(
             *_param,