dynaTrace 6.0 Collector Configuration does not have option to setup Collector Group.
We have just changed our Test Center Edition of dynaTrace over to the new 6.0 version. We are trying to setup the Collector Groups via the Server Settings in the client. The documentation shows a bottom section of the collectors section that would allow us to set the groups. This configuration section is not available to us (See below screenshot). Is there anything we need to do to be able to configure collector groups?
Hi,
For the UI problem, please open a support case with a Client logfile or full supportarchive, it seems somehow the Client could not create the user interface components in your case.
Thanks... Dominik.
I guess this is a resizing problem of this dialog as you have that many entries in that table. Can you try changing the size of this dialog and see if these additional controls show up? I will check with our UI Developers if this could be a layout bug
Andreas,
I attempted to resize the window vertically across two 1920x1080 screens, to no avail. The window remained without the bottom pane. Is there a way to manually add the collector groups in the meantime?
Thanks,
Brian
hi Brian,
in the meantime you could change the collector.config.xml (located in <install_dir>/collector/conf/) manually.
you'll find a " groupname="" " attribute there, which points to an empty collector group name per default. just changing it to the desired collector group name should do the trick.
however, don't forget to restart the collector to read the config file.
best,
Christian
Thanks Christian! We will use this to configure the collector groups in the mean time.
Christian,
After testing this method of setting the collector groups, it does not seem to work. The connected agent seems to correctly know how many collectors are in the collector group, but then it just writes the name of the connected collector that many times to the collectorlist file (see screenshot). I think this is probably a bug with the program.
Thanks,
Brian
Hey Brian,
Can you try setting the Bind Address property in one or more of your other collectors and restart? Another customer had a similar issue to what you describe and that seemed to help.
Rick B
I'm adding the same comment here as on the other forum entry:
putting an address in the bind address is basically the manual specification of the collector address. this might be necessary for very specific network setups where the collector cannot figure an address of itself that the agent can resolve.
however, it would be very interesting why the collectors should figure the same name of themselves resulting in a list of 5 identical entries.
Rick,
Thanks! This seems to have fixed the issue. I will open a case with compuware so that they can investigate the issue.
Thanks,
Brian
FYI: I double-checked, there is already a fix by now which has to go through our build and testing stages.
hi Brian,
could you please send us a system information archive with agent, collector & server log files so we can take a short look at it.
I also recommend to open a support ticket for this behavior to be investigated and also to have the right people involved.
best,
Christian
