It would be great to see raw body request on analytics. Good for monitoring restful api calls (for example json payloads)307 votes
We are exploring how to implement this feature without compromising privacy. Thank you for all the feedback!
- Matt, Product Manager
The average response time metric is not very useful if it is counting signalr persistent connections. I can't filter out these requests in the default dashboard graphs and it's a pain to filter it out in every single graph I create. There needs to be a way to ignore certain patterns from being tracked.91 votes
Thank you all for sharing the feedback and upvoting for this feature. It is something being reviewed internally by the team and will be considered in the next wave of planning.
When an exception happens and the details are captured on Application insight, it would be great if POST parameters were available as well.
This feature can be turned off for certain pages via configuration r even posting an extra parameter like Ignore Post Parameters.
This will make sure sensitive application data like login information is not captured.
This feature can only work when a http POST ends up with a 500 error to assist debugging application, to make sure huge data is not captured and never used.31 votes
Thank you for the feedback, team is reviewing the item to prioritize it accordingly with other priority features for the semester. We will continue to revisit it and update the status accordingly. Thank you
We'd like to use Application Insights with our native (Win32) server application written in C++, as well as our Win32 desktop application (C++).
Without C++ support we can't build a full stack solution based on Application Insights.17 votes
I’m interested in hearing more about your C++ scenarios. If you have a few minutes to chat, please shoot me an email at email@example.com.
- Matt McCleary, Product PM
There should be a priority level that indicates the relative priority of the data.
The priority level of a tracked item should be possible to set on an item by item basis, or by more general declarative rules.
High priority data should be retained for longer time and care should be taken to make sure no high priority data is lost anywhere.
Example of use case:
You might want to mark events when a user change/request a new password longer than a metric of time taken for a storage request.13 votes
Having different retention policies for different telemetry items is a very interesting feature request. Enabling this is fundamentally non-trivial, so please keep upvoting and including the use cases where this is necessary. Please keep in mind that you can today ensure retention longer than 90d by using continuous export to archive subsets of the telemetry to external storages/data warehouses of your choice.
-AppInsights Product Management
- Don't see your idea?