Best practice for monitoring network switch interfaces without generating noise from unused ports

Gewo — Thu, 14 May 2026 12:31:13 GMT

Hi everyone,

I’m working on a use case where a customer wants to monitor network switch/router interfaces and generate Problems only when critical ports go down.

We are using the Dynatrace network device extension metric com.dynatrace.extension.network_device.if.status.

The initial idea was to alert when an interface is admin up but oper down or lowerLayerDown.

This technically works, but it creates too much noise because many ports are admin up and oper down simply because nothing is connected to them. They match the condition, but they are not real incidents.

So the actual requirement is:

admin up + oper down + expected-up interface = alert

The customer also wants to classify interfaces as P1, P2 or P3. Only P1 interfaces should automatically open tickets in Halo ITSM through Problem Notifications / Alerting Profiles.

I’m considering these options:

Maintain an allowlist of expected-up interfaces and alert only on those.
Tag interfaces with expected_up:true and priority:P1/P2/P3.
Create separate DQL alerts for P1/P2/P3 and route only P1 Problems to Halo.
Use lookup data or an external source instead of hardcoding all interfaces in the DQL query.

What would be the recommended Dynatrace approach for this use case?

Is tagging network interface entities reliable for this, or would you recommend handling the classification directly in DQL with an allowlist/lookup?

Has anyone implemented a scalable way to avoid alerting on unused admin up / oper down switch ports?

Thanks!

Re: Best practice for monitoring network switch interfaces without generating noise from unused ports

p_devulapalli — Tue, 19 May 2026 02:27:28 GMT

@Gewo If you are trying to monitor a network switch you would ideally be looking at interfaces that are critical to be monitored like ports that are connecting to upstream/downstream devices, critical servers etc.,.

Normally the network administrators would label these critical switch ports using the ifAlias field for easy identification. If its setup in a similar way in your environment you can look at ifAlias field on the interfaces to identify and filter only those for monitoring instead of setting up alerting on all the ports .

topic Re: Best practice for monitoring network switch interfaces without generating noise from unused ports in Alerting

Best practice for monitoring network switch interfaces without generating noise from unused ports

Re: Best practice for monitoring network switch interfaces without generating noise from unused ports