Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is.
As the Experience team is starting to track more analytics events through the ReportStream website, we need an App Insights key to test tracked events locally. This usually involves pulling the keys from a non-local environment -- one of the demo environments or even staging -- but a dedicated key for local development would make this much easier and would result in less test pollution on the analytics side for the live environments.
(This may also be a good sandbox environment for us to test Terraform changes in the future, but that's not the goal of this ticket.)
Describe the solution you'd like
Create a dev environment specifically for local development. In the event that storage is an issue, data retention can be set to the lowest possible values; when we're testing a new analytics event, we probably don't need more than a day or two in the past.
Describe alternatives you've considered
We could hardcode one of the demo(1|2|3) environment keys to use locally, but this value can change between deployments.
We've also considered using the staging key, but we don't want to conflate engineer testing events with onboarding events.
Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is.
As the Experience team is starting to track more analytics events through the ReportStream website, we need an App Insights key to test tracked events locally. This usually involves pulling the keys from a non-local environment -- one of the demo environments or even staging -- but a dedicated key for local development would make this much easier and would result in less test pollution on the analytics side for the live environments.
(This may also be a good sandbox environment for us to test Terraform changes in the future, but that's not the goal of this ticket.)
Describe the solution you'd like
Create a
devenvironment specifically for local development. In the event that storage is an issue, data retention can be set to the lowest possible values; when we're testing a new analytics event, we probably don't need more than a day or two in the past.Describe alternatives you've considered
We could hardcode one of the demo(1|2|3) environment keys to use locally, but this value can change between deployments.
We've also considered using the staging key, but we don't want to conflate engineer testing events with onboarding events.