The events subsystem in the Accelario Masking service functions as a monitoring and notification framework. It captures and logs various business events related to system and user processes, providing essential visibility for users and support personnel.
Description
...
Event logging.
The subsystem logs distinct events, such as adding or removing data sources and creating environments, or masking process steps. Each event is recorded with specific details like the action taken, the component involved, and the name of the entity (e.g., data source or environment).
Severity level.
Events are categorized by severity levels - 'Info' for successful operations and 'Error' for failed attempts or operations. This categorization aids in the quick identification of the status and importance of each event.
Message details.
Each event generates a descriptive message. For successful operations, the message confirms the successful completion (e.g., "Data Source <Name> was successfully added"). In case of failures, the message includes the error reason (e.g., "Failed to add data source <Name> due to <error reason>"), which is crucial for troubleshooting.
Component.
The subsystem is component-oriented, logging events under specific components like 'Data sources' or 'Environments'. This allows for easy filtering and analysis of events related to specific aspects of the system.
Action Tracking.
Each event message includes the type of action taken - such as 'Add data source', 'Remove data source', or 'Add environment'. This provides a clear context on the nature of the event.
Datetime.
This attribute records the exact date and time when the event occurred. It's crucial for tracking the sequence of events, understanding the system's behavior over time, and correlating events for troubleshooting.
Client ID.
This unique identifier is likely specific to the client or instance of the application where the event occurred. It's useful for distinguishing events across different clients or service instances.
License ID.
This is a unique identifier for the specific license under which the Masking solution is operating. Tracking events by license ID is beneficial for license management, auditing, and understanding usage or issues per licensed instance.
Application type.
Its is consistently 'Masking', the Accelario UsageMate event logging system is shared across multiple Accelario services.
Application version.
This specifies the version of the Masking service during the event. It's important for identifying issues or behaviors that are specific to certain versions and for managing version-wise operational insights.
Object name.
If applicable, this attribute provides a name of the specific component within the system to which the event is related. This is a name for a data source, environment, or other components in the system, enabling precise referencing of the event’s context.
Object reference ID.
If applicable, this ID provides a reference to the specific component object within the system to which the event is related. This could be a unique identifier for a data source, environment, or other components in the system, enabling precise linking of the event’s context.
User.
If applicable, this records which user (by username or user ID) was involved in or responsible for the event. This is particularly important for actions that are user-initiated or for auditing purposes to track user activity and responsibility.
Overall, this subsystem enhances operational transparency, aids in debugging, and assists in system auditing by providing a detailed, categorized, and easily navigable record of system events.
...
service refer /wiki/spaces/GEN/pages/2191753225
List of masking components for masking events
System parameters
Data Sources
Environments
Masking Rules
Privacy Policies
Users
Masking configurations
...