Bruno

My feedback

  1. 11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  API Management » API management experience  ·  Flag idea as inappropriate…  ·  Admin →
    Bruno supported this idea  · 
    Bruno commented  · 

    The memory consumtion of the cache instance would be useful too.
    And in documentation, the precision of the behavior of APIM when total memory cache is reached whould be usefull and comfortable (I suppose in this case you get a cache "miss" rather than an error, but I not totaly sure either).

  2. 87 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  API Management » Policies  ·  Flag idea as inappropriate…  ·  Admin →
    Bruno supported this idea  · 
  3. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  API Management » Security  ·  Flag idea as inappropriate…  ·  Admin →
    Bruno supported this idea  · 
    Bruno commented  · 

    In a general way, a way to access (in gateway logs for example) to client side transport security protocol (TLS 1.0 , 1.1 ...) would be great to be able to better plan our TLS security updates.

  4. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  API Management » Policies  ·  Flag idea as inappropriate…  ·  Admin →
    Bruno commented  · 

    Hi I made further tests and in fact I ws wrong about URL and return code. If you get Request.URL just after backend call you get the info even if backend url was changed before the call. I don't know why I figured it was a static info (the service url configured).
    The same for response.ReturnCode I can get it before it is changed by a policy.
    So the improve could be limited to have only backend call duration (but I could calculate it via policy too).
    So I suggest you archive this request. Thanks again for your interest.

    Bruno commented  · 

    Hi, thanks for your interest. In APIM native gateway logs you have a lot of interesting informations about backend call like backendMethod, backendUrl, backendResponseCode, backendTime, backendProtocol. You're right there is some information in Request or Response, like service URL or responce code. But the response code or backend url can be manipulated by process (by example a policy can change backend url, a backend response call can be reinterpreted ...). In this case I'm not sure that the context will provide the right information. The return code seems to be the final one (the one finally returned by APIM). In gateway logs, the informations are clearly distinctive and richer. I would be very interested to have this clear level of information in policies (for my custom logging for example).

    Bruno shared this idea  · 
  5. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  API Management » Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    Bruno shared this idea  · 
  6. 35 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  API Management » Integration  ·  Flag idea as inappropriate…  ·  Admin →
    Bruno commented  · 

    For my case we never recreate the overall instance when deploying an API or other operaiton on APIM. But in case of a need to restore an overall APIM (serious outage, return back to a previous version, need to duplicate on another region ...) we would need to be able to keep the same adress.

    Bruno supported this idea  · 
    Bruno commented  · 

    It would be great to be able to re provisioning an overall APIM instance (for exemple with Terraform) and be able to assign the public IP (usefull for reset of dev environments for example).

    Even in production env, according to documentation, you are not sure your public IP will not change in case of major outage.

  7. 10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  API Management » API management experience  ·  Flag idea as inappropriate…  ·  Admin →
    Bruno supported this idea  · 
  8. 37 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  API Management » Policies  ·  Flag idea as inappropriate…  ·  Admin →
    Bruno commented  · 

    The problem is that JSON don't support comments where XML does.

  9. 139 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  API Management » Policies  ·  Flag idea as inappropriate…  ·  Admin →
    Bruno supported this idea  · 
  10. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  API Management » API management experience  ·  Flag idea as inappropriate…  ·  Admin →
    Bruno shared this idea  · 
  11. 68 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  3 comments  ·  API Management » Policies  ·  Flag idea as inappropriate…  ·  Admin →
    Bruno supported this idea  · 
  12. 59 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  API Management » Policies  ·  Flag idea as inappropriate…  ·  Admin →
    Bruno supported this idea  · 
  13. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  API Management » Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    Bruno commented  · 

    A more flexible behavior would be to be able to choose any property of API context to be added to Log analytics by configuration, for example "context.Operation.Name" (via "overide menu" of Azure Monitor in API settings).

    Bruno shared this idea  · 
  14. 116 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  4 comments  ·  API Management » Pricing  ·  Flag idea as inappropriate…  ·  Admin →
    Bruno supported this idea  · 
  15. 93 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  API Management » Developer portal  ·  Flag idea as inappropriate…  ·  Admin →
    Bruno commented  · 

    As a workaround you can assign your "API products" to users groups by using "Access control" on "API products".
    Users can still "sign up" but they don't see any API or product on the portal until you move them user to the correct user(s) group(s). Even better, users don't see all APIs but only those authorized for their group.

  16. 288 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  13 comments  ·  API Management » Pricing  ·  Flag idea as inappropriate…  ·  Admin →
    Bruno supported this idea  · 
  17. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure portal » Resource management  ·  Flag idea as inappropriate…  ·  Admin →
    Bruno shared this idea  · 

Feedback and Knowledge Base