Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Empty resource is getting published in Choreo analytics when invoking a GraphQL Subscription #12737

Open
wasuradananjith opened this issue Mar 22, 2022 · 1 comment
Labels
4.x.x feature/GraphQL Subs issues found during GraphQL subscriptions feature implementation Priority/Normal Type/Bug

Comments

@wasuradananjith
Copy link
Contributor

Description:

An empty resource is getting published multiple times in Choreo analytics when invoking a GraphQL Subscription operation

Steps to reproduce:

  1. Setup Choreo Analytics as mentioned in [1].
  2. Create a GraphQL API [2].
  3. Invoke a GraphQL Subscription [3]. (Refer to the below for a sample invocation screenshot)
    image
  4. The corresponding analytics data will be shown in the Choreo Analytics portal as shown below.
    screencapture-console-choreo-dev-organizations-wasurawattearachchi-insights-traffic-2022-03-22-17_45_43
  5. The marked record in the above screenshot contains an empty resource and an API method which is not meaningful at all.

Affected Product Version:

APIM 4.1.0-PreRC

[1] https://apim.docs.wso2.com/en/4.1.0/tutorials/scenarios/scenario7-analytics/#step-1-set-up-analytics
[2] https://apim.docs.wso2.com/en/4.1.0/design/create-api/create-a-graphql-api/
[3] https://apim.docs.wso2.com/en/4.1.0/consume/invoke-apis/invoke-apis-using-tools/invoke-an-graphql-api-using-the-integrated-graphql-console/#invoke-a-graphql-subscription-operation

@wasuradananjith wasuradananjith added Type/Bug Priority/Normal feature/GraphQL Subs issues found during GraphQL subscriptions feature implementation 4.x.x labels Mar 22, 2022
@wasuradananjith
Copy link
Contributor Author

I was able to identify a reason for the above issue.

I followed the below steps when further exporling.

  • I created a new GraphQL API with Subscriptions
  • Invoke it several times
  • Then when I check the API Resource Usage Summary I was able to see the blank record that was added 15 times.
    image
  • Then I check the API Errors section and was able to identify the total number of failures was also 15.
    image
  • Hence, we can see that a blank record was added for each failure. Need to decide whether this is the expected behaviour and fix it if needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4.x.x feature/GraphQL Subs issues found during GraphQL subscriptions feature implementation Priority/Normal Type/Bug
Projects
None yet
Development

No branches or pull requests

1 participant