• Forums
    • Public Forums
      • Community Connect
      • Dynatrace
        • Dynatrace Open Q&A
      • Application Monitoring & UEM
        • AppMon & UEM Open Q&A
      • Network Application Monitoring
        • NAM Open Q&A
  • Home /
  • Public Forums /
  • Application Monitoring & UEM /
  • AppMon & UEM Open Q&A /
avatar image
Question by Sreerag M. · Apr 20, 2013 at 09:21 AM ·

Best practice in Agent Group definition?

Hi,

We have a web application with two tiers in the presentation layer(web layer). these two tiers are in same technology but running different code. I would like to know the best way to define agent groups for this application. Should we define one agent groups for each tier or define one agent group for entire web layer and apply sensors for both tier in one agent group?

Thanks,

Sreerag

Comment

People who like this

0 Show 0
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

3 Replies

  • Sort: 
  • Most voted
  • Newest
  • Oldest
avatar image

Answer by Abhijeet G. · Aug 06, 2013 at 07:34 PM

Hello,

Thoughts on the similar lines...

Is it a best practice to even split each of the outbound calls from a particular tier as a separate Agent Group?

Idea is to visually see the complete end-to-end application flow (using Transaction Flow) to determine how much time is spent within the tier and the outbound calls separately from within that tier.

 

 

Thanks,

 

Abhijeet G

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Rob V. · Apr 21, 2013 at 04:05 PM

Sreerag,

As Andi mentions, you should look at your app from a functional point of view (looking at application "Tiers") and break it into agent groups along those lines. There are a couple of reasons for that. One, as you mention, is that sensors are placed and configured at the agent group level.. Second, the agent groups define the view of the Transaction Flow. Surely you would like to differentiate the time spent in one FE tier from the other FE tier, and in the time spent communicating from each of those tiers to the backend. This will happen if you make each separate frontend tier its own agent group. Another benefit is that you can set filters to just look at transactions that pass through a particular tier. Bottom line is that I recommend you consider having two FE agent groups based on your description.

There is no performance penalty with having multiple agent groups. The only downside (and this is changing) is that it is sometimes tedious when you have settings that you want to apply to all agent groups. In those cases you would need to make the changes in each group. Small price to pay for the benefits listed above.

Comment

People who like this

0 Show 1 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image Sreerag M. · Apr 23, 2013 at 12:00 AM 0
Share

Thanks for the recommendations Rob and Andi. Looks like defining Agent Groups for each tier is the best way to go.

avatar image

Answer by Andreas G. · Apr 20, 2013 at 11:24 AM

Hi

Agent Groups should be considered like Application Tiers. In your case it seems that these two agents actually belong to the same tier (Frontend) - so it would make sense to create one agent group and use sensors that will work for both agents.
The AGent Groups also play a big role in the Transaction Flow - which is the visual representation from your PurePaths.
If your two Frontend Agents "talk" with each other then I assume you also want to see the transaction flow showing the transactions going into each agent - in this case I recommend two creating Agent Groups.

Andi

Comment

People who like this

0 Show 1 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image Sreerag M. · Apr 21, 2013 at 12:39 PM 0
Share

Hi Andi,

The two sections of the frontend doesn't talk to each other but we have around 40 servers in the frontend (half of them running different code than the other half). Would you recommend to put the agents from all these servers into one Agent Group? Will there be any issues in applying custom sensors when we group two frontend tiers into one. Some sensors won't make any sense to half of the agents in the agent group.

Also would like to know if there is any benefit in using less number or Agent Groups than creating one agent group for each code type so that agents from all server running the same code belong to one agent group. Is there a limit in the Agent Groups in DynaTrace for a profiles or is there a recommended number. Does having more agent groups impact the DT system performance?

Thanks,

Sreerag

How to get started

First steps in the forum
Read Community User Guide
Best practices of using forum

NAM 2019 SP5 is available


Check the RHEL support added in the latest NAM service pack.

Learn more

LIVE WEBINAR

"Performance Clinic - Monitoring as a Self Service with Dynatrace"


JANUARY 15, 3:00 PM GMT / 10:00 AM ET

Register here

Follow this Question

Answers Answers and Comments

3 People are following this question.

avatar image avatar image avatar image

Forum Tags

dotnet mobile monitoring load iis 6.5 kubernetes mainframe rest api dashboard framework 7.0 appmon 7 health monitoring adk log monitoring services auto-detection uem webserver test automation license web performance monitoring ios nam probe collector migration mq web services knowledge sharing reports window java hybris javascript appmon sensors good to know extensions search 6.3+ server documentation easytravel web dashboard kibana system profile purelytics docker splunk 6.1 process groups account 7.2 rest dynatrace saas spa guardian appmon administration production user actions postgresql upgrade oneagent measures security Dynatrace Managed transactionflow technologies diagnostics user session monitoring unique users continuous delivery sharing configuration alerting NGINX splitting business transaction client 6.3 installation database scheduler apache mobileapp RUM php dashlet azure purepath agent 7.1 appmonsaas messagebroker nodejs 6.2 android sensor performance warehouse
  • Forums
  • Public Forums
    • Community Connect
    • Dynatrace
      • Dynatrace Open Q&A
    • Application Monitoring & UEM
      • AppMon & UEM Open Q&A
    • Network Application Monitoring
      • NAM Open Q&A