none
AppInisghts Resource - Grouping Applications into there own AppInsighst Resources or ALL in one resource?

    Question

  • When adding a new application to AppInsights (Status Monitor) would you just have 1 x AppInsights Resource and add ALL your applications to that resource? Or separate them based on application with each application having its own Resource like below?

    ***Cant add image yet***

    The reason I'm looking to use different resources is when it comes to sharing published dashboards, as we need to separate what Applications each team viewing the dashboards see, as I don't want them having to select roles and exclude Applications they don't support.

    Looking at the details listed here ***Cant add URL yet***

    number 3 states - "Configure the resource where you want to see the results in the Application Insights portal. (Normally, it's best to create a new resource. Select an existing resource if you already have web tests or client monitoring for this app.)" This would imply you have an AppInsights Resource for each Application, but all these Resources can be added to the same Resource Group/Location.

    Would really like some advice on best practice on how to utilise AppInsighst Resources to manage Applications in this way. Also how this would impact cost?


    Friday, February 8, 2019 11:36 AM

Answers

  • Cost currently depends on the amount of the data ingested, so having one or many resources won't impact cost as the amount fo the data stored stays the same.

    If you'd like an easy way for each team to look at only their application data, having resource per app makes sense. There is still a possiblity to see the connected services on the Application Map view if one has permissions to access all necessary AI resources. Distributed transaction view (former event details view) will also include communications of one service to another if those were part of the overall transaction that team investigates. So, there is almost no drawback of having multiple resources.

    Having one resource / one Instrumentation Key is easier from the resource management perspective - there is only one thing to worry about. 


    Dmitry Matveev

    Friday, February 8, 2019 8:09 PM
    Owner

All replies

  • Adding the image that the customer provided while engaging with @AzureSupport on Twitter: 



    Original tweet thread: https://twitter.com/MrAsh74/status/1093816201007063040/photo/1

    Thanks,
    @AzureSupport

     
    Friday, February 8, 2019 12:27 PM
  • Cost currently depends on the amount of the data ingested, so having one or many resources won't impact cost as the amount fo the data stored stays the same.

    If you'd like an easy way for each team to look at only their application data, having resource per app makes sense. There is still a possiblity to see the connected services on the Application Map view if one has permissions to access all necessary AI resources. Distributed transaction view (former event details view) will also include communications of one service to another if those were part of the overall transaction that team investigates. So, there is almost no drawback of having multiple resources.

    Having one resource / one Instrumentation Key is easier from the resource management perspective - there is only one thing to worry about. 


    Dmitry Matveev

    Friday, February 8, 2019 8:09 PM
    Owner
  • Thanks for clarifying Dmitry.
    Monday, February 11, 2019 9:25 AM