06 Dec 2019 12:57 AM
Allow wildcards in ignore exceptions
WE have an issue that at the moment we need to ignore certain business exceptions which we need to do in the following way at the moment;
System.ServiceModel.FaultException`1[[RWWA.Gateway.Betting.Contracts.DataContract.Fob.FobFault, RWWA.Gateway.Betting.Contracts, Version=55.0.18703.0, Culture=neutral, PublicKeyToken=null]]
System.ServiceModel.FaultException`1[[RWWA.Gateway.Betting.Contracts.DataContract.Fob.FobFault, RWWA.Gateway.Betting.Contracts, Version=62.0.37728.0, Culture=neutral, PublicKeyToken=null]]
However, everytime we deploy a new version, the version number is updated, so always throws up a new problem every release.
This is hurting us in our ability to be able to automate releases as this needs to be added as another excpetion, and the overhead of about 50 services changing weekly is getting quite burdensome.
If we were able to specify a wildcard for the version number, this would work perfectly! ie to be able to specify
System.ServiceModel.FaultException`1[[RWWA.Gateway.Betting.Contracts.DataContract.Fob.FobFault, RWWA.Gateway.Betting.Contracts, Version=*, Culture=neutral, PublicKeyToken=null]]
(by the way we have tested and doesnt currently work)
Solved! Go to Solution.
06 Dec 2019 08:06 AM
Regular expressions or wildcard are probably too expensive. The error detection rules do match a substring. You don't have to enter the whole exception message.
In your case, would the match of the message text up to the version fit? e.g.
[[RWWA.Gateway.Betting.Contracts.DataContract.Fob.FobFault, RWWA.Gateway.Betting.Contracts, Version=
09 Dec 2019 01:56 AM
Thanks we will give this a go and report back! EDIT - yep works perfectly thanks a lot has solved lots of problems for us!