Is there an easy way to log the requests? #431
|
When using the SDK, we see the dependency call to the dataverse like so
But as you can see, it doesn't tell us what it is actually doing in that call. Is it querying data, or updating data etc. Is there any quick and easy way to log extra information out, like the Fetch XML included in the query. I'm looking for an out of the box way to do it with the SDK rather than rolling my own for now. |
Replies: 1 comment · 3 replies
|
Yes, This message changes depending on if a session ID is present or not, and the type of message being sent. Additionally if you use the "ExecuteOrganizationRequest" extension, you can pass your own message that will be tagged in this log. |
|
Hey This is how I wire up the ServiceClient
Not sure what you mean by Then I make calls like so. public async Task<EntityCollection> RetrieveMultipleAsync(QueryExpression qe)
{
try
{
var result = await ((ServiceClient)client).RetrieveMultipleAsync(qe);
return result;
}
catch (Exception)
{
throw;
}
}Where would I add the extra logging? That RetrieveMultipleAsync appears to call "ExecuteOrganizationRequest" in its code behind. |
|
In your case, the logger you're passing in is assigned a log level, this is the level that logs will reported to whatever write sink you have attached to the logger. I misused the term "channel" in-place of LogLevel ( I think of these has channels as they can be handled independently, sorry for the confusion there). the Dataverse ServiceClient, when executing the statement you have above will log the following on the Trace LogLevel: when it starts and when it completes. this allows you to see the start and end of the request along with the duration. If you used "ExecuteOrganizationRequest( , )" you can add a custom tag to each log event written to trace. To see ExecuteOrganziationRequest you need to add Microsoft.PowerPlatform.Dataverse.Client.Extensions namespace. Does that help? |
|
Thank you for your advice |
In your case, the logger you're passing in is assigned a log level, this is the level that logs will reported to whatever write sink you have attached to the logger. I misused the term "channel" in-place of LogLevel ( I think of these has channels as they can be handled independently, sorry for the confusion there).
Full documentation on Ilogger is here
the Dataverse ServiceClient, when executing the statement you have above will log the following on the Trace LogLevel:
when it starts and