API Mesh Queries | Community
Skip to main content
R
rkmk107
Level 2
June 8, 2023
Question

API Mesh Queries

  • June 8, 2023
  • 2 replies
  • 2040 views

Hello,

Need clarification on following queries related to API Mesh:
1. Can we fetch internal logs of the API mesh. For e.g. what was the request payload sent to the source systems (Open API, GraphQL, JSONSchema)

2. Is the request payload visible if we enable includeHttpDetails option in mesh configuration.

3. Could we get details regarding licensing report. Is license bundled when we procure license for AEM as Cloud Service or Adobe Commerce.
4.Is there is any Rate limitation. How may number of maximum requests can be sent say per minute, per second.

5. Do we need to submit the Project (App Builder) for review to use API mesh for Production usage.

6. Is retry support present in API Mesh? 

7. Dashboards available for monitoring API mesh.

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    2 replies

    adobechat
    adobechat
    Level 5
    June 14, 2023

    Hi @rkmk107 ,

    API Mesh is not a product or feature offered by Adobe, you can probably raise a feature request but its not there yet.

    Hope this answers your question.

    Thanks
    Madhan

    sarahxxu
    Adobe Employee
    sarahxxuAdobe Employee
    Adobe Employee
    June 15, 2023

    I think he's referring to this functionality that is a part of Adobe Developer App Builder https://developer.adobe.com/graphql-mesh-gateway/.

     

    I've forwarded the question to the team and they'll post a response soon! 

     

    cc @rkmk107 

      R
      rkmk107Author
      Level 2
      June 15, 2023

      Yes @sarahxxu , you are correct. All these questions are related to Adobe API Mesh (https://developer.adobe.com/graphql-mesh-gateway/gateway/).

      C
      Adobe Employee
      cparticaAdobe Employee
      Adobe Employee
      June 15, 2023

      Hi @rkmk107 

      Hopefully these responses finds you well:

      1. To be able to troubleshoot and diagnose API Mesh during development staging and production, we are working on a features to resolve this problem so a developer can view what's going in inside API Mesh when it's forming requests for each source and responses for both payloads and headers. This set of features are on our roadmap to be released this year.

      2. The formed request payload for each individual source is not visible using `includeHttpDetails`, but that's a good idea for a feature request.
      There is a workaround if you want to access the request payload. You can use the `beforeAllHooks` context (`context.request` or `context.req`). https://developer.adobe.com/graphql-mesh-gateway/gateway/hooks/#beforeall-hooks which has access to fetch which forms the request. You can integrate a hook with a logging system which would get you that payload.

      3. Any existing license of AEM as Cloud Service or Adobe Commerce would get you App Builder entitlement therefore API Mesh entitlement.

      4. A generic rate limit is in place to accommodate mesh users meaning and won't be directly throttled if you reach the limit, Having two licenses AEM + Commerce certainly increases your limit. The package we offer is set to fit your traffic needs, most integrations usually don't reach it, and it can be increased upon request.

      5. The submission review to prod is needed for several checks like security or fair usage analysis.

      6. API Mesh doesn't retry, but if such a feature is needed, we can incorporate it as we are actively doing active feature enhancements.

      7. Better dashboards for monitoring API Mesh will also be available in the next half of this year as an enhancement to the insights tab which is present now in Developer Console. These enhancements will include real-time data and will include tracking uptime & traffic, detecting anomalies detection and thresholds alerting, checking endpoints for possible errors, etc

       

        Terms & ConditionsAccessibility statement

        Loading footer...