Java APM agents used in a production environment are consistently found to be disabled while no development environments exhibit this behavior Given that agents in both environments use the default…

Question

Options

• AEnable agent auto-restart in the controller Ul.
• BIncrease heap space for agent
• CDecrease worker thread count
• DEnable heap-storage-monitor-enabled setting on agent.

• A
  8% (2)
• B
  19% (5)
• C
  8% (2)
• D
  65% (17)

Explanation

One possible reason why Java APM agents used in a production environment are consistently found to be disabled while no development environments exhibit this behavior is that the production agents are running out of heap memory and crashing. This can happen if the production agents are monitoring a high volume of business transactions, metrics, or snapshots, and the default heap size is not sufficient to handle the load. To resolve this issue, you can enable the heap-storage-monitor- enabled setting on the agent, which allows the agent to monitor its own heap usage and automatically reduce the amount of data it collects when the heap usage reaches a certain threshold. This can help to prevent the agent from running out of memory and crashing. You can also adjust the heap-storage-monitor-threshold setting to specify the percentage of heap usage that triggers the data reduction. Alternatively, you can also increase the heap space for the agent by using the -Xmx option in the agent startup script, but this may require more resources from the host machine.

No community discussion yet for this question.