Manta Flow Server Administration
Encoding
All property files are encoded in ISO 8859-1 character encoding. Characters that cannot be directly represented in this encoding can be written using Unicode escapes as defined in section 3.3 of The Java™ Language Specification; only a single “u“ character is allowed in an escape sequence.
Logging
The Manta Dataflow Server uses the log4j2 framework for logging. The configuration is available on the page Configurations > Server > Common > Log4J Server in Manta Admin UI. The official documentation for this framework can be found here.
Usage Statistics
The Manta Flow Server collects usage statistics in the inner database. These statistics are captured during user interaction with Manta UI and API.
The collected statistics can be exported using the link <manta-server-url>/usage
as an archived CSV file. The export form enables you to set the starting date from which the statistics are exported. The statistics can be cleaned
via the URL
<manta-server-url>/usage/clean
.
The usage statistics CSV file has the following columns.
-
date — The date and time of the action that is logged
-
user — The user who performed/triggered the action
-
action — The code of the action that was performed; the table below contains a complete list of action codes together with descriptions of the actions
-
params — Additional parameters that are logged; the attributes are represented as a JSON object and are different for each action. The key in the JSON object is always the name of the parameter, and the value is either a value literal or a nested JSON object.
Action source module |
Action code |
Action description |
Params |
---|---|---|---|
Manta Flow |
server_start |
This action is logged after the start-up of the Manta Flow Server application. |
|
Manta Flow Viewer |
flow_catalog_show |
This action is logged when the user views the main screen of the Manta Flow Viewer application. |
N/A |
Manta Flow Viewer |
flow_vis_refView |
This action is logged when the user executes the analysis and visualization of the data lineage in the Manta Flow Viewer application. |
|
Manta Flow Viewer |
flow_vis_contractionEvent |
This action is logged when the result of a data lineage analysis is too big to be visualized in Manta Flow Viewer and has to be contracted. |
|
Manta Flow Viewer |
flow_vis_aggEdgesIssue |
This action is logged when the result of a data lineage analysis contains too many aggregate edges to be visualized in Manta Flow Viewer and, as a result, the aggregate edges have to be removed. |
N/A |
Manta Flow Viewer |
flow_vis_sourceCode |
This action is logged when the user views the content of any source script in the Manta Flow Viewer application. |
|
Manta Flow Viewer |
flow_vis_permaLink |
This action is logged when the user generates a permalink for a specific data lineage visualization in the Manta Flow Viewer application. |
|
Manta Flow Viewer |
flow_vis_exportCsv |
This action is logged when the user exports the result of a data lineage analysis to a CSV. This export can be triggered either from the main screen or from the data lineage visualization screen of the Manta Flow Viewer application. |
|
Manta Flow Viewer |
flow_vis_exportPng |
This action is logged when the user exports a specific data lineage diagram to a PNG file. This export can only be triggered from the data lineage visualization screen of the Manta Flow Viewer application. |
|
Manta Flow Viewer |
flow_vis_exportDirect |
This action is logged when the user executes the analysis and export of the data lineage directly from the main screen of the Manta Flow Viewer application. (The lineage is not visualized in Manta Flow Viewer in this case.) |
The params for this action are the same as for |
Manta Flow Merger |
flow_revision_new |
This action is logged whenever a new (major or minor) revision is created in the Manta Flow Server repository. |
|
Manta Flow Merger |
flow_revision_commit |
This action is logged whenever an opened (major or minor) revision is committed in the Manta Flow Server repository. |
|
Manta Flow Merger |
flow_revision_rollback |
This action is logged whenever an opened (major or minor) revision is rolled back in the Manta Flow Server repository. |
|
Manta Flow Merger |
flow_revision_pruneTo |
This action is logged whenever the content of the Manta Flow Server repository is pruned from the oldest revision to a specific (newer) revision. |
|
Manta Flow Merger |
flow_revision_pruneOldest |
This action is logged whenever the content of the Manta Flow Server repository is pruned and only a specified number of latest revisions is preserved. |
The params for this action are the same as for the |
Manta Flow Merger |
flow_repository_truncate |
This action is logged whenever all the content of the Manta Flow Server repository is truncated. |
N/A |
Manta Flow Merger |
flow_repository_content |
This action is logged whenever the Collect Statistics scenario is executed. |
|
Manta Flow Merger |
flow_repository_backLinks |
This action is logged whenever the backlink phase of the repository postprocessing scenario is executed for a specified Manta resource. |
|
Manta Flow Merger |
flow_repository_unification |
This action is logged whenever the unification phase of the repository postprocessing scenario is executed. |
|
Manta Flow Merger |
flow_repository_edgePropagate |
This action is logged whenever the edge propagation phase of the repository postprocessing scenario is executed. |
|
Manta Flow Merger |
flow_repository_contraction |
This action is logged whenever the contraction phase of the repository postprocessing scenario is executed. |
|
Manta Flow Merger |
flow_repository_interpolation |
This action is logged whenever the lineage interpolation phase of the repository postprocessing scenario is executed. |
|
Manta Flow Exporter |
flow_repository_export |
This action is logged whenever an export of the whole Manta Flow Server repository is executed. |
|