Introduction to clustered watch
In IBM Spectrum Scale 5.0.3, watch folder has a clustered watch capability.
With a clustered watch, it is possible to watch file operations across clusters using a centralized tool that has scalability and resiliency built-in. An entire file system, fileset, or inode space can be watched. You can specify all or a subset of events that are listed in Table 1. Similar to file audit logging, clustered watch captures file system activities at the IBM Spectrum Scale file system level, generates event notifications for those activities, and streams the notifications to topics within the message queue. Unlike file audit logging, the event notifications are then consumed by a conduit and sent to an external sink that you can manage.
- Producers in clustered watch
Producers generate file access event notifications and publish the notifications to a list of message queue servers (brokers). - The message queue in clustered watch
The message queue collects the file access event notifications published by the producer. - Conduits in clustered watch
The conduits in a clustered watch subscribe to the IBM Spectrum Scale topic that is associated with the watch and publish the messages to an external Kafka sink that is specified when enabling the clustered watch. - The message queue services monitor and clustered watch
With the introduction of clustered watch, a new component has been added to the message queue infrastructure in IBM Spectrum Scale: the message queue services monitor. - Interaction between clustered watch and the external Kafka sink
In IBM Spectrum Scale 5.0.3, clustered watch supports sending watch events to an external Kafka sink. - JSON attributes in clustered watch
Use this information to learn more about the JSON attributes that are associated with the 12 events that can be specified when enabling a clustered watch and the other events that might be received due to other file system activity.
Parent topic: Product overview