search

umbraco / Umbraco.Heartcore.Issues

3 stars 1 forks source link

Better insights about made REST API/GraphQl and webhook calls #61

Open wvankesteren-ax opened 2 years ago

wvankesteren-ax commented 2 years ago

Issue description

In order to monitor e.g. performance and workflow it would be very handy to see which rest api, etc. calls are made and how many (statistics). This way it can easily been seen whether e.g. there is a loop going on retreiving data. (see support ticket 71621)

sitereactor commented 2 years ago

Thanks for the suggestion! We'll add it to our backlog and report back here once its matured and scheduled for an upcoming sprint.

wvankesteren-ax commented 2 years ago

see also support ticket 73615, where all GraphQL queries where not working anymore, due to one misconfigured Media type. perhaps this could be made visible in the insights.

sitereactor commented 2 years ago

I understand the issue, but the challenge with that type of misconfiguration is that it's very context specific. When doc types or media types are used in an inheritance structure the parent becomes a composition in Umbraco and thus an Interface in GraphQL. Some times that might be as intended while at other times not desirable.

One idea could be to have some kind of GraphQL type/schema info or indicator in the Umbraco Backoffice to make it more transparent and obvious.

wvankesteren-ax commented 2 years ago

all kinds of insights are welkom and hugely appreciated

Outlook voor Androidhttps://aka.ms/AAb9ysg downloaden

From: Morten Christensen @.> Sent: Tuesday, September 20, 2022 5:11:34 PM To: umbraco/Umbraco.Heartcore.Issues @.> Cc: Willem Jan van Kesteren @.>; Author @.> Subject: Re: [umbraco/Umbraco.Heartcore.Issues] Better insights about made REST API/GraphQl and webhook calls (Issue #61)

I understand the issue, but the challenge with that type of misconfiguration is that it's very context specific. When doc types or media types are used in an inheritance structure the parent becomes a composition in Umbraco and thus an Interface in GraphQL. Some times that might be as intended while at other times not desirable.

One idea could be to have some kind of GraphQL type/schema info or indicator in the Umbraco Backoffice to make it more transparent and obvious.

— Reply to this email directly, view it on GitHubhttps://github.com/umbraco/Umbraco.Heartcore.Issues/issues/61#issuecomment-1252505175, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AWM567SZAOFEOLHELBSKM7DV7HH2NANCNFSM53NRBSJQ. You are receiving this because you authored the thread.Message ID: @.***>

jmf-umbraco commented 9 months ago

Just to give a quick update on this issue (I know it's a been a while!) we are currently considering enhancing the Cloud usage dashboard for Heartcore to include number of requests made to our delivery APIs - GraphQL and REST, but potentially also the management API.

Note we're not intending to add much complexity here - you will only be able to see aggregate data, not individual requests.

We don't have a timeframe on this functionality, but will update this issue when we have more information. Thanks!