[ ] question about the decisions made in the repository
What is the current behavior?
Navigating through the app will track the appinsights pageViews properly so it sends the url in the track request but it sends the operationName tag incorrectly in that track request. It sends the url in the tag which was initially requested. So if we navigate to "ourdomain.com/help" page initially and we continue to use the website and navigating around it will send "/help" in the operation.name tag all the time. Then if we reload the site at another url it will send that url in the operation name from here.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
Enable angulartics2 appinsights provider so it fires a pageView on every route change and check the Azure Portal Application Insights's Browser blade and you will see that only the initial url shows up here and every track request is displayed under that no matter what was the url for these requests.
What is the motivation / use case for changing the behavior?
We cannot really profile or inspect the routes if we see every route under the "/" operation for instance.
I'm submitting a ...
[X] bug report
[ ] feature request
[ ] question about the decisions made in the repository
What is the current behavior? Navigating through the app will track the appinsights pageViews properly so it sends the url in the track request but it sends the operationName tag incorrectly in that track request. It sends the url in the tag which was initially requested. So if we navigate to "ourdomain.com/help" page initially and we continue to use the website and navigating around it will send "/help" in the operation.name tag all the time. Then if we reload the site at another url it will send that url in the operation name from here.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Enable angulartics2 appinsights provider so it fires a pageView on every route change and check the Azure Portal Application Insights's Browser blade and you will see that only the initial url shows up here and every track request is displayed under that no matter what was the url for these requests.
What is the expected behavior? If you look at what happens if you use a non SPA you will see that every route is displayed at the Azure Portal in the list of operations. So if we are using a single page app we should see every route in the operations list. This is how we can change the operation.name tag: https://stackoverflow.com/questions/48508883/how-to-set-application-insights-operation-name-from-javascript
What is the motivation / use case for changing the behavior? We cannot really profile or inspect the routes if we see every route under the "/" operation for instance.
Environment: