Closed gimmecoderg closed 3 months ago
@gimmecoderg Thanks for your feedback! We will investigate and update as appropriate.
Thanks for your dedication to our documentation. This issue has been moved to an internal work item for triage and prioritization. Thanks in advance for your understanding as we investigate to provide the most accurate documentation updates. #please-close
Internal work item: https://dev.azure.com/msft-skilling/Content/_workitems/edit/262445
Please also note that GitHub documentation issues are being phased out completely. For more information see: https://aka.ms/ContentUserFeedback.
Our support team is available to assist you if you have any pressing questions or problems that need to be resolved. You can create a support ticket by visiting the following link: https://azure.microsoft.com/support/create-ticket/
You may also ask support questions to our Q&A forums or on Stack Overflow when the questions are related to coding.
We've had some struggles with using a custom data source in the legacy agent for the SQL "ERRORLOG" file. Since it doesn't have an extension, it's not able to be explicitly set as a path. I've tried several wildcard paths like \ERRORLOG. and \ERRORLOG.* - no dice.
Looking in this updated article for the new AMA, it doesn't seem to indicate that it's any different, even using DCRs.
I also see that we can likely use SQL agent to write errors to a windows event log, so we might pursue that if natively reading ERRORLOG isn't doable.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.