Audit and change logging for ADO activity

KaveengaWijayasekara · 2025-06-11T23:47:31+00:00

There was an error rendering this rich post.

I am trying to ensure comprehensive logging and auditing within the Anaplan Data Orchestrator (ADO). Currently, ADO activities are not being logged in the audit log. This includes crucial details such as:

Users who logged in
Login timestamps
Objects created or changed
Data integration processes executed

While Cloudworks integrations are logged, ADO activities are not, creating a gap in our audit trail.

Specific Examples

User Activity Tracking: When a user logs into ADO, there is no record of this event. For instance, if an unauthorized user gains access, we have no way of identifying this.
Object Changes: When objects (e.g., models, modules, lists) are created or modified, there is no log entry. This makes it difficult to track changes over time or identify the source of issues.
Data Integration Processes: Executions of data integration processes are not logged. For example, if a data import fails, we lack the details needed to troubleshoot and resolve the issue.

Workarounds

Currently, there are no effective workarounds to capture this missing information. We rely on manual tracking and user reports, which are neither reliable nor efficient.

Impact

Frequency

This issue impacts our users on a daily basis as ADO is a critical component of our data management and integration workflows.

Affected Users

Model Builders: Unable to track changes to models and modules.
Solution Architects: Lack of visibility into integration processes and potential failures.
Admins: Difficulty in monitoring user activities and ensuring compliance.
Integration Experts: Challenges in troubleshooting and optimizing data integration processes.
Business/End Users: Potential delays and inaccuracies in data reporting and analysis.

Ideal Solution

Solution Description

The ideal solution would involve comprehensive logging of all ADO activities in the audit log. This includes:

User Logins: Record user login details with timestamps.
Object Changes: Log creation, modification, and deletion of objects.
Data Integration Processes: Capture execution details, including success or failure statuses, timestamps, and any error messages.

Value Addition

Enhanced Security: Ability to monitor and audit user access and activities, improving security and compliance.
Improved Troubleshooting: Detailed logs would aid in identifying and resolving issues more efficiently.
Change Management: Better tracking of changes to objects, aiding in version control and change management.
Operational Efficiency: Streamlined monitoring and management of data integration processes, reducing downtime and errors.

Comments

Quick Links

New ideas

Lock Freeze Panes ability for View Designers as a card setting
In as much detail as possible, describe the problem or experience related to your idea. Please provide the context of what you were trying to do and include specific examples or workarounds: With the new release of the ability for end-users to lock freeze panes - I feel it would actually be materially more helpful if page…
Ability to Expand/Collapse horizontal sections full of field cards (like filters).
In as much detail as possible, describe the problem or experience related to your idea. Please provide the context of what you were trying to do and include specific examples or workarounds: How often is this impacting your users? Who is this impacting? (ex. model builders, solution architects, partners, admins,…
Status Log
Could you please allow me to see a log of the processing status of the workspace and model? Once this is achieved, it will be possible to identify the cause of the failure to some extent by checking the logs when it occurs, and the speed of response to the failure will increase.