-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dexter seems to fail when loading a customer application (UWM, MuleSoft Application) #128
Labels
Comments
and a fragment of a ConsoleLog showing the failure happening and stopping the run.
|
In hindsight, the customer application configuration may contain sensitive info. Sending it straight to AppD (BradH) for debugging support. |
I thought @bradhjelmar fixed that already. This is for the metrics lookup when something in the entity name is null. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
While doing a SaaS controller migration planning exercise for United Wholesale Mortgage, we took configuration and metadata dumps for a non-production and production controller.
Non-production DEXTER extracts worked without issue
Production repeatedly failed, stopping in the middle of dumping an app in the middle of their applications at an app called "Mulesoft".
Dexter throws and error, then stops processing, and stops generating CSV files.
We have extracted the application configuration using ConfigExporter, hoping that the problem will replicate in another controller after loading. (JSON attached)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
DEXTER stops generating output files and cancels remaining job steps including report generation.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Logs
Add logs from the program execution https://github.com/Appdynamics/AppDynamics.DEXTER/wiki/Log-Files
Reports
Include any produced reports that you have issues with
The text was updated successfully, but these errors were encountered: