This version of ServiceControl introduces more transport options as well as a few bug fixes and improvements.
The transport options available for ServiceControl and Monitoring instances are now aligned and allows Azure Service Bus and RabbitMQ users to choose from the following options:
You can see my configured queue prefix is “lpi-dev-sqspoc-670-” but when the monitoring service is restarted and I start up one of the business end points with the monitoring plug in installed I still get the following error in the monitoring service logs (GRM-ActivityStream-DataMigration-Host is the logical endpoint name of the business service):
2018-11-21 17:14:22.2167|18|Error|ServiceControl.Transports.AmazonSQS.QueueLengthProvider|Obtaining an approximate number of messages failed for ‘GRM-ActivityStream-DataMigration-Host’
Amazon.SQS.Model.QueueDoesNotExistException: The specified queue does not exist for this wsdl version. —> Amazon.Runtime.Internal.HttpErrorResponseException: The remote server returned an error: (400) Bad Request. —> System.Net.WebException: The remote server returned an error: (400) Bad Request.
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at System.Threading.Tasks.TaskFactory1.FromAsyncCoreLogic(IAsyncResult iar, Func2 endFunction, Action1 endAction, Task1 promise, Boolean requiresSynchronization)
I can see the fix in the ServicedControl.Montoring solution in GutHub. Perhaps this is a bundling/packaging issue? Or is there some other aspect of configuration I am missing?
Maybe it is best if we get on a call so that we can trouble shoot that issue better. Shoot me an email to daniel dot marbach at particular dot net and I’ll try to find a slot that works for both of us. Please add the timezone you are in as an additional info.