[ZBX-21870] Extra fields of nested objects are logged to audit log details by the frontend Created: 2022 Nov 04  Updated: 2025 Mar 19

Status: READY TO DEVELOP
Project: ZABBIX BUGS AND ISSUES
Component/s: API (A)
Affects Version/s: 6.4.0beta2
Fix Version/s: 7.0.12rc1, 7.2.6rc1, 7.4.0beta1 (master)

Type: Problem report Priority: Trivial
Reporter: Vladimirs Maksimovs Assignee: Vladimirs Maksimovs
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File audit_log.diff    
Issue Links:
Sub-task
depends on ZBXNEXT-6998 Implement audit for API host READY TO DEVELOP
Team: Team C
Sprint: Sprint 94 (Nov 2022), Sprint 95 (Dec 2022), Sprint 96 (Jan 2023), Sprint 97 (Feb 2023), Sprint 98 (Mar 2023), Sprint 99 (Apr 2023), Sprint 100 (May 2023), Sprint 101 (Jun 2023), Sprint 102 (Jul 2023), Sprint 103 (Aug 2023), Sprint 104 (Sep 2023), Sprint 105 (Oct 2023), Sprint 106 (Nov 2023), Sprint 107 (Dec 2023), Sprint candidates, S2401
Story Points: 1

 Description   

After ZBXNEXT-6889 was developed the internal fields became visible in details of audit log report. These internal fields represents a primary key fields of the database tables, where are stored the data of the nested objects of the base API object, e.g. tags, macros.

Example: When new tag was added to template, the primary key of the tags table is loged in audit log details: template.tags[670].hosttagid: 670.

To make the audit logging consistent with server, there is necessary to prevent the logging of such internal fields.

Exception is the interfaceid field of host interfaces(only for hosts, not for proxies and host prototypes), and the hostmacroid field of user macros (for templates, host prototypes, hosts).

This task should be done after ZBXNEXT-6998 will be realized, because in scope of this task the logging of proxy assignment to hosts will be changed: Such assignments will be logged as the change on the host, not change on the proxy.


Generated at Tue Apr 01 04:11:22 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.