MSNev
commented
3 years ago Yes you can, as long as all of the subscription(s) all end up in the same region (and therefore get sent to the same location -- without the server sending service side redirects).
Then there are 2 simple methods
- Before you call appInsights.track[XXX}() calls, simply set the "iKey" property on the event to the teams event (
evt.iKey = "xxx") - You can also add a telemetryInitializer which does the same, although at this level the default iKey will already have been assigned to the
instrumentationKeyprovided during initialization. Soooo, you could "replace" thetelemetryItem.iKeyvalue with the value you want (probably based on some other value that you temporarily assign to the telemetry item -- sort of like setting the iKey above)
What this doesn't do for you is that all of the automatic events (PageView, Instrumented XHR or fetch) requests etc will still use be assigned the default instrumentationKey and these will only get sent once (which is fine -- most of the time, except for maybe the Page view for different subscriptions). For the ajax (XHR, fetch) dependency calls this is where the telemetryInitializer option would work better as you can switch the iKey based on the URL.
Another option
You can create "multiple" appInsights instances and use them directly, this is easiest when consuming via the NPM so that all teams could use the same code and just create multiple instances, but it can also be done via the snippet loader you would need multiple "snippets" with each one defining it's own configuration and each with their own INSTRUMENTATION_KEY AND also specifying the name config value which will assign the global instance (on window) to this name and then each team would have their own instances.
So the following will create 2 global objects window.team1AppInsights and window.team2AppInsights
<script type="text/javascript">
!function(T,l,y){<!-- Removed the Snippet code for brevity -->}(window,document,{
src: "https://js.monitor.azure.com/scripts/b/ai.2.min.js",
crossOrigin: "anonymous",
onInit: function (sdk) {
sdk.addTelemetryInitializer(function (envelope) {
envelope.data.someField = 'This item passed through my telemetry initializer';
});
}, // Once the application insights instance has loaded and initialized this method will be called
name: "team1AppInsights",
cfg: { // Application Insights Configuration
instrumentationKey: "YOUR_INSTRUMENTATION_KEY - TEAM1"
}});
</script>
<script type="text/javascript">
!function(T,l,y){<!-- Removed the Snippet code for brevity -->}(window,document,{
src: "https://js.monitor.azure.com/scripts/b/ai.2.min.js",
crossOrigin: "anonymous",
onInit: function (sdk) {
sdk.addTelemetryInitializer(function (envelope) {
envelope.data.someField = 'This item passed through my telemetry initializer';
});
}, // Once the application insights instance has loaded and initialized this method will be called
name: "team2AppInsights",
cfg: { // Application Insights Configuration
instrumentationKey: "YOUR_INSTRUMENTATION_KEY - TEAM2"
}});
</script>Note: I've not tried this recently, so if you encounter an issue with this let us know as that would be considered a bug.
FredUK
Karlie-777
We are leveraging the ApplicationInsights-JS package in a micro UI architecture where many teams are contributing to overall user experience. These teams would like to be able to monitor and instrument with their own instance of App Insights subscription.
Would like to be able to instantiate or maintain a collection of app insights subscriptions on client side and be able to push data to any of them based on configuration.
We have tried to implement all telemetry to a single app insights instance, but storage threshold is becoming an issue.
Is there any way to be able to selectively push telemetry data to multiple subscriptions in the same application.