Welcome to the forum! It could be. I guess when Prognosis received null data from the Avaya CM for DS1 service, it set the list of Trunk Boards to all down status triggering so many SNMP Trap alerts.
Perhaps first check if the Avaya CM login ID that Prognosis authenticates to the CM as, has the correct permissions to retrieve the data it requires.
Here's the Help location detailing the required permissions:
Product Guides > Prognosis for Unified Communications > Avaya Aura Communication Manager > Configuration > Avaya Setup > Configure SAT User Profile (CM 4+)
Product Guides > Prognosis for Unified Communications > Avaya Aura Communication Manager > Configuration > Avaya Setup > Create Login Account (CM 4+)
Otherwise, you could open a case with Support, and include a new IRFAX that they can use to see if they can identify the source threshold and give you suggestions to try if there are ways to refine it. Those alerts do not come from the default out-of-box threshold Avaya_Alerts. Perhaps it is something some one created or that was carried over from a previous version if this was an upgrade.