2 results found
-
When there are errors on the servicebus we don't log it. It would help if we logged errors for troubleshooting purposes.
When there are issues with the servicebus it is not possible to see what went wrong many times. You can go to the servicebus and look at the graph and see that there are "server errors" and "user errors" and "throttled messages"but there is no way to see the details of the server errors or the user errors.
Some times we can see a log entry in the CMS logs but not always and I guess it depends on the type of error.
If we had more information it would help when troubleshooting customers having problems with the servicebus.12 votes -
DXP support for alerts
This is essentially a copy of https://feedback.optimizely.com/forums/964806-commerce-connect/suggestions/51196846-dxp-support-for-alerts and with same intent for all services hosted on the DXP platform.
The scenario for usage is to add monitoring to be able to react swiftly on production issues and support our partner customers.
This gives both us partners and Optimizely more rapid enviroment insights which results in more stable environments and happy end users and thereby customers.
Some examples to mention a few scenarios:
Response times in checkout
High error rates
Failing external calls
Slow response times external services
Slow response times servers
Failing endpoints
Asp.net core threading issues
High cpu on…3 votes
- Don't see your idea?