在多个Web应用程序和服务之间共享AI密钥? [英] Share AI key between between multiple web apps and services?
问题描述
我们有一个包含多个Web应用程序，Web API和Windows服务的应用程序套件.今天，每个webapp/api/服务都有一个工具密钥，每个环境还有一个.这有点混乱，我们认为在每个环境中只使用一个共享密钥会更好.
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.
是否还有其他方法可以聚合和可视化来自多个键的AI数据，还是应该将我们所有的键都移到一个共享的键上?
Are there other ways to aggregate and visulize the AI data from multiple keys, or should be move all our keys into one shared?
致谢
拉西
推荐答案
通常，有一些注意事项.为了说明，我们假设您有两个组件" A和B
In general, there are several considerations. To illustrate, let's assume you have two "components" A and B
-
可见性范围-您是单独还是一起分析有关A和B的遥测.将资源放到单个资源(单个iKey)中，即可跨A和B进行汇总(例如，一起查看对A和B的请求总数).另一方面，要单独查看(例如，仅向A提出请求)，则必须应用过滤器，这可能会影响我们提供的开箱即用旅程的价值.如果您选择保持分离，则仍然可以在仪表板上混合并匹配"，但不能汇总.我们正在努力启用
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
访问控制-您是否希望某些人仅访问有关A而不是B的遥测
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
这篇关于在多个Web应用程序和服务之间共享AI密钥?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
