Finance | Project Operations, Human Resources, ...

Performance issue in PROD. How will I found rootcause without reproduce the issue in DEV

(2) Share

Report

Posted on by CU10121822-0

532

Dear team,

If I faced, any Performance issue in PROD. How will I found the root cause without reproduce the issue in DEV.

I mean to say, what is the best approach.

Kindly elaborate please.

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (6)

Answers (0)

Sort by

Suggested answer

Shaluma 369 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi,
Enable tracing for the affected user, Ask the user to execute the slow process, Stop the trace, Download and analyze using Trace Parser. please find the below URL for your ref.
https://d365ffo.com/2021/07/24/ax-d365fo-how-to-use-trace-parser-as-a-debugger/
.

Thanks,
If you found it helpful, please consider marking it as verified — it may be useful for others in the future!

Was this reply helpful? Yes No
André Arnaud de Cal... 306,276 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi,

The reply above from Shaluma is correct. You can use the Trace Parser to create a system event log and then start analyzing the details. Preferrable the user facing the issue should perform the recording and send the trace to a system administrator.

It is recommended to be able to reproduce the issue on another environment. In case you will apply a potential fix, you can then test the performance improvements without skipping tests and move it to a production environment.

Was this reply helpful? Yes No
CU10121822-0 532 on at

Like
a
(2)

Report
Copy link

Link copied!

Thanks Andre and Shaulma fir the response.

As per my knowledge, the performance can be happened due to some other reason as well. Like Environment issues, CPU consumption etc...

If required, where I can check this kind of issue in PROD.

Kindly elaborate pls.

Was this reply helpful? Yes No
Suggested answer

Subra 1,705 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi

Please check the below link to troubleshoot the performance issue.

https://kurthatlevik.com/2024/08/18/d365-performance-checklist-troubleshooting-and-resolving-performance-issues/

https://www.linkedin.com/pulse/introduction-d365-environment-monitoring-performance-using-okiemute

Thanks,
Subra

If this helped, please mark it as "Verified" for others facing the same issue

Was this reply helpful? Yes No
Suggested answer

Shaluma 369 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi,

Environment Monitoring and Performance troubleshooting using tools in Lifecycle Services,
https://www.linkedin.com/pulse/introduction-d365-environment-monitoring-performance-using-okiemute

Thanks,
Shaluma

If you found it helpful, please consider marking it as verified — it may be useful for others in the future!

Was this reply helpful? Yes No
André Arnaud de Cal... 306,276 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi,

Shaluma shared an older LinkedIn article about LCS environment monitoring. The monitoring options are being moved to Azure Application Insights, and not all details are available in LCS anymore.

I would start finding out what exact part of the process is slow using the Trace Parser. Here, you can also see the times consumed for executing coding and database actions. Still available on LCS today is the option to check for long-running queries and deadlocks. This can also help.

If you know what is slow, you can check how to improve it. E.g. change row-by-row actions to set-based actions. This will be way more effective and will reduce CPU usage as well.

So far, your question is broad and generic. Each performance issue can have its distinct root cause. E.g. Last year, I had seen long-running queries where an update of a single record took over 20 seconds. This was due to contention. It appeared that a batch job was scheduled three times running at exactly the same time, causing conflicts. By ensuring only one instance was scheduled, this solved the problem. Recently, I had seen another issue due to a wrong range in a while select. It looped unnecessarily some records where a lot of coding was executed.

Was this reply helpful? Yes No