问题
We got an app suite that consist of multiple web apps, web api's and windows services. Today we have one instrumentation key per webapp / api / service, in addition one per environment. This gets a bit messy and we're thinking it would have been better to only one shared key per environment.
Are there other ways to aggregate and visulize the AI data from multiple keys, or should be move all our keys into one shared?
Regards
Larsi
回答1:
In general, there are several considerations. To illustrate, let's assume you have two "components" A and B
Visibility scope - do you analyze telemetry about A and B separately or together. Putting into a single resource (single iKey) will enable you to aggregate across A and B (e.g. see a total number of requests for A and B together). On the other side, to view separately (e.g. just requests to A), you will have to apply filters, which may impact the value of out of the box journeys we provide. If you choose to keep separate, you can still "mix and match" on dashboards, but not aggregate across. We are working to enable
Access control - do you want certain people only access telemetry about A and not B
Pricing - as we charge per app, you should consider this aspect
Lifecycle - you may want your telemetry containers to match the topology of your deployment artifacts
回答2:
You can use a dashboard in order to organize your data. Dashboard can contain metrics from different applications so your data will be very organized in one page.
You can read more about dashboards here: https://azure.microsoft.com/en-us/documentation/articles/app-insights-dashboards/
Thanks, Yair
来源：https://stackoverflow.com/questions/39265633/share-ai-key-between-between-multiple-web-apps-and-services