Forum Discussion

Joe_Skup's avatar
Joe_Skup
7 years ago

Tuning a collector to work on a t2.micro EC2 instance?

I know that it is not exactly recommended/reliable to use a 1GB/1CPU Core machine to monitor...but it seems that installing a "nano" sized collector on a t2.micro AWS instance and having it just mo...
aws
collector
ec2
  • Joe_Skup's avatar
    Joe_Skup
    6 years ago

    Update- I found the solution:

    Edit agent.conf:
    1. collector.xxxx.enable=false on every unused/unneeded datasource collection mechanism.
    2. eventcollector.xxxx.enable=false on every unused/unneeded eventsource collection mechanism.
    3. sbproxy.pool.connections=25
    4. sbproxy.linux.threadPoolSize=60
    5. collector.snmp.threadpool=25
    6. discover.workers=5

    In my case, I pretty much am monitoring the collector machine only, and I've only left snmp, script & webpage-related collectors enabled and this seems to have done the trick.

    The last few configurations might not be necessary..but everything seems to be working fine with these configs..!

Joe_Skup's avatar
Joe_Skup
6 years ago

Update- I found the solution:

Edit agent.conf:
1. collector.xxxx.enable=false on every unused/unneeded datasource collection mechanism.
2. eventcollector.xxxx.enable=false on every unused/unneeded eventsource collection mechanism.
3. sbproxy.pool.connections=25
4. sbproxy.linux.threadPoolSize=60
5. collector.snmp.threadpool=25
6. discover.workers=5

In my case, I pretty much am monitoring the collector machine only, and I've only left snmp, script & webpage-related collectors enabled and this seems to have done the trick.

The last few configurations might not be necessary..but everything seems to be working fine with these configs..!