Application Insights

Welcome to the Azure Application Insights UserVoice site. This site is for suggestions and ideas for all aspects of Application Insights such as our SDKs, Web tests, Analytics, etc. We look forward to hearing from you!

The Application Insights team

How can we improve Application Insights?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Return Export ID on Application Insights Continuous Export creation

    Currently, creating a Continuous Export via the API or Go SDK returns a list of all continuous export configurations on success.

    It would be better if it returned only the export configuration just created, or only the Export ID for the configuration just created, so the user knows the Export ID of the new export configuration.

    Please see https://github.com/Azure/azure-sdk-for-go/issues/4745 for more details.

    2 votes
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for the valid suggestion. Your feedback is now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.

  2. application insight rest api - allow filter on ingressTimestamp

    Currently the rest api does not allow to do the filter using "le", "ge" etc. IngressTimestamp which is part of CustomDimension item. I guess this is because it is treating ingressTimestamp as string field. It allows for eq operator but does not allow le gt etc. This is useful for pulling the incremental data from the application insight. we cannot rely on the timestamp field because some records are back filled. if we rely on timestamp to do the incremental extract then we miss some records

    1 vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.

  • Don't see your idea?

Feedback and Knowledge Base