• 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 Christopher A. · Apr 09, 2015 at 08:26 AM ·

Load balancing doesn't work...

... because the host returned by the collector is not correct.

In our case, we have two physical servers (preprodcoll01 and preprodcoll02 )with 5 collector instances on each one of them. The five instances on the first server are overloaded while there are no agents on the second server.

When we took a closer look, we noticed it was because the host name being returned by the collector seems to be a short version while our agents need the fully qualified name to connect.

For example, it returns "preprodcoll01" while it should return "preprodcoll01.mycompany.com" instead.

Is there a way we can force the collector to use a different host name(like the "external host name" configuration for the server)?

Thanks in advance!


Chris

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.

4 Replies

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

Answer by Christopher A. · Apr 10, 2015 at 08:56 AM

I am happy to report that bind addresses and changing the hostname both seem to have done the trick as my agents are slowly starting to connect to all my collectors and not only to only one.

Thanks everyone for the help!

Comment

People who like this

0 Show 2 · 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 Dave M. · Apr 10, 2015 at 09:24 AM 0
Share

Glad the bind addresses worked for you.  I also saw something innovative recently where someone used a bind address of 127.0.0.1 for a Monitor Collector to (I assume) prevent regular agents from accidentally being pointed at it.  I thought this was a nice practice.  Has anyone else seen or done this?  Does it seem like a good idea?

avatar image Christopher A. Dave M. · Apr 10, 2015 at 09:32 AM 0
Share

I'd say it's a very good idea indeed! This way, we are sure that no agents are going to connect to it (unless they are local).

avatar image

Answer by Christian S. · Apr 10, 2015 at 03:25 AM

hi everybody,

David is right, that's actually exactly what those bind addresses are for.

as taken from the doc (Collectors):

"The Collector name that is sent to the Agent for storage in its CollectorList file is the detected host name of the Collector. If an IP address (multiple NICs in the machine) or fully qualified domain name is required for the Agent to connect to the Collector, you can choose to configure a Collector Bind Address. This bind address will be sent to the Agent and populated in its CollectorList file. To configure this, switch from the Basic to the Advanced Configuration in the dialog."

HTH,
Christian 

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 Reinhard W. · Apr 09, 2015 at 12:55 PM

Actually I think a network service as the collector should ALWAYS return the FQDN (if it can be detected safely) as you can never assume for proper short DNS resolution.

What you probably can do Chis is to make sure the "hostname" command on the machines returns the full qualified name instead of the short name on the machines...

Comment

People who like this

0 Show 6 · 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 Christopher A. · Apr 09, 2015 at 01:08 PM 0
Share

Thanks for the info Reinhard! Is there no other way we can change this?

I mean, there is an option for the server but not for the collectors?!

avatar image Dave M. Christopher A. · Apr 09, 2015 at 01:28 PM 0
Share

I believe you can go to Settings/dynatrace Servers/Collectors/Advanced Configuration and add a bind address. 

avatar image Christopher A. Dave M. · Apr 09, 2015 at 01:32 PM 0
Share

Doesn't the bind address bind the collector to only specific hosts?

avatar image Reinhard W. Dave M. · Apr 09, 2015 at 01:33 PM 0
Share

That's not what Chris is looking for. If the first collector in a loadbalanced configuration tells the client to connect to "thishostname" but the agent can't resolve "thishostname" there should be an option to set that the colelctor should return the full qualified name "thishostname.domain.my".

avatar image Dave M. Reinhard W. · Apr 09, 2015 at 01:39 PM 0
Share

I thought that was what the bind address did.

We had similar issues with EasyTravel and used the bind address to fix it:

Re: Can't get Collector Group to work on 6.0 with EasyTravel

SUPDT-4550

But maybe I am missing something.

Thanks,

dave

 

avatar image Reinhard W. Dave M. · Apr 09, 2015 at 02:40 PM 0
Share

Actually that might be a good workaround putting the FQDN in there and hoping it resolves locally to the collector as well. Otherwise I'd just put the IP adress in there and hope that the balanced collector forwards this to the agents.

avatar image

Answer by Andreas G. · Apr 09, 2015 at 12:43 PM

Going to move this to the Dynatrace Open Q&A forum as this is currently posted in the general Community Open Q&A

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

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