Telemetry for Finance and Operations
My previous post 1 & 2 covered the purpose and requirement gathering for moniroting solution respectively. This post covers configuring telemtry in F&O.
Set up an Application insights resource in Azure
The feature 'Monitoring and Telemetry' is on by default in the new versions.
Configure environments to link to the correct Azure application insights resources
Configure the type of telemetry that must be sent to application insight.
Configure F&O environments and link to Application Insights:
Environments are classified as
Dev
Test
Production
Link the correct environments from System administration > Monitoring and Telemetry parameters.
In the monitoring tab, enter the environment Id and select the type . Make sure the correct environment Id is provided. Giving a TEST environment id in Dev box would lead to incorrect results.
Environment ID can be found in LCS
Next step in the 'Application insights Registry' to enter the environment type, instrumention key or connection string. If Connection string is entered, instrumentation key is optional.
Connection string is from Azure application insight instance.
Final steps in this configuration is to setting the type of telemetry to be captured.
In my next post, we will understand about configuring Azure application insights.
Connecting ERP, Analytics, and AI for Future-Ready Enterprises | D365 F&O | Microsoft Fabric
1moThanks for sharing
Microsoft Dynamics 365 F&SCM, Azure, Power Platform Technical Architect | MVP Alumni | 3x Microsoft MVP | 2x Microsoft MCT
1moThanks Anita additional you can add Operational Insights along with App Insights which will cover all the CRT calls from Retails and capture in Azure App Insights
Microsoft Dynamics 365 F&O Senior SCM Functional Consultant lead & Corporate Trainer, Conducting Mocs & Software kills exposure & Motivational Speaker, Inspiring of career growth for Candidature & Career Guidance
1moThanks for sharing, Anitha