How can I enable or disable ptrace in OneAgent 1.333, and how can I verify whether OneAgent is using ptrace?

[Nakazato_IIM]

[Edit from the Moderator: Translation from Google:

I am trying to find a way to enable or disable ptrace in a OneAgent 1.333 environment, but I haven't found a working method.
Here is what I have tested:

1. I opened the following configuration file:

/var/lib/dynatrace/oneagent/agent/config/ruxitagentproc.conf

2.I added the following item to the [general] section (using 'on' to enable and 'off' to disable):

enablePtrace off

3. I restarted OneAgent.

After the restart, I checked the configuration file again and found that the 'enablePtrace off' entry had been automatically removed.

Questions:

1. What is the supported method for enabling or disabling ptrace in OneAgent 1.333?
2. Is it expected behavior for the 'enablePtrace' parameter to be removed from 'ruxitagentproc.conf' after restarting OneAgent?
3. How can I verify whether OneAgent is actually using ptrace at runtime, rather than another monitoring mechanism?

I would greatly appreciate any relevant information or documentation.
]


OneAgent 1.333環境でptraceを有効または無効にする方法を調べていますが、有効な方法が見つかりません。

私がテストしたもの

1. 以下の設定ファイルを開きました。
   

   /var/lib/dynatrace/oneagent/agent/config/ruxitagentproc.conf
   

2. [general] セクションに以下の項目を追加しました（有効にするには on、無効にするには off を使用します）。

   enablePtrace をオフにする

3. OneAgentを再起動しました。

再起動後、設定ファイルを再度確認したところ、enablePtrace off のエントリが自動的に削除されていることがわかりました。

質問

1. OneAgent 1.333でptraceを有効化または無効化するためのサポートされている方法は何ですか？
2. OneAgentの再起動後にruxitagentproc.confからenablePtraceパラメータが削除されるのは想定される動作ですか？
3. OneAgentが実行時に他の監視メカニズムではなく、実際にptraceを使用しているかどうかを確認するにはどうすればよいですか？

参考になる情報や資料があれば大変ありがたいです。

[sujit_k_singh]

Hi @Nakazato_IIM 

ruxitagentproc.conf is regenerated from server-side config on restart that's why your manual enablePtrace off entry got wiped. It's not meant for persistent hand-editing.
enablePtrace isn't a documented/supported parameter in OneAgent's public config reference, so I can't confirm the correct syntax or behavior.
For supported config changes, use oneagentctl --get-agent-config / --set-agent-config instead of editing the conf file directly.
To check what mechanism is actually used at runtime, check the OneAgent logs (/var/lib/dynatrace/oneagent/log/) for that process — it logs whether it attached via LD_PRELOAD injection or ptrace.

Since this isn't in the standard docs, I'd suggest opening a support ticket with Dynatrace for a definitive answer on 1.333 behavior.

Thanks,

Sujit

[Nakazato_IIM]

@sujit_k_singh 

Thank you for your response.
I checked the help for `oneagentctl`, but neither “--get-agent-config” nor “--set-agent-config”
was listed as an available option.

Based on the above, I understand that modifying `ruxitagentproc.conf` directly may be difficult, but is there really no alternative?

[sujit_k_singh]

Hi @Nakazato_IIM 

Thank you for pointing that out. You're correct that oneagentctl --get-agent-config and --set-agent-config are not available options in your OneAgent version, so please disregard that part of my previous response.

I reviewed the public documentation again and still haven't found any documented or supported method for configuring ptrace via oneagentctl or by manually editing ruxitagentproc.conf in OneAgent 1.333.

Based on your testing, the enablePtrace entry is removed after restart, but I cannot confirm from the documentation whether this behavior is expected or whether the parameter is still supported internally.

At this point, I would recommend opening a Dynatrace Support case so they can provide an authoritative answer regarding:

Support for enablePtrace in OneAgent 1.333?

Expected behavior of ruxitagentproc.conf?
How to verify the monitoring mechanism used at runtime?

Thanks

Sujit