Add support for AIM SSC.

[umaannamalai]

Support server side configuration of AIM settings in NR1

Precedence:
If ai_monitoring.enabled is present in the connect response, this value MUST take precedence to override the ai_monitoring.enabled value and fallback on using the value from collect_ai. For example, if collect_ai is False, and ai_monitoring.enabled locally is True, the agent would ultimately disable AI Monitoring. If both collect_ai is False and ai_monitoring.enabled is True in the connect response, ai_monitoring.enabled would ultimately enable AI Monitoring. If HSM is enabled, the appropriate AI monitoring settings SHOULD be set appropriately in the connect response. As a safeguard however, agents SHOULD also enforce HSM mode on AI settings they receive from the connect response.

[github-actions]

✅MegaLinter analysis: Success

Descriptor	Linter	Files	Fixed	Errors	Warnings	Elapsed time
✅ ACTION	actionlint	9		0	0	1.07s
✅ MARKDOWN	markdownlint	7	0	0	0	1.34s
✅ PYTHON	ruff	1065	0	0	0	1.18s
✅ PYTHON	ruff-format	1065	0	0	0	0.36s
✅ YAML	prettier	23	0	0	0	1.65s
✅ YAML	v8r	23		0	0	6.75s
✅ YAML	yamllint	23		0	0	0.73s

Notices

📣 MegaLinter 9.5.0 is out! Discover the new features and security recommendations in the release announcement. (Skip this info by defining SECURITY_SUGGESTIONS: false)

See detailed reports in MegaLinter artifacts

Show us your support by starring ⭐ the repository

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.06%. Comparing base (6b6dc03) to head (1fe803a).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1793      +/-   ##
==========================================
+ Coverage   81.98%   82.06%   +0.07%     
==========================================
  Files         216      216              
  Lines       26796    26806      +10     
  Branches     4242     4245       +3     
==========================================
+ Hits        21970    21999      +29     
+ Misses       3355     3340      -15     
+ Partials     1471     1467       -4     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[hmstepanek]

Shouldn't this be agent_config instead of server_side_config?

[hmstepanek]

Do we need to do a pop here instead of a get to ensure it doesn't loop over this same setting and override the value out of order in the code below?

[umaannamalai]

collect_ai actually isn't sent up in the agent_config block. It is its own key within the connect response payload.

I can add a pop for collect_ai. The call to apply_config_setting(settings_snapshot, name, value) in the server_side_config loop shouldn't actually affect any logic with ai_monitoring.enabled since it's looking for the name collect_ai. However, it isn't necessary to store the value of collect_ai in the settings_snapshot if we've already done the override on line 1663 so I can get rid of it.

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request