nsxt.PolicyLbUdpMonitorProfile
Explore with Pulumi AI
Create PolicyLbUdpMonitorProfile Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new PolicyLbUdpMonitorProfile(name: string, args: PolicyLbUdpMonitorProfileArgs, opts?: CustomResourceOptions);
@overload
def PolicyLbUdpMonitorProfile(resource_name: str,
args: PolicyLbUdpMonitorProfileArgs,
opts: Optional[ResourceOptions] = None)
@overload
def PolicyLbUdpMonitorProfile(resource_name: str,
opts: Optional[ResourceOptions] = None,
display_name: Optional[str] = None,
description: Optional[str] = None,
fall_count: Optional[float] = None,
interval: Optional[float] = None,
monitor_port: Optional[float] = None,
nsx_id: Optional[str] = None,
policy_lb_udp_monitor_profile_id: Optional[str] = None,
receive: Optional[str] = None,
rise_count: Optional[float] = None,
send: Optional[str] = None,
tags: Optional[Sequence[PolicyLbUdpMonitorProfileTagArgs]] = None,
timeout: Optional[float] = None)
func NewPolicyLbUdpMonitorProfile(ctx *Context, name string, args PolicyLbUdpMonitorProfileArgs, opts ...ResourceOption) (*PolicyLbUdpMonitorProfile, error)
public PolicyLbUdpMonitorProfile(string name, PolicyLbUdpMonitorProfileArgs args, CustomResourceOptions? opts = null)
public PolicyLbUdpMonitorProfile(String name, PolicyLbUdpMonitorProfileArgs args)
public PolicyLbUdpMonitorProfile(String name, PolicyLbUdpMonitorProfileArgs args, CustomResourceOptions options)
type: nsxt:PolicyLbUdpMonitorProfile
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
Parameters
- name string
- The unique name of the resource.
- args PolicyLbUdpMonitorProfileArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args PolicyLbUdpMonitorProfileArgs
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args PolicyLbUdpMonitorProfileArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args PolicyLbUdpMonitorProfileArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args PolicyLbUdpMonitorProfileArgs
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
Constructor example
The following reference example uses placeholder values for all input properties.
var policyLbUdpMonitorProfileResource = new Nsxt.PolicyLbUdpMonitorProfile("policyLbUdpMonitorProfileResource", new()
{
DisplayName = "string",
Description = "string",
FallCount = 0,
Interval = 0,
MonitorPort = 0,
NsxId = "string",
PolicyLbUdpMonitorProfileId = "string",
Receive = "string",
RiseCount = 0,
Send = "string",
Tags = new[]
{
new Nsxt.Inputs.PolicyLbUdpMonitorProfileTagArgs
{
Scope = "string",
Tag = "string",
},
},
Timeout = 0,
});
example, err := nsxt.NewPolicyLbUdpMonitorProfile(ctx, "policyLbUdpMonitorProfileResource", &nsxt.PolicyLbUdpMonitorProfileArgs{
DisplayName: pulumi.String("string"),
Description: pulumi.String("string"),
FallCount: pulumi.Float64(0),
Interval: pulumi.Float64(0),
MonitorPort: pulumi.Float64(0),
NsxId: pulumi.String("string"),
PolicyLbUdpMonitorProfileId: pulumi.String("string"),
Receive: pulumi.String("string"),
RiseCount: pulumi.Float64(0),
Send: pulumi.String("string"),
Tags: nsxt.PolicyLbUdpMonitorProfileTagArray{
&nsxt.PolicyLbUdpMonitorProfileTagArgs{
Scope: pulumi.String("string"),
Tag: pulumi.String("string"),
},
},
Timeout: pulumi.Float64(0),
})
var policyLbUdpMonitorProfileResource = new PolicyLbUdpMonitorProfile("policyLbUdpMonitorProfileResource", PolicyLbUdpMonitorProfileArgs.builder()
.displayName("string")
.description("string")
.fallCount(0)
.interval(0)
.monitorPort(0)
.nsxId("string")
.policyLbUdpMonitorProfileId("string")
.receive("string")
.riseCount(0)
.send("string")
.tags(PolicyLbUdpMonitorProfileTagArgs.builder()
.scope("string")
.tag("string")
.build())
.timeout(0)
.build());
policy_lb_udp_monitor_profile_resource = nsxt.PolicyLbUdpMonitorProfile("policyLbUdpMonitorProfileResource",
display_name="string",
description="string",
fall_count=0,
interval=0,
monitor_port=0,
nsx_id="string",
policy_lb_udp_monitor_profile_id="string",
receive="string",
rise_count=0,
send="string",
tags=[{
"scope": "string",
"tag": "string",
}],
timeout=0)
const policyLbUdpMonitorProfileResource = new nsxt.PolicyLbUdpMonitorProfile("policyLbUdpMonitorProfileResource", {
displayName: "string",
description: "string",
fallCount: 0,
interval: 0,
monitorPort: 0,
nsxId: "string",
policyLbUdpMonitorProfileId: "string",
receive: "string",
riseCount: 0,
send: "string",
tags: [{
scope: "string",
tag: "string",
}],
timeout: 0,
});
type: nsxt:PolicyLbUdpMonitorProfile
properties:
description: string
displayName: string
fallCount: 0
interval: 0
monitorPort: 0
nsxId: string
policyLbUdpMonitorProfileId: string
receive: string
riseCount: 0
send: string
tags:
- scope: string
tag: string
timeout: 0
PolicyLbUdpMonitorProfile Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
In Python, inputs that are objects can be passed either as argument classes or as dictionary literals.
The PolicyLbUdpMonitorProfile resource accepts the following input properties:
- Display
Name string - Display name of the resource.
- Description string
- Description of the resource.
- Fall
Count double - Mark member status DOWN if the healtcheck fails consecutively for fall_count times.
- Interval double
- Active healthchecks are initiated periodically, at a configurable interval (in seconds), to each member of the Group.
- Monitor
Port double - Typically, monitors perform healthchecks to Group members using the member IP address and pool_port. However, in some cases, customers prefer to run healthchecks against a different port than the pool member port which handles actual application traffic. In such cases, the port to run healthchecks against can be specified in the monitor_port value.
- Nsx
Id string - The NSX ID of this resource. If set, this ID will be used to create the resource.
- Policy
Lb stringUdp Monitor Profile Id - ID of the resource.
- Receive string
- The expected data string to be received from the response, can be anywhere in the response. UDP healthcheck is considered failed if there is no server response within the timeout period.
- Rise
Count double - Bring a DOWN member UP if rise_count successive healthchecks succeed.
- Send string
- The data to be sent to the monitored server.
- List<Policy
Lb Udp Monitor Profile Tag> - A list of scope + tag pairs to associate with this resource.
- Timeout double
- Timeout specified in seconds. After a healthcheck is initiated, if it does not complete within a certain period, then also the healthcheck is considered to be unsuccessful. Completing a healthcheck within timeout means establishing a connection (TCP or SSL), if applicable, sending the request and receiving the response, all within the configured timeout.
- Display
Name string - Display name of the resource.
- Description string
- Description of the resource.
- Fall
Count float64 - Mark member status DOWN if the healtcheck fails consecutively for fall_count times.
- Interval float64
- Active healthchecks are initiated periodically, at a configurable interval (in seconds), to each member of the Group.
- Monitor
Port float64 - Typically, monitors perform healthchecks to Group members using the member IP address and pool_port. However, in some cases, customers prefer to run healthchecks against a different port than the pool member port which handles actual application traffic. In such cases, the port to run healthchecks against can be specified in the monitor_port value.
- Nsx
Id string - The NSX ID of this resource. If set, this ID will be used to create the resource.
- Policy
Lb stringUdp Monitor Profile Id - ID of the resource.
- Receive string
- The expected data string to be received from the response, can be anywhere in the response. UDP healthcheck is considered failed if there is no server response within the timeout period.
- Rise
Count float64 - Bring a DOWN member UP if rise_count successive healthchecks succeed.
- Send string
- The data to be sent to the monitored server.
- []Policy
Lb Udp Monitor Profile Tag Args - A list of scope + tag pairs to associate with this resource.
- Timeout float64
- Timeout specified in seconds. After a healthcheck is initiated, if it does not complete within a certain period, then also the healthcheck is considered to be unsuccessful. Completing a healthcheck within timeout means establishing a connection (TCP or SSL), if applicable, sending the request and receiving the response, all within the configured timeout.
- display
Name String - Display name of the resource.
- description String
- Description of the resource.
- fall
Count Double - Mark member status DOWN if the healtcheck fails consecutively for fall_count times.
- interval Double
- Active healthchecks are initiated periodically, at a configurable interval (in seconds), to each member of the Group.
- monitor
Port Double - Typically, monitors perform healthchecks to Group members using the member IP address and pool_port. However, in some cases, customers prefer to run healthchecks against a different port than the pool member port which handles actual application traffic. In such cases, the port to run healthchecks against can be specified in the monitor_port value.
- nsx
Id String - The NSX ID of this resource. If set, this ID will be used to create the resource.
- policy
Lb StringUdp Monitor Profile Id - ID of the resource.
- receive String
- The expected data string to be received from the response, can be anywhere in the response. UDP healthcheck is considered failed if there is no server response within the timeout period.
- rise
Count Double - Bring a DOWN member UP if rise_count successive healthchecks succeed.
- send String
- The data to be sent to the monitored server.
- List<Policy
Lb Udp Monitor Profile Tag> - A list of scope + tag pairs to associate with this resource.
- timeout Double
- Timeout specified in seconds. After a healthcheck is initiated, if it does not complete within a certain period, then also the healthcheck is considered to be unsuccessful. Completing a healthcheck within timeout means establishing a connection (TCP or SSL), if applicable, sending the request and receiving the response, all within the configured timeout.
- display
Name string - Display name of the resource.
- description string
- Description of the resource.
- fall
Count number - Mark member status DOWN if the healtcheck fails consecutively for fall_count times.
- interval number
- Active healthchecks are initiated periodically, at a configurable interval (in seconds), to each member of the Group.
- monitor
Port number - Typically, monitors perform healthchecks to Group members using the member IP address and pool_port. However, in some cases, customers prefer to run healthchecks against a different port than the pool member port which handles actual application traffic. In such cases, the port to run healthchecks against can be specified in the monitor_port value.
- nsx
Id string - The NSX ID of this resource. If set, this ID will be used to create the resource.
- policy
Lb stringUdp Monitor Profile Id - ID of the resource.
- receive string
- The expected data string to be received from the response, can be anywhere in the response. UDP healthcheck is considered failed if there is no server response within the timeout period.
- rise
Count number - Bring a DOWN member UP if rise_count successive healthchecks succeed.
- send string
- The data to be sent to the monitored server.
- Policy
Lb Udp Monitor Profile Tag[] - A list of scope + tag pairs to associate with this resource.
- timeout number
- Timeout specified in seconds. After a healthcheck is initiated, if it does not complete within a certain period, then also the healthcheck is considered to be unsuccessful. Completing a healthcheck within timeout means establishing a connection (TCP or SSL), if applicable, sending the request and receiving the response, all within the configured timeout.
- display_
name str - Display name of the resource.
- description str
- Description of the resource.
- fall_
count float - Mark member status DOWN if the healtcheck fails consecutively for fall_count times.
- interval float
- Active healthchecks are initiated periodically, at a configurable interval (in seconds), to each member of the Group.
- monitor_
port float - Typically, monitors perform healthchecks to Group members using the member IP address and pool_port. However, in some cases, customers prefer to run healthchecks against a different port than the pool member port which handles actual application traffic. In such cases, the port to run healthchecks against can be specified in the monitor_port value.
- nsx_
id str - The NSX ID of this resource. If set, this ID will be used to create the resource.
- policy_
lb_ strudp_ monitor_ profile_ id - ID of the resource.
- receive str
- The expected data string to be received from the response, can be anywhere in the response. UDP healthcheck is considered failed if there is no server response within the timeout period.
- rise_
count float - Bring a DOWN member UP if rise_count successive healthchecks succeed.
- send str
- The data to be sent to the monitored server.
- Sequence[Policy
Lb Udp Monitor Profile Tag Args] - A list of scope + tag pairs to associate with this resource.
- timeout float
- Timeout specified in seconds. After a healthcheck is initiated, if it does not complete within a certain period, then also the healthcheck is considered to be unsuccessful. Completing a healthcheck within timeout means establishing a connection (TCP or SSL), if applicable, sending the request and receiving the response, all within the configured timeout.
- display
Name String - Display name of the resource.
- description String
- Description of the resource.
- fall
Count Number - Mark member status DOWN if the healtcheck fails consecutively for fall_count times.
- interval Number
- Active healthchecks are initiated periodically, at a configurable interval (in seconds), to each member of the Group.
- monitor
Port Number - Typically, monitors perform healthchecks to Group members using the member IP address and pool_port. However, in some cases, customers prefer to run healthchecks against a different port than the pool member port which handles actual application traffic. In such cases, the port to run healthchecks against can be specified in the monitor_port value.
- nsx
Id String - The NSX ID of this resource. If set, this ID will be used to create the resource.
- policy
Lb StringUdp Monitor Profile Id - ID of the resource.
- receive String
- The expected data string to be received from the response, can be anywhere in the response. UDP healthcheck is considered failed if there is no server response within the timeout period.
- rise
Count Number - Bring a DOWN member UP if rise_count successive healthchecks succeed.
- send String
- The data to be sent to the monitored server.
- List<Property Map>
- A list of scope + tag pairs to associate with this resource.
- timeout Number
- Timeout specified in seconds. After a healthcheck is initiated, if it does not complete within a certain period, then also the healthcheck is considered to be unsuccessful. Completing a healthcheck within timeout means establishing a connection (TCP or SSL), if applicable, sending the request and receiving the response, all within the configured timeout.
Outputs
All input properties are implicitly available as output properties. Additionally, the PolicyLbUdpMonitorProfile resource produces the following output properties:
Look up Existing PolicyLbUdpMonitorProfile Resource
Get an existing PolicyLbUdpMonitorProfile resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.
public static get(name: string, id: Input<ID>, state?: PolicyLbUdpMonitorProfileState, opts?: CustomResourceOptions): PolicyLbUdpMonitorProfile
@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
description: Optional[str] = None,
display_name: Optional[str] = None,
fall_count: Optional[float] = None,
interval: Optional[float] = None,
monitor_port: Optional[float] = None,
nsx_id: Optional[str] = None,
path: Optional[str] = None,
policy_lb_udp_monitor_profile_id: Optional[str] = None,
receive: Optional[str] = None,
revision: Optional[float] = None,
rise_count: Optional[float] = None,
send: Optional[str] = None,
tags: Optional[Sequence[PolicyLbUdpMonitorProfileTagArgs]] = None,
timeout: Optional[float] = None) -> PolicyLbUdpMonitorProfile
func GetPolicyLbUdpMonitorProfile(ctx *Context, name string, id IDInput, state *PolicyLbUdpMonitorProfileState, opts ...ResourceOption) (*PolicyLbUdpMonitorProfile, error)
public static PolicyLbUdpMonitorProfile Get(string name, Input<string> id, PolicyLbUdpMonitorProfileState? state, CustomResourceOptions? opts = null)
public static PolicyLbUdpMonitorProfile get(String name, Output<String> id, PolicyLbUdpMonitorProfileState state, CustomResourceOptions options)
resources: _: type: nsxt:PolicyLbUdpMonitorProfile get: id: ${id}
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- resource_name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- Description string
- Description of the resource.
- Display
Name string - Display name of the resource.
- Fall
Count double - Mark member status DOWN if the healtcheck fails consecutively for fall_count times.
- Interval double
- Active healthchecks are initiated periodically, at a configurable interval (in seconds), to each member of the Group.
- Monitor
Port double - Typically, monitors perform healthchecks to Group members using the member IP address and pool_port. However, in some cases, customers prefer to run healthchecks against a different port than the pool member port which handles actual application traffic. In such cases, the port to run healthchecks against can be specified in the monitor_port value.
- Nsx
Id string - The NSX ID of this resource. If set, this ID will be used to create the resource.
- Path string
- The NSX path of the policy resource.
- Policy
Lb stringUdp Monitor Profile Id - ID of the resource.
- Receive string
- The expected data string to be received from the response, can be anywhere in the response. UDP healthcheck is considered failed if there is no server response within the timeout period.
- Revision double
- Indicates current revision number of the object as seen by NSX-T API server. This attribute can be useful for debugging.
- Rise
Count double - Bring a DOWN member UP if rise_count successive healthchecks succeed.
- Send string
- The data to be sent to the monitored server.
- List<Policy
Lb Udp Monitor Profile Tag> - A list of scope + tag pairs to associate with this resource.
- Timeout double
- Timeout specified in seconds. After a healthcheck is initiated, if it does not complete within a certain period, then also the healthcheck is considered to be unsuccessful. Completing a healthcheck within timeout means establishing a connection (TCP or SSL), if applicable, sending the request and receiving the response, all within the configured timeout.
- Description string
- Description of the resource.
- Display
Name string - Display name of the resource.
- Fall
Count float64 - Mark member status DOWN if the healtcheck fails consecutively for fall_count times.
- Interval float64
- Active healthchecks are initiated periodically, at a configurable interval (in seconds), to each member of the Group.
- Monitor
Port float64 - Typically, monitors perform healthchecks to Group members using the member IP address and pool_port. However, in some cases, customers prefer to run healthchecks against a different port than the pool member port which handles actual application traffic. In such cases, the port to run healthchecks against can be specified in the monitor_port value.
- Nsx
Id string - The NSX ID of this resource. If set, this ID will be used to create the resource.
- Path string
- The NSX path of the policy resource.
- Policy
Lb stringUdp Monitor Profile Id - ID of the resource.
- Receive string
- The expected data string to be received from the response, can be anywhere in the response. UDP healthcheck is considered failed if there is no server response within the timeout period.
- Revision float64
- Indicates current revision number of the object as seen by NSX-T API server. This attribute can be useful for debugging.
- Rise
Count float64 - Bring a DOWN member UP if rise_count successive healthchecks succeed.
- Send string
- The data to be sent to the monitored server.
- []Policy
Lb Udp Monitor Profile Tag Args - A list of scope + tag pairs to associate with this resource.
- Timeout float64
- Timeout specified in seconds. After a healthcheck is initiated, if it does not complete within a certain period, then also the healthcheck is considered to be unsuccessful. Completing a healthcheck within timeout means establishing a connection (TCP or SSL), if applicable, sending the request and receiving the response, all within the configured timeout.
- description String
- Description of the resource.
- display
Name String - Display name of the resource.
- fall
Count Double - Mark member status DOWN if the healtcheck fails consecutively for fall_count times.
- interval Double
- Active healthchecks are initiated periodically, at a configurable interval (in seconds), to each member of the Group.
- monitor
Port Double - Typically, monitors perform healthchecks to Group members using the member IP address and pool_port. However, in some cases, customers prefer to run healthchecks against a different port than the pool member port which handles actual application traffic. In such cases, the port to run healthchecks against can be specified in the monitor_port value.
- nsx
Id String - The NSX ID of this resource. If set, this ID will be used to create the resource.
- path String
- The NSX path of the policy resource.
- policy
Lb StringUdp Monitor Profile Id - ID of the resource.
- receive String
- The expected data string to be received from the response, can be anywhere in the response. UDP healthcheck is considered failed if there is no server response within the timeout period.
- revision Double
- Indicates current revision number of the object as seen by NSX-T API server. This attribute can be useful for debugging.
- rise
Count Double - Bring a DOWN member UP if rise_count successive healthchecks succeed.
- send String
- The data to be sent to the monitored server.
- List<Policy
Lb Udp Monitor Profile Tag> - A list of scope + tag pairs to associate with this resource.
- timeout Double
- Timeout specified in seconds. After a healthcheck is initiated, if it does not complete within a certain period, then also the healthcheck is considered to be unsuccessful. Completing a healthcheck within timeout means establishing a connection (TCP or SSL), if applicable, sending the request and receiving the response, all within the configured timeout.
- description string
- Description of the resource.
- display
Name string - Display name of the resource.
- fall
Count number - Mark member status DOWN if the healtcheck fails consecutively for fall_count times.
- interval number
- Active healthchecks are initiated periodically, at a configurable interval (in seconds), to each member of the Group.
- monitor
Port number - Typically, monitors perform healthchecks to Group members using the member IP address and pool_port. However, in some cases, customers prefer to run healthchecks against a different port than the pool member port which handles actual application traffic. In such cases, the port to run healthchecks against can be specified in the monitor_port value.
- nsx
Id string - The NSX ID of this resource. If set, this ID will be used to create the resource.
- path string
- The NSX path of the policy resource.
- policy
Lb stringUdp Monitor Profile Id - ID of the resource.
- receive string
- The expected data string to be received from the response, can be anywhere in the response. UDP healthcheck is considered failed if there is no server response within the timeout period.
- revision number
- Indicates current revision number of the object as seen by NSX-T API server. This attribute can be useful for debugging.
- rise
Count number - Bring a DOWN member UP if rise_count successive healthchecks succeed.
- send string
- The data to be sent to the monitored server.
- Policy
Lb Udp Monitor Profile Tag[] - A list of scope + tag pairs to associate with this resource.
- timeout number
- Timeout specified in seconds. After a healthcheck is initiated, if it does not complete within a certain period, then also the healthcheck is considered to be unsuccessful. Completing a healthcheck within timeout means establishing a connection (TCP or SSL), if applicable, sending the request and receiving the response, all within the configured timeout.
- description str
- Description of the resource.
- display_
name str - Display name of the resource.
- fall_
count float - Mark member status DOWN if the healtcheck fails consecutively for fall_count times.
- interval float
- Active healthchecks are initiated periodically, at a configurable interval (in seconds), to each member of the Group.
- monitor_
port float - Typically, monitors perform healthchecks to Group members using the member IP address and pool_port. However, in some cases, customers prefer to run healthchecks against a different port than the pool member port which handles actual application traffic. In such cases, the port to run healthchecks against can be specified in the monitor_port value.
- nsx_
id str - The NSX ID of this resource. If set, this ID will be used to create the resource.
- path str
- The NSX path of the policy resource.
- policy_
lb_ strudp_ monitor_ profile_ id - ID of the resource.
- receive str
- The expected data string to be received from the response, can be anywhere in the response. UDP healthcheck is considered failed if there is no server response within the timeout period.
- revision float
- Indicates current revision number of the object as seen by NSX-T API server. This attribute can be useful for debugging.
- rise_
count float - Bring a DOWN member UP if rise_count successive healthchecks succeed.
- send str
- The data to be sent to the monitored server.
- Sequence[Policy
Lb Udp Monitor Profile Tag Args] - A list of scope + tag pairs to associate with this resource.
- timeout float
- Timeout specified in seconds. After a healthcheck is initiated, if it does not complete within a certain period, then also the healthcheck is considered to be unsuccessful. Completing a healthcheck within timeout means establishing a connection (TCP or SSL), if applicable, sending the request and receiving the response, all within the configured timeout.
- description String
- Description of the resource.
- display
Name String - Display name of the resource.
- fall
Count Number - Mark member status DOWN if the healtcheck fails consecutively for fall_count times.
- interval Number
- Active healthchecks are initiated periodically, at a configurable interval (in seconds), to each member of the Group.
- monitor
Port Number - Typically, monitors perform healthchecks to Group members using the member IP address and pool_port. However, in some cases, customers prefer to run healthchecks against a different port than the pool member port which handles actual application traffic. In such cases, the port to run healthchecks against can be specified in the monitor_port value.
- nsx
Id String - The NSX ID of this resource. If set, this ID will be used to create the resource.
- path String
- The NSX path of the policy resource.
- policy
Lb StringUdp Monitor Profile Id - ID of the resource.
- receive String
- The expected data string to be received from the response, can be anywhere in the response. UDP healthcheck is considered failed if there is no server response within the timeout period.
- revision Number
- Indicates current revision number of the object as seen by NSX-T API server. This attribute can be useful for debugging.
- rise
Count Number - Bring a DOWN member UP if rise_count successive healthchecks succeed.
- send String
- The data to be sent to the monitored server.
- List<Property Map>
- A list of scope + tag pairs to associate with this resource.
- timeout Number
- Timeout specified in seconds. After a healthcheck is initiated, if it does not complete within a certain period, then also the healthcheck is considered to be unsuccessful. Completing a healthcheck within timeout means establishing a connection (TCP or SSL), if applicable, sending the request and receiving the response, all within the configured timeout.
Supporting Types
PolicyLbUdpMonitorProfileTag, PolicyLbUdpMonitorProfileTagArgs
Package Details
- Repository
- nsxt vmware/terraform-provider-nsxt
- License
- Notes
- This Pulumi package is based on the
nsxt
Terraform Provider.