Obtaining API Parameters
Location | Parameter | Mandatory | Type | Description |
|---|---|---|---|---|
region_name | Yes | String | Region name, which can be obtained from the region field in Table 3. | |
region_id | No | String | Region ID, which can be obtained from the region field in Table 3. | |
business_id | Yes | Long | Application ID, which can be obtained from the id field in Table 3. | |
env_tag_id | No | Long | Environment tag ID, which can be obtained from the id field in Table 4. | |
business_id | Yes | Long | Application ID, which can be obtained from the id field in Table 3. | |
business_id | Yes | Long | Application ID, which can be obtained from the id field in Table 3. | |
app_id | Yes | Long | Component ID, which can be obtained from the id field in Table 4. | |
business_id | Yes | Long | Application ID, which can be obtained from the id field in Table 3. | |
sub_business_id | Yes | Long | Sub-application ID, which can be obtained from the real_id of the node whose type is SUB_BUSINESS in Table 5. | |
env_id | Yes | Long | Environment ID, which can be obtained from real_id of the node whose type is ENVIRONMENT in Table 5. | |
collector_id | Yes | Long | Collector ID, which can be obtained from the collector_id field in Table 5. | |
trace_id | Yes | String | Trace ID, which can be obtained from the trace_id field in Table 5. | |
trace_id | Yes | String | Trace ID, which can be obtained from the trace_id field in Table 4. | |
span_id | Yes | String | Span ID, which can be obtained from the span_id field in Table 4. | |
event_id | Yes | String | Event ID, which can be obtained from the event_id field in Table 4. | |
env_id | Yes | Long | Environment ID, which can be obtained from the env_id field in Table 4. | |
env_id | No | Long | Environment ID, which can be obtained from the id field in Table 4. | |
instance_id | No | Long | Instance ID, which can be obtained from the instance_id field in Table 4. | |
app_id | No | Long | Component ID, which can be obtained from the id field in Table 4. | |
biz_id | Yes | Long | Application ID, which can be obtained from the id field in Table 3. | |
trace_id | Yes | String | Trace ID, which can be obtained from the trace_id field in Table 5. | |
view_config | Yes | TrendView object | View configuration information, which can be obtained from the ViewBase object in Table 5. | |
instance_id | No | Long | Instance ID, which can be obtained from the instance_id field in Table 4. If this parameter is left blank, the aggregated data of all instances will be obtained. | |
monitor_item_id | Yes | Long | Monitoring item ID, which can be obtained from the monitor_item_id field in Table 5. | |
env_id | Yes | Long | Environment ID, which can be obtained from real_id of the node whose type is ENVIRONMENT in Table 5. | |
view_config | Yes | SumTableView object | View configuration information, which can be obtained from the ViewBase object in Table 5. | |
instance_id | No | Long | Instance ID, which can be obtained from the instance_id field in Table 4. If this parameter is left blank, the aggregated data of all instances will be obtained. | |
monitor_item_id | Yes | Long | Monitoring item ID, which can be obtained from the monitor_item_id field in Table 5. | |
env_id | Yes | Long | Environment ID, which can be obtained from real_id of the node whose type is ENVIRONMENT in Table 5. | |
view_config | Yes | RawTableView object | Raw data table view, which can be obtained from the ViewBase object in Table 5. | |
instance_id | Yes | Long | Instance ID, which can be obtained from the instance_id field in Table 4. If this parameter is left blank, the aggregated data of all instances will be obtained. | |
monitor_item_id | Yes | Long | Monitoring item ID, which can be obtained from the monitor_item_id field in Table 5. | |
env_id | Yes | Long | Environment ID, which can be obtained from real_id of the node whose type is ENVIRONMENT in Table 5. | |
env_id | Yes | Long | Environment ID, which can be obtained from real_id of the node whose type is ENVIRONMENT in Table 5. | |
env_id | Yes | Long | Environment ID, which can be obtained from real_id of the node whose type is ENVIRONMENT in Table 5. | |
region | No | String | Region name, which can be obtained from the region field in Table 3. | |
business_id | Yes | Long | Application ID, which can be obtained from the id field in Table 3. | |
monitor_item_id | No | Long | Monitoring item ID, which can be obtained from the monitor_item_id field in Table 5. | |
collector_id | No | Integer | Collector ID, which can be obtained from the collector_id field in Table 5. | |
alarm_data_id | Yes | Integer | Alarm/event ID, which can be obtained from the id field in Table 4. | |
region | Yes | String | Region name, which can be obtained from the region field in Table 3. | |
target_business_id | Yes | Long | Target application ID, which can be obtained from the id field in Table 3. | |
env_tag_list | No | Array of integers | Environment tag list, which can be empty or obtained from the id field in Table 4. | |
target_env_id | Yes | Long | Environment ID, which can be obtained from real_id of the node whose type is ENVIRONMENT in Table 5. | |
business_id | Yes | Long | Application ID, which can be obtained from the id field in Table 3. | |
env_id | No | Long | Environment ID, which can be obtained from the id field in Table 4. | |
business_id | Yes | Long | Application ID, which can be obtained from the id field in Table 3. | |
region | Yes | String | Region name, which can be obtained from the region field in Table 3. | |
business_id | Yes | Long | Application ID, which can be obtained from the id field in Table 3. | |
region | Yes | String | Region name, which can be obtained from the region field in Table 3. | |
env_id | No | Long | Environment ID, which can be obtained from the env_id field in Table 4. | |
tx_name | Yes | String | Transaction name, which is obtained from the tx_name field in Table 4. |