• Forums
    • Public Forums
      • Community Connect
      • Dynatrace
        • Dynatrace Open Q&A
      • Application Monitoring & UEM
        • AppMon & UEM Free Trial
        • AppMon & UEM Open Q&A
        • AppMon & UEM Plugins
      • Data Center RUM
        • DC RUM Open Q&A
        • Enterprise Synthetic Monitoring
      • Synthetic Classic
        • Synthetic Classic Open Q&A
        • Synthetic Classic EAP Feedback
      • BSM Open Q&A
      • Dynatrace Open Q&A en Español
  • Home /
  • Public Forums /
  • Application Monitoring & UEM /
  • AppMon & UEM Open Q&A /
avatar image
Question by Yc M. · Dec 04, 2014 at 09:14 AM ·

May I use Collector Group for Server Fail Over?

Presentation1.jpg

 

Hi There,

 

I see the new function of dT6 regard collector group that allow me to setup fail over among difference collectors. My question is if I can use this function for dT server fail over?  The scenario is  as above,

-Agents connect to single configured collector in collector group.

-Collectors in one collector group are report to two difference server

-One dT Server goes down, can agent continue work with other collectors which report to another dT server in sames collector group?

 

Thanks

YC

Comment

People who like this

0 Show 0
10 |2000 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

5 Replies

· Add your reply
  • Sort: 
  • Most voted
  • Newest
  • Oldest
avatar image

Answer by Reinhard B. · Dec 05, 2014 at 12:43 AM

YC,

no you can't do that. Collectors cannot report to more than one server.

Reinhard

Comment

People who like this

0 Show 3 · Share
10 |2000 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users
avatar image Yc M. · Dec 05, 2014 at 01:28 AM 0
Share

Hi Reinhard,

 

I meant I include  difference collectors in one collector group. For example , I have collector A and collector B belongs same collector group. Collector A report to Server A, Collector B report to Server B. If Server A goes down, can the agents report to collector A switch to collector B.  I just looking for a HA solution of dT server within dynaTrace technology.

 

Thanks

YC

avatar image Reinhard B. &. Yc M. · Dec 05, 2014 at 09:22 PM 0
Share

Still you can't do that. Collectors that might report to different servers might also have different configurations from those servers.
The collector will now know that it's server is down and tel the agent to connect to another collector that is configured on a second server.
I know we had a few customers that did failover on a lower level for the dynatrace server (IP failover) but the dynatrace server per se doesn't have HA capabilities (considering session filestorage that would need to be accessed r/w by two servers, database access etc..)

Reinhard 

avatar image Yc M. Reinhard B. ♦ · Dec 06, 2014 at 01:49 AM 0
Share

Thanks at first.

 

If the servers are configed identically and we are OK with losing some historical data in session, then the server fail over is not possible?

 

Best

YC

 

avatar image

Answer by Rob V. · Dec 06, 2014 at 02:47 AM

Hi YC,

You can configure dT server failover, but as Reinhard mentions this happens at a low level, and has nothing to do with dynaTrace. It is a somewhat tedious task that has to be done by someone who knows how to set up active/passive clusters in something like MSCS. At a high level, it would go like this... you'd have two servers, A and B. Only one would be active at a time. There would be a VIP established pointing to the active server. The easiest (simplest) way to go about it would be to have the dynaTrace home directory on a SAN, able to be shared by both servers A and B. That would ensure that all critical config files, etc, were shared by each server. Also, the session storage would need to be on a SAN as well, again sharable by both servers.

The trick would be identifying to the cluster software what it means for the dT server to be down on the primary (active) server, so that it could fire up the dT server process on the passive server and re-point the VIP to the newly active server. As Reinhard mentioned, dT has no inherent HA functionality or cluster-awareness.

This should work for you if you pay attention to all the clustering details. dynaTrace would have no idea that you are doing this.

Rob

 

Comment

People who like this

0 Show 0 · Share
10 |2000 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users
avatar image

Answer by Avelina K. · Dec 10, 2014 at 10:59 AM

I have collectors group setup and when the main collector that has been used in Monitors settings goes down all monitors stop working till I configure them on-line collector instead.

Please advise.

Comment

People who like this

0 Show 0 · Share
10 |2000 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users
avatar image

Answer by Dave M. · Dec 10, 2014 at 02:54 PM

I don't think it is possible to have fail over for a monitor collector.  Agents can fail over between collectors in a group, but monitors have to be set up to run on a single collector at a time and there is no "standby" arrangement possible at this point.  .

Comment

People who like this

0 Show 0 · Share
10 |2000 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users
avatar image

Answer by Avelina K. · Dec 11, 2014 at 05:53 AM

Thank you, Dave. It is not very good news. If collector goes offline all our monitors won't work.

Comment

People who like this

0 Show 2 · Share
10 |2000 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users
avatar image Andreas G. &. · Dec 11, 2014 at 06:08 AM 0
Share

A best pratice is to install separate collectors that execute monitors. Separate from those collectors that capture data from agents. With that you ensure that your collectors are not impacted by a situation where a lot of new agents are starting and consuming a lot of CPU and with that maybe impacting monitor execution.

Also - if a collector looses the connection to the server it will buffer the data. Once the connection is re-established the data will be sent. In that respect you dont often really loose data

avatar image Dave M. · Dec 11, 2014 at 11:01 AM 0
Share

You might be able to create a "hot standby" collector that could be activated via a script that pushes the appropriate configuration files from some shared repository and starts the "standby collector".  Just brainstorming here...

Your answer

Hint: You can notify a user about this post by typing @username

Up to 10 attachments (including images) can be used with a maximum of 52.4 MB each and 262.1 MB total.

Welcome to the
Dynatrace Community Forums

Check out the Forum User Guide and Forum Guidelines to learn how to get started.

Community Member of the Month
April 2018

Announcing Dynatrace's Community Member of the Month for April 2018, Babar Q.! Click here to read more!

Live webinar: Web Performance Optimization and Web Frontend Engineering with Dynatrace

Learn key aspects on how Dynatrace helps you in your day to day web performance activities. Take a deep dive look into Real User Monitoring and the Synthetic capabilities of Dynatrace.
Thursday, April 26, 2018
Register today!

Live webinar: Web Performance Optimization and Web Frontend Engineering with Dynatrace

Learn key aspects on how Dynatrace helps you in your day to day web performance activities. Take a deep dive look into Real User Monitoring and the Synthetic capabilities of Dynatrace.
Thursday, April 26, 2018
Register today!

DC RUM 2018 Beta is here!

Improve your operational efficiency and collaborate more effectively while addressing tightening security requirements. Have an early taste of what we have cooked up for 2018!
Learn more!

Follow this Question

Answers Answers and Comments

3 People are following this question.

avatar image avatar image avatar image

Forum Tags

upgrade nginx java diagnostics dotnet docker 6.5 ios appmonsaas browser agent database sensor 7.1 performance warehouse chart hybris 6.3+ services production web performance monitoring transactionflow test automation incidents measures business transaction plugins migration php javascript android processes server dashlet monitoring purelytics nodejs 6.2 splunk rest api system profile uem appmon framework appmon 7 license mobile monitoring collector installation adk messagebroker web services apache guardian appmon plugin iis dashboard rest webserver reports 7.0 kibana mainframe client 6.1 configuration forum user guide continuous delivery sensors security documentation agent web dashboard alerting auto-detection load window dynatrace apm 6.3 administration oneagent
  • Forums
  • Public Forums
    • Community Connect
    • Dynatrace
      • Dynatrace Open Q&A
    • Application Monitoring & UEM
      • AppMon & UEM Free Trial
      • AppMon & UEM Open Q&A
      • AppMon & UEM Plugins
    • Data Center RUM
      • DC RUM Open Q&A
      • Enterprise Synthetic Monitoring
    • Synthetic Classic
      • Synthetic Classic Open Q&A
      • Synthetic Classic EAP Feedback
    • BSM Open Q&A
    • Dynatrace Open Q&A en Español