-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable app insights on the client #179
Conversation
Now we enable and disable app insights using the presence of the connection string in the secrets file
1f511d2
to
126cc48
Compare
Code looks good, needs security test to be run before merge EDIT - Given the OWASP tests aren't working at the moment (and this change won't go to prod without them having been run) we should be ok to skip running the tests |
126cc48
to
22447a7
Compare
Now we enable and disable app insights using the presence of the connection string in the secrets file
22447a7
to
1b0be7c
Compare
Deploy multiple SSL Checks from using StatusCake
Now we enable and disable app insights using the presence of the connection string in the secrets file
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Closing and reopening on fixed branch |
User Story 139068: Build: connect App Insights to our Test or Dev environment
Enable client side telemetry to be sent to application insights. We are now tracking page view in addition to the requests we were already tracking.
Changes
Moved App insights initializer so it can be enabled in development mode. This means that developers can track events when running locally. This can be enabled or disabled by putting the connection string into the secrets file or by setting is as an environment variable.
Updated the Content security policy to allow for app insights script to load and for telemetry to be sent back to app insights.
Add the snippet to the layout to load it onto all files.
Checklist