App Insights - Switched from instrumentation key to connection string #1558
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
babakamyljanovssw
temporarily deployed
to
staging
GitHub Actions
Inactive
babakamyljanovssw
had a problem deploying
to
staging
GitHub Actions
Failure
babakamyljanovssw
temporarily deployed
to
staging
GitHub Actions
Inactive
babakamyljanovssw
temporarily deployed
to
staging
GitHub Actions
Inactive
babakamyljanovssw
temporarily deployed
to
staging
GitHub Actions
Inactive
babakamyljanovssw
temporarily deployed
to
staging
GitHub Actions
Inactive
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Relates to #1522
This pull request involves updating the configuration for Application Insights across multiple files to use a connection string instead of an instrumentation key. Additionally, it includes a minor version update for the
applicationinsightspackage inpackage.json.Note: Added new
APPLICATIONINSIGHTS_CONNECTION_STRINGto production and staging environmentsApplication Insights Configuration Update:
.github/workflows/template-build.yml: ChangedAPPINSIGHTS_INSTRUMENTATIONKEYtoAPPLICATIONINSIGHTS_CONNECTION_STRING.gatsby-browser.js: Updated the configuration to useconnectionStringinstead ofinstrumentationKey.gatsby-node.js: Modified the environment variable check and warning message to useAPPLICATIONINSIGHTS_CONNECTION_STRING.connectionString:src/components/acknowledgements/acknowledgements.jssrc/components/bookmark/bookmark.jssrc/components/comments-not-connected/comments-not-connected.jssrc/components/header/header.jssrc/components/profile-content/profile-content.jssrc/components/reaction/reaction.jssrc/components/sidebar-categories/sidebar-categories.jssrc/components/signin/signin.jssrc/pages/orphaned.jssrc/pages/profile.jssrc/pages/user/index.jssrc/templates/category.jssrc/templates/rule.jsDependency Update:
package.json: Updated@microsoft/applicationinsights-webfrom^3.3.2to^3.3.3andapplicationinsightsfrom^3.2.1to^3.3.0.