![]() ![]() Please have technical services be less “robotic” in responses, I understand the typinator love found in Technical Services, but when it’s blatantly obvious the person who took the support ticket isn’t actually reading what the problem is, that typinator script will tick off your customers engineering team more than you’ll ever believe when it’s not even related to the complaint. Give Atlas App Services Logging more information, there’s no reason like stated above for errors to be cryptic, as when they are cryptic they are worthless, and then my clients (aka mongoDBs as well) start asking me about alternatives to get rid of Device Sync all together for a platform that actually communicates problems so they can be fixed. Error logs like “Device Sync Issue” creates a “You don’t say” response when Device Sync is crashing, this error is as worthless to literally everyone who handles issues with Device Sync as the Windows BSOD error “something happened.” It’s great an error came up, but besides the captain obvious sensation, it’s frustrating. ![]() Make tools accessible to third parties to better troubleshoot or provide better error logging to narrow the problem down. This feedback pertains to supporting Device Sync as a third party: The following is feedback via experiences handling MongoDB customers as the only person on LinkedIn with long-term experience with Device Sync, inside and outside of MongoDB. ![]()
0 Comments
Leave a Reply. |