• 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 Dan A. · Feb 10, 2013 at 05:15 PM ·

Collector configuration

This question is related to the setting in the dynaTrace Server -> Services (General Tab).

Where I work we have a pretty simple dynaTrace 5 installation meaning we don't have that many agents connected and usually will troubleshoot some issue with a team, disable profile to release agent license, and move on to another team that requires help with their application. We have tons of applications we support. The dynaTrace server is on the same server as the dynaTrace client and collector.

With that said, can we use the option "Allow Agent Connections to dynaTrace Server"? What is the point of using a collector if it's on the same box as the server. And on top of that we never have more than 5 agents connected and no more than 2 profiles active.

Right now it's actually unchecked but wondering if I should probably check it...which is the default setting after install.

Thank you!
Dan

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.

1 Reply

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

Answer by Roman S. · Feb 11, 2013 at 07:24 AM

Hi Dan,

My recommendation would be to always use a separate collector rather than the in-process one you can enable with that option.

Reasons are that when the dynaTrace server runs into a major GC or comes under heavy load because a lot of analyzer threads are triggered by users you still have the collector to accept data from incoming agents, allow new agents to connect and so on.

The number of agents can be low - it is how much transactions they produce that is the key factor if the embedded collector works or not.

What's your concern here - we do install the out-of-process collector automatically, so it's just another service to start and one option (amongst many) to change in the server settings after install...

Best, Roman

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