TunnelState (by Region and TunnelIpAddress) metric : how to find the VPN id ?

[flomaz]

Hello,

I want to monitor AWS VPNs with multiple tunnels. It can happen that only one tunnel IP fails, in this case the VPN won't fail but we would like to be alerted and to check the issue.

I've found this metric but I do not know how to use the dimensions to find the VPN custom_device id to which this tunner IP belongs.

Metric name : `ext:cloud.aws.vpn.tunnelStateByRegionTunnelIpAddress`
Dimensions: `dt.entity.custom_device_group`, `Region`, `TunnelIpAddress`

When monitoring the VPN state per TunnelIPAddress, is there a way to find the VPN id to which a tunnel IP belongs ?

[Peter_Youssef]

Hello @flomaz 

As per the available metrics

you can create metric events and you will be alerted upon valid alerting configurations 

hoping it adds value

KR,

Peter

[flomaz]

Hello @Peter_Youssef ,

Thanks, yes, exactly, I would like to use metric events. I've configured a metric event with the metric "ext:cloud.aws.vpn.tunnelStateByRegionTunnelIpAddress" as I need the IP of the failed tunnel and the VPN id.

I generated an alert and was able to find the failling tunnel IP but not the VPN to which it belongs. Currently if an alerts occurs, the operation team will need to list all the IPS of all VPNs to find to which VPN this IP belongs.

KR,

Florent

[Peter_Youssef]

Hi @flomaz 

1. You can enrich the setup with more tagging rules for discriminations and then the correlations will be easy.
2. It's good to check the topology Model if the full dependencies and correlations are provided Out-Of-The Box it fine to use it in the tagging rules, Otherwise you can define a new rules as per the below example.

(1) - Generic Relationships

(2) - Generic Types

Dynatrace Ref:

• https://docs.dynatrace.com/docs/extend-dynatrace/extend-topology#custom-topology-model

Hoping it adds value.

BR,

Peter.

KR,

Peter. 

[flomaz]

Hi @Peter_Youssef 

Thanks, this looks like an interesting feature. I will try this.

KR,

Florent

[flomaz]

Hi @Peter_Youssef ,

By checking the solution you've documented, I've found the list of entities and explored the properties of this entity `dt.entity.cloudvpn`. The field ipAddress is present but null in my case, do you know if it reserved for a future usage or if there is an issue during metadata retrieval such as missing permissions ?

fetch `dt.entity.cloudvpn`
| fieldsAdd ipAddress,listenPorts,entity.name,called_by,parent_of,accessible_by

 KR,
Florent

[flomaz]

Hi,
It seems that it is not possible. After checking with the support, I've submitted a new product idea.

KR,
Florent

[Peter_Youssef]

Hello @flomaz 

Happy for your progress, it's good to submit it with Dynatrace for a sooner built-in solution.

KR,

Peter