• 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 Mark C. · Sep 24, 2014 at 03:53 AM ·

Collector group evaluation criteria? [forqandawebinar]

I read in the documentation for v6.0 that agents configured to connect to one of the Collectors within a group are equally distributed within the group.  But what is the basis for that distribution?  Is this strictly based on count of attached agents per Collector, or (preferably) on a more sophisticated set of criteria, such total purepaths or total events over a certain period of time?  Do administrators have some means of controlling the weight of those various factors that come into play in this decision?

Also, the doc goes on to say that if a Collector in a group terminates, the connected Agents will reconnect to another Collector within the same group.  But if that Collector group has a total of three or more Collectors, on what basis does the agent choose the Collector to which to connect?

Thanks...
-- Mark 

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.

2 Replies

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

Answer by Andreas G. · Sep 24, 2014 at 04:58 PM

Great question: even though rick answered the question I will bring it up today in the webinar

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 Rick B. · Sep 24, 2014 at 08:32 AM

Hi Mark,

In the current iteration (6.0) the collector group feature is handled by randomization.  A secondary impact of this feature, though, is that collectors share their instrumentation metadata, so it is now possible to put a real load balancer in front of your collectors and allow agents to failover without missing transaction context data.  In this way, you can control how the agents are load balanced to your collectors (smile)

Hope that helps,

Rick B

Comment

People who like this

0 Show 5 · 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 Mark C. · Sep 24, 2014 at 09:11 AM 0
Share

Ok, thanks.

avatar image John K. · Oct 01, 2014 at 05:34 AM 0
Share

Richard,

  Since you mention you can now put the collectors behind a load balance does that mean I can define a collector group across different servers?   And if yes....could one be say Windows and one a flavor of Unix?

Currently our agent point to FQDNs of the servers a particular collector is on.  We would like to create a dns entry for a vip and point the agents to that if we can.

avatar image Rick B. John K. · Oct 01, 2014 at 05:38 AM 0
Share

Hi John: Yep!  Just make sure to put all the collectors behind the same vip in the collector group, again so they share metadata and can translate events from all connected agents no matter who handled the initial instrumentation.  Make sense?

Rick B

avatar image John K. Rick B. · Oct 02, 2014 at 01:39 AM 0
Share

 

Rick,

  Yes it does.  I may have more questions when we get closer to attempting in our test environment but for now I have 1.   

  1.  We will probably have collectors of the same name and ports on different servers defined to the same group...Is that OK.  The use the LB.  

   

avatar image John O. Rick B. · Oct 04, 2014 at 06:23 AM 0
Share


If you put these behind a load balancer and they are in the same collector group, do you need to anything to disable the collector level balancing?  Here is what we fear will happen:

Example:

Agent connects to the vip, which passes it onto collector1

Collector 1 responds "you need to reconnect to collector2"

Agent is now connected to collector2 directly, bypassing the vip

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

5 People are following this question.

avatar image avatar image 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