Mapping tags to data and events
You can map tags that you give meaningful names to data in events to display information in the Completed file transfers view, Completed processes view, or both, that is relevant to your business needs.
- Identify information that you want to display in the Completed file transfers view or the Completed processes view in the web console.
- Specify labels for user-defined fields. The labels you specify are displayed in the list of available tags when you are mapping data in events.
After you assess the data, events, and user-defined fields that are needed to include information that you want to see in the views, you can begin mapping the elements.
Tag mappings, which map user-defined labels to data and events, can be created so that they apply to both file transfers and processes, or only file transfers, or only processes. If you want to extract a piece of data from an event to store alongside file transfers from a particular type of server, you can define the mapping once by selecting Both processes and file transfers. This action saves you the trouble of defining the mapping twice.
You can create mappings that apply to processes, transfers, or both coming from any type of server. If you have a piece of data that is not limited to a particular type of server, you can define the mapping under Defaults for all server types.
If a mapping is defined for a process, file transfer, or both but does not end up matching the event that is specified in the mapping, the field is not populated. You can define a mapping that matches only sometimes. If the mapping matches, the field is populated. If the mapping does not match, the field is not populated. As a result, you can define two mappings for the same tag that are mutually exclusive. For example, Tag 2 might be populated sometimes by mapping 1 and sometimes by mapping 2.
- Any server type / Any server / Any event
- Any server type / Any server / Specific event
- Specific server type / Any server / Any event type
- Specific server type / Any server / Specific event type
- Specific server type / Specific server / Any event type
- Specific server type / Specific server / Specific event type
If you define mappings at all six levels for Tag 1, they are processed in the order listed: least specific to most specific, with the most specific taking precedence over the least specific. However, if you have 4 mappings for Tag1 and the mapping at level 4 matches an event but the event is not populated with data or is populated with a null value, then the value found in events that were matched at levels 1, 2, and 3 take precedence.
To map tags so that they can be displayed in the Completed file transfers view, Completed processes views, or both:
Configure the Completed file transfers view or the Completed processes view to include the tag mappings in the web console.