Call the CreateHybridMonitorTask operation to create a data import task for an Alibaba Cloud service or a metric from Simple Log Service (SLS) logs.
Operation description
Usage notes
-
Make sure that you have activated Hybrid Cloud Monitoring. For more information, see Activate Hybrid Cloud Monitoring.
-
If you want to create metrics from SLS logs, make sure that you have activated Simple Log Service (SLS) and created a project and a Logstore. For more information, see Quick Start.
Instructions
This topic provides an example of how to create a data import task named aliyun_task for an Alibaba Cloud service. In this example, the cpu_total metric from Elastic Compute Service (ECS) is imported into the aliyun metric repository. The response indicates that the data import task was created.
Try it now
Test
RAM authorization
|
Action |
Access level |
Resource type |
Condition key |
Dependent action |
|
cms:CreateHybridMonitorTask |
create |
*All Resource
|
None | None |
Request parameters
|
Parameter |
Type |
Required |
Description |
Example |
| Namespace |
string |
Yes |
The name of the metric repository. For information about how to obtain the name of a metric repository, see DescribeHybridMonitorNamespaceList. |
aliyun |
| Description |
string |
No |
The description of the monitoring job. |
阿里云产品数据接入任务。 |
| TaskName |
string |
No |
The name of the monitoring job.
|
aliyun_task |
| TaskType |
string |
Yes |
The type of the monitoring job. Valid values:
Valid values:
|
aliyun_fc |
| CollectTargetType |
string |
Yes |
The type of the collection target.
|
aliyun_fc |
| CollectInterval |
string |
No |
The collection period of the metric. Unit: seconds. Valid values:
Unit: seconds. Note
This parameter is required only when you set Valid values:
|
60 |
| GroupId |
string |
No |
The ID of the application group. For information about how to obtain the ID of an application group, see DescribeMonitorGroups. Note
This parameter is required only when you set |
3607**** |
| YARMConfig |
string |
No |
The configuration file of the Alibaba Cloud service that is connected to Hybrid Cloud Monitoring.
The following code provides a sample configuration file:
Note
This parameter is required when you set |
products:- namespace: acs_ecs_dashboard metric_info: - metric_list: - cpu_total |
| TargetUserId |
string |
No |
The ID of the member. If you use a management account to call this operation, you can connect the Alibaba Cloud services of any member in your resource directory to Hybrid Cloud Monitoring. This lets you centrally monitor the Alibaba Cloud services of different members across accounts. Note
This parameter is required only when you set |
120886317861**** |
| AttachLabels |
array<object> |
No |
The tags of the metric. Note
This parameter is required only when you set |
|
|
object |
No |
None. |
||
| Value |
string |
No |
The value of the tag. |
testValue |
| Name |
string |
No |
The key of the tag. |
app_service |
| TargetUserIdList |
string |
No |
The IDs of the members. Separate multiple member IDs with commas (,). Note
This parameter is required only when you call this operation using a management account. |
120886317861**** |
| SLSProcessConfig |
object |
No |
The configurations of SLS logs. Note
This parameter is required only when you set |
|
| Filter |
object |
No |
The filter conditions for the parameters in SLS logs. |
|
| Relation |
string |
No |
The relationship between multiple filter conditions. Valid values:
Valid values:
|
and |
| Filters |
array<object> |
No |
The list of filter conditions for the parameters in SLS logs. |
|
|
object |
No |
None. |
||
| SLSKeyName |
string |
No |
The name of the parameter that is used to filter logs. |
code |
| Operator |
string |
No |
The operator that is used to filter logs based on the parameter value. Valid values:
|
= |
| Value |
string |
No |
The value of the parameter that is used to filter logs. |
200 |
| Statistics |
array<object> |
No |
The method that is used to aggregate the log data. |
|
|
object |
No |
None. |
||
| SLSKeyName |
string |
No |
The name of the parameter that is used to aggregate log data. |
name |
| Function |
string |
No |
The aggregate function. The log data is aggregated based on the specified function over a statistical period. Valid values:
|
count |
| Alias |
string |
No |
The alias of the aggregation result. |
level_count |
| Parameter1 |
string |
No |
The aggregation value.
|
200 |
| Parameter2 |
string |
No |
The aggregation value. Note
This parameter is required only when you set |
299 |
| GroupBy |
array<object> |
No |
The dimension based on which the log data is aggregated. This is equivalent to the GROUP BY clause in SQL. |
|
|
object |
No |
None. |
||
| SLSKeyName |
string |
No |
The name of the parameter that is used to aggregate log data. |
code |
| Alias |
string |
No |
The alias of the aggregation result. |
ApiResult |
| Express |
array<object> |
No |
The result of the basic operations that are performed on the extended fields of the aggregation result. |
|
|
object |
No |
None. |
||
| Express |
string |
No |
The result of the basic operations that are performed on the extended fields of the aggregation result. |
success_count |
| Alias |
string |
No |
The alias of the result of the basic operations that are performed on the extended fields of the aggregation result. |
SuccRate |
| CloudAccessId |
array |
No |
The list of main account IDs for other cloud service providers that are connected to Cloud Monitor. |
|
|
string |
No |
The ID of the main account of another cloud service provider that is connected to Cloud Monitor. |
n5n9ik1b**** |
For more information about common request parameters, see Common parameters.
Response elements
|
Element |
Type |
Description |
Example |
|
object |
None. |
||
| Code |
string |
The status code. Note
A status code of 200 indicates that the request was successful. |
200 |
| Message |
string |
The error message. |
yamlConfigFail |
| RequestId |
string |
The request ID. |
28CEA2E0-3E90-51B2-A7E8-B1ED75534E49 |
| Success |
string |
Indicates whether the operation was successful. Valid values:
|
true |
| TaskId |
integer |
The ID of the monitoring job. |
36**** |
Examples
Success response
JSON format
{
"Code": "200",
"Message": "yamlConfigFail",
"RequestId": "28CEA2E0-3E90-51B2-A7E8-B1ED75534E49",
"Success": "true",
"TaskId": 0
}
Error codes
|
HTTP status code |
Error code |
Error message |
Description |
|---|---|---|---|
| 400 | %s | %s | |
| 500 | %s | %s | |
| 500 | InternalError | The request processing has failed due to some unknown error. | |
| 403 | %s | %s | |
| 404 | %s | %s | |
| 409 | %s | %s |
See Error Codes for a complete list.
Release notes
See Release Notes for a complete list.