• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 59 subscribers
  • Views 2121 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Remote Foglight Agent Manager

georgios.giannoutsos
over 5 years ago

We were in process of using one of the existing FGLAM as a remote Foglight agent manager to monitor 10 VM’s.

 There are some concerns:

 Looking at the Exist FGLAM( which will  become the remote Foglight Agent Manager for the  10 VM’s) I see the fglam in the list with top consumption's see image attached.

  • The customer is concerned  about taking this approach . They are afraid that it will consume much more..
  • According to tech support  the remote Foglight Agent Manager can monitor  about 150 Devices

  What is your opinion

  • 0 over 5 years ago

    Hi Georgios,

    What type of agent will be monitoring the 10 vm''s? The Netmonitor agent or something else? It's hard to tell from the screenshot, but it looks like it is using ~ 400 MB currently.

    You can put a cap on the memory used by the fglam by editing the jvm settings and restarting the service.

    Foglight Agent Manager, JVM Settings **

    Edit the baseline.jvmargs.config file located under the <Agent Manager installation directory>\state\default\config\
    directory

    For 1024MB, add the following lines:

    vmparameter.0 = "-Xms1024m";
    vmparameter.1 = "-Xmx1024m";

    I normally don't set mine under 1 GB but the Xmx parameter is the "max" and so that is roughly what it should stop at. You could set the Xms parameter lower (the starting point) and let it grow up to the Xmx value.

    regards,

    -Darren

  • 0 over 5 years ago

    What I would do is set the JVM parameters, deploy the 10 new IC agents, and monitor. Might be a good idea to monitor the fglam host too and watch for memory related alarms.