web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

Check out the Community Spotlight Video Series
News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Performance timer, Tra...
Finance | Project Operations, Human Resources, ...
Suggested Answer

Performance timer, Trace parser, Aplication insight, Telematory tool for performance monitoring

(1) ShareShare
ReportReport
Posted on by CU10121822-0 872

Hi team,

For the performance monitoring we used performance timer,Trace parser, Aplication insight, Telematory tools in D365FO 

In which sequence we should go … I mean which one come first, then next one so on…

Pls advise, thanks

Categories:
Dynamics 365 Finance
I have the same question (0)
  • Suggested answer
    SajeedMullaji Profile Picture
    SajeedMullaji 684 on at

    @CU10121822-0 
    The correct sequence is Application Insights → Performance Timer → Trace Parser. Always work from macro to micro — environment level first, then session level, then code level. Reversing this wastes hours debugging X++ when the real issue is a database lock.

    Phase 1 — Application Insights and Telemetry — start here
    When a user reports the system is slow — do not touch the UI or code yet. Query Application Insights or LCS Environment Monitoring. Look for SQL DTU spikes, blocking queries, deadlocks, and long-running batch threads. This tells you where and when the problem is happening — systemic database issue or isolated process.

    Phase 2 — Performance Timer — once you have isolated the slow process
    Append &debug=develop to your D365 URL. Reproduce the exact slow steps. The timer splits execution time between Client, Network, and Server. If Client time is high — the issue is UI rendering. If Server time is high — the issue is X++ or SQL. This tells you who is to blame before you open a single line of code.

    Phase 3 — Trace Parser — only after Performance Timer confirms Server is the bottleneck
    Capture an ETL trace using Settings > Trace while executing the slow process. Open in the Trace Parser desktop utility. Sort by Inclusive/Exclusive time in the Call Tree. Trace Parser pinpoints the exact X++ method causing the delay, highlights inefficient database roundtrips like while select loops without set-based operations, and exposes missing indexes.

    Skip Phase 1 and you risk spending days optimizing code that was never the problem.

    If it helps, mark as answered

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Check out the Community Spotlight Video Series

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the July Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
SajeedMullaji Profile Picture

SajeedMullaji 531

#2
Martin Dráb Profile Picture

Martin Dráb 303 Most Valuable Professional

#3
CU10121822-0 Profile Picture

CU10121822-0 290

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP
License usage reporting (in-app and PPAC) with Entra dynamic groups

Product updates

Dynamics 365 release plans