Troubleshooting errors is really bad , there should access to logs to find what went wrong
as end user I just want to give a feedback that , this is no the right approach to tackle problem like this , we should have a access to logs somewhere , where we all can easily see what went wrong in the logs rather than using the below trivial method which is really time consuming and frustrating as well.
You have already explained that your team is working on this but having access to logs to monitor what’s happening with asset is the right approach , we have been uploading 100 ‘s of video for transcription and this approach of troubleshooting is really cumbersome .
ravi kumar singh commented
Regarding the question:
>> Also if you can help me with tools and other troubleshooting mechanism , so that I can also do the initial troubleshooting before reaching out to you guys.
Well, as you may know, VI is a SaaS application built on various Azure technologies(for example, media services, storage, web app, cognitive services, APIM, Bing APIs, indexing services, transcription services, search services, SQL, etc.), it is not that easy to troubleshoot yourself to figure out where exactly lies the problem. Even our support engineers may sometimes engage with multiple production teams to troubleshoot together on the issues. Some internal tools are under constructions to help bridge the gap and the long term goal is have the tools public available in the “Diagnose and solve problems” section of media services or somewhere else on Azure portal.
At the current point, I think there are a couple things you can do to isolate if it is a client side issue or server side issue before reaching out to us:
1. Try to use VI portal to upload artifacts => to check if it is your application side issue
2. Try to use VI API to upload artifacts => 1) to check if it is a VI portal issue 2) APIs usually provides more details than portal
3. Does the issue occur to all of your videos or only part of the videos? Have you observed a specific pattern of the failed videos?
4. Does the issue suddenly occurs and is there any VI releases recently? https://docs.microsoft.com/en-us/azure/media-services/video-indexer/release-notes
5. If it is an application side issue, is there any possibilities you can capture a network trace and compared with the success runs from VI portal.
6. you may go to the media service account to check how VI encoding jobs running.
7. you may check F12 traces on the VI portal debug console