You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This api is using GET for read, POST for insert, PATCH for update and DELETE for delete - as I understand it a basic webapi.
However - when I use TrackDepencency I would like the Blazor mini-site to be a bit more up to the task. As it is for now it seems to show dependency stats based upon the url (removing any query params (thumbs-up))
On the one hand I would like to be able to capture the full url in the dependency tracking - but on the other having dependency tracking "stats" be without <> and <>
I thought of having the stats be presented on the Blazor size be by either "url" (as it is now) OR by dependency name. If this functionality was available I could rather easily set the name to something like
Hi Daniel,
I'm currently starting using TinyInsights.Maui in my mobile app.
However I'm not getting how to use Dependency Tracking especially with the api I'm calling.
Any api call will be structured like this
https://<>.site.com/api/entity/list
https://<>.site.com/api/entity/<>
etc...
This api is using GET for read, POST for insert, PATCH for update and DELETE for delete - as I understand it a basic webapi.
However - when I use TrackDepencency I would like the Blazor mini-site to be a bit more up to the task. As it is for now it seems to show dependency stats based upon the url (removing any query params (thumbs-up))
On the one hand I would like to be able to capture the full url in the dependency tracking - but on the other having dependency tracking "stats" be without <> and <>
I thought of having the stats be presented on the Blazor size be by either "url" (as it is now) OR by dependency name. If this functionality was available I could rather easily set the name to something like
"PATCH *.site.com/api/entity/" while having the url (data) be "https://firstcompany.site.com/api/entity/9f046867-aee2-47fc-9d79-2189be62b1ed"
By having the Blazor site utilising both by name and by url I think this would enable some much appreciated functionality.
I know I could do it myself leveraging custom queries - but I would think it would be nicer if baked in !
Any thoughts ?
The text was updated successfully, but these errors were encountered: