Skip to main content

LCS Monitoring and diagnostic


Telemetry data is the base of the information for environment monitoring and used in three use cases 
  • Monitoring
  • Diagnostics
  • Analytics
Let me go through for each subject one by one quickly and explain which has been used for which purpose.

Monitoring

Monitoring in basic just for monitoring your environment if is in active state, up and running. This monitoring can be done in two states 
  1. Availability monitoring 
  2. Health monitoring

Diagnostics

High detail of telemetry data is used for user created issues to identify the real cause of the issues. In addition the SQL data can be added to identify the performance issues too.

Analytics

Another usage of telemetry data. This part is can be done only by Microsoft now. Microsoft tracks the feature usage and performance through Power BI.


Access LCS Monitoring and Diagnostics portal

Navigate to LCS and select your project.
Select necessary environment from the Environments section.
On the opened page find the Environment Monitorıing 



Comments

Popular posts from this blog

D365 F&O Transportation Module (TMS)

      I would like to give some summary information on the TMS module. TMS module helps you manage your both inbound and outbound operations.   You can plan your shipments, routes, loads, appointments and drier check in/outs.  You can see the fastest or less expensive routes as an example with to assign rates and calculate with engines. Also you can manage and reconcile charges. Please find the Microsoft Documentation for the Module below: https://docs.microsoft.com/en-us/dynamics365/supply-chain/transportation/transportation-management-overview Also I like the video series below from Michael Cobbin which give detail for the TM module from Tech Talk: https://www.youtube.com/watch?v=gqGKgiDEQLk https://www.youtube.com/watch?v=gqGKgiDEQLk&list=PLaKeZD0fHWIp8zD088_6svgMZ5v1CmJGz&index=8 https://www.youtube.com/watch?v=9-gGUxeQSAc&t=1408s https://www.youtube.com/watch?v=gqGKgiDEQLk&t=1456s

Vendor Invoice Posting Date (Pending Invoices)

  On the pending invoice posting form, there are different dates that may need to be filled. But there are two fields that may be mixed up. Invoice Date and Posting Date.  -Invoice Date is the date of the real invoice and most of the calculations(cash discount, exchange rates etc.) are using this date. It is optional not to fill this information unless on the parameters it is set to be filled mandatory. (Account payable > Setup > Account payable parameters -> Require document date on vendor invoice) - Posting Date is the date the transaction is posted to GL. This may differ from the invoice date in many circumstances. For example the invoice may arrive to posting user after the invoice date, period is closed etc. This field is used for calculations if invoice date is not filled. To fill the invoice date is mandatory and it is set to today as default when invoice is created but can be changed before posting. In some circumstances, users may need to change or bulk ...

Default Descriptions

  In D365 F&O there are ways to manage the descriptions. You may find the list below: Manual:  You may fill the description in the journals per line before you post the transactions. you may fill both for account and offset account. If you define a description before, you may select one from the list. Automatic:  Some transactions are auto created to the journals or on transactions default from the hard coded codes, like asset lease management and some functionalities in TMS management. Default Descriptions:  You can setup default descriptions by transaction type (sales order invoice, Po invoice, revaluation etc). On the transaction types you can use static (constant) text and/or variables. Specific Cases:  There are specific cases like revaluation. If you define the text during to run in revaluation process, system uses that information instead of to use the definition on the default description. Or if there is no setup on default descriptions, cancel opera...