• 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 Michael B. · Jul 25, 2014 at 03:54 AM ·

Collector dns with multiple A records doesn't load balance

With the new collector failover logic we are hoping to rid ourselves of our load balancers all together. However there seems to be a deficiency in the initial connection logic that prevents this. The agent will not try to connect to all address returned from an alias even with multiple A records, it will only try to connect to the first one. This means that if the "first" collector isn't up even though all the other ones are, the agent will not connect to any of them. It's even sillier since the log file is telling me that you know about the multiple addresses but are just using the first one. If this isn't fixed we need to bring the load balancer back solely for making sure our initial connection works!

nslookup result

Name:    dyndevcollectors6

Addresses:  10.20.40.173

          10.20.40.174

Agent bootstrap log file:

2014-07-24 12:39:27 [00000148] warning [native] Connection::connect(): Address resolution for 'dyndevcollectors6' returned multiple addresses. Using first returned: 10.20.40.174

 

 

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 Markus P. · Jul 29, 2014 at 01:12 AM

Hello,

if the collector groups are set up correctly (so all collectors are in the same group), the dynaTrace agent should behave as requested. So if the first collector is not reachable it should try the next one.

In the agent directory there should be a subdirectory "conf" with files like "collectorlist.*". This is the list of collectors the agent should try to connect to. You should see at least on entry per collector of the defined collector group.

Maybe it would be better to open a support ticket with a full support archive to investigate the problem.

Best regards,

Markus

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 Andreas G. · Jul 28, 2014 at 06:43 PM

Hi Michael

I will forward this to the engineering team that worked on the load balancing implementation

Andi

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.

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

2 People are following this question.

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