Create Ipfix Config
Create a new IPFIX configuration
{
"_self": {
"rel": "string"
},
"_system_owned": false,
"display_name": "string",
"description": "string",
"tags": [
{
"scope": "string",
"tag": "string"
}
],
"_revision": 0,
"applied_tos": [
{
"target_display_name": "string",
"is_valid": false,
"target_id": "string",
"target_type": "string"
}
],
"_schema": "string",
"_create_time": 0,
"_links": [
{
"action": "string",
"href": "string",
"rel": "string"
}
],
"resource_type": "string",
"_last_modified_time": 0,
"_last_modified_user": "string",
"id": "string",
"_create_user": "string"
}
Indicates system owned resource
Defaults to ID if not set
description
The _revision property describes the current revision of the resource. To prevent clients from overwriting each other's changes, PUT operations must include the current _revision of the resource, which clients should obtain by issuing a GET operation. If the _revision provided in a PUT request is missing or stale, the operation will be rejected.
List of objects where the IPFIX Config will be enabled.
_schema
Timestamp of resource creation
The server will populate this field when returing the resource. Ignored on PUT and POST.
Supported IPFIX Config Types.
Timestamp of last modification
ID of the user who last modified this resource
id
ID of the user who created this resource
Resource created successfully
{
"_self": {
"rel": "string"
},
"_system_owned": false,
"display_name": "string",
"description": "string",
"tags": [
{
"scope": "string",
"tag": "string"
}
],
"_revision": 0,
"applied_tos": [
{
"target_display_name": "string",
"is_valid": false,
"target_id": "string",
"target_type": "string"
}
],
"_schema": "string",
"_create_time": 0,
"_links": [
{
"action": "string",
"href": "string",
"rel": "string"
}
],
"resource_type": "string",
"_last_modified_time": 0,
"_last_modified_user": "string",
"id": "string",
"_create_user": "string"
}
Indicates system owned resource
Defaults to ID if not set
description
The _revision property describes the current revision of the resource. To prevent clients from overwriting each other's changes, PUT operations must include the current _revision of the resource, which clients should obtain by issuing a GET operation. If the _revision provided in a PUT request is missing or stale, the operation will be rejected.
List of objects where the IPFIX Config will be enabled.
_schema
Timestamp of resource creation
The server will populate this field when returing the resource. Ignored on PUT and POST.
Supported IPFIX Config Types.
Timestamp of last modification
ID of the user who last modified this resource
id
ID of the user who created this resource
Unexpected error
{
"module_name": "string",
"error_message": "string",
"error_code": 0
}
module_name
error_message
error_code