@ngaddam TCP Aborted Connections In is a built-in metric does not require a trigger in order to use it. You can create a dashboard and use the Metric Explorer to visualize these metrics.
In the case of TCP Aborted Connections In, you would set your metric source as TCP Devices. If the one device is all you are interested in, you could set the metric source as that device, but I would recommend keeping track of them all if you are worried about this behavior.
As far as alerting on this type of activity, review our documentation on creating an alert. You will most likely want to use a Trend-based alert as aborts are sometimes typical on a network.