Best practices request: One or many appinsight accounts? RRS feed

  • Question

  • Dear Appinsights Pros,

    We are developing a lot of web apps, conatiners, APIs and so on. And we like to use appinsights to gain insights on the solutions  

    A discussion in the team that arose these days was: should we link all APIs agains a single app insight account or should we add an appinsight per API?

    If the second is recommended  how to we get an overview over all appinsights to see them in a kind of umbrella dashboard  

    Thanks allot 

    Kind regards 


    Monday, November 26, 2018 7:05 PM

All replies

  • Hello Benedikt,

    Choosing one vs. many resources will depend on the implementation of the system you're trying to setup telemetry for.

    For instance, if some of these APIs talk to one another / proxy one another via HTTPs, then AI will automatically correlate those for you. By opening any AI resource with an issue / slowdown detected in such a case, you'll see end-to-end transaction that crossed all involved APIs regardless of which AI resource their data landed in (if you have access to those resources in Azure Portal, of course). Here is the example of such distributed transaction and map views.

    Alternatively, if most of these resources are independent and won't talk to one another, then to have a single pane of glass you may either go with:

    - Single resource for all APIs and then build Azure Dashboards (or AI Workbooks) via Metrics Explorer or Analytics queries by slicing on API name;

    - Multiple resource (one per API) and then build Azure Dashboards (or AI Workbooks) via ME and Analytics queries by slicing on resoruce name instead. Or, simply make each chart represent its own resource.

    Dmitry Matveev

    Tuesday, November 27, 2018 1:06 AM