Fuse Management Central: User Guide

Once you enter a System you’ll be presented with a system dashboard where you can visualize more detailed system information, individual metrics and system related actions.

Some of the information, regarding the system status (offline and CSIDE Mode), will have visual indicators so the user can easily identify the system status.

The widgets presented will be more detailed in the following topics.

Actions can be performed in two ways, Immediate Actions or Scheduled Actions.

Each action is an operation performed directly on a system, having a direct consequence to it (e.g. Restart), meaning that all actions should be planned and performed carefully.

Any issues Fuse has detected with your system will be shown as described in Alerts.

Besides that, errors and warnings can be expanded to view the details by clicking on top of the Errors and Warnings widget.

Clicking in an Environment name in the Systems list will open the Environment Details page. This page shows you details about an environment.

The Environment page is divided into 3 main sections:

At a glance, you will see overall performance, availability and broad system statistics all from a single place. On the overview section you can see the following widget:

On the right side you will have a list of active alerts grouped by System or Environment. For instance, if a system has alerts, you will have a panel with the system name and a collapsible block with all the alerts of that system.

Clicking in an alert entry will redirect you to the Alert Details page.

This list can be filtered and searched to find alerts easier.

You will have a list of the running Operations and the latest Operations finished. You will also have a list of the next scheduled Operations.

Fuse Management Central allows you to quickly identify problems in the OpenText ™ system components and processes using visual indicators.

These visual indicators are easy to identify and are spread all over the application trough dashboards and widgets.

Errors and alerts counters can be expanded in some dashboards, usually the more detailed ones (for instance, a System Dashboard). When expanded it will show the list of all related alerts with more detail. It is possible to highlight the widget related with the alert, to do that just hover the mouse over the alert on the alerts list.

Some indicators can also be hovered and a tooltip will be shown showing more details about the alert.

Clicking in any Alert entry in an Alerts list, existent in Dashboard, System Details, Environment Details or in the Events side ribbon, will open an Alert Details page which offers a wide view over a specific Alert.

This page contains everything there is to know about the Alert: the alert cause, start and end time, current status, systems and/or environments affected, components affected, or any other detailed information available in the Alert.

It will also show if any user was notified of the Alert and which channel was used for that notification.

On the right side, there is a list of all currently active alerts. It is possible to navigate that list and easily switch between alerts. There are filters available to facilitate the search on that list, for example: filter by environment, system or component, filter by alert severity. It is also possible to search with text by name or description.

All the information available in this page is time-machinable, which means that it is possible to navigate in time and check the alert status at any specific point in time. It is also possible to check information about past alerts that are already resolved.

Fuse Management Central allows to dismiss alerts that the user may think are not worth for a specific system and/or environment.

In alerts lists there is a context menu that allows to dismiss an alert. There are 2 options available:

Using any of these dismiss actions means that that specific alert will be ignored for that specific component in that system/environment (contextual to the current alert entry).

Some points to have in consideration:

All dismissals will be listed in Fuse Administration Alert Manager page, inside each alert configuration, from where they can be removed in order to get the alert working again. Only Fuse Administrators can access this page. For more information please refer to the Installation and Administration Guide.

To get email notifications from a specific system, or environment, one must belong to the owners' distribution list.

To configure the owner for a specific system, you must:

To get email notifications from an environment, you must:

There are two situations that inhibit alert notifications, meaning that you won’t get those notifications even if the alert is actually active:

In the email subject, we include the following information:

An example of the email subject is:

For the email body, the following information is included:

There is a View Details button available to navigate directly to the Alert Details page, from where it is possible to check all the information available from the alert, as well as perform related actions. For more info, please check Alert Details.

Currently, an audit event is created every time a user creates, updates or deletes the following entities:

These events can be used to determine who, when and what changed in Fuse Management Central for auditing purposes.

Alert events are triggered by alerts from Alert Manager, and they basically store when the alert was triggered and its status (either it has been resolved or not).

Alert events are grouped by alert type, system/environment and time, which means that if more than one component triggers the same alert type for the same system/environment, they will be stored in the same event.

The following table describes event severity types:

To list all events:

It’s then possible to apply filters and scroll down results to keep getting previous events.

Relevant information regarding each event is displayed:

Events retention policy is 15 days. Events before that period are permanently deleted from Fuse Management Central.

From the point of view of Fuse operations are a set of actions executed on just one system or to multiple systems at the same time.
Each operation has a global status that depends on the individual result of each system job that belongs to the operation. Based on that, operations can have one of the next status:

In Fuse Management Central scheduled operations are divided in 2 types:

With those two types, Administrators can easily schedule simple operations (like execute next friday) or more complex ones (like execute every day at midnight) .

In Fuse Management Central Administrators can opt to receive operations status notifications. Depending on the configuration selected, notifications will be sent or not to a list of users.

When scheduling an operation, Administrators can choose one of the following notification options:

The Overview chart provides an at-a-glance view of the status of all operations.

All operations are included and grouped by state. The user can easily see how many operations there are in each state.

All operations in execution or already executed are listed here and can be filtered by:

All scheduled operations are listed here and can be filtered by:

To disable a scheduled operation:

When users open the Time Machine mode, they will see a timeline at the top of the page with a range of 2 days. The range is represented by 2 date fields displayed in the time machine header.

On this timeline, users will have an overview of errors (red bars) and warnings (yellow bars) over the selected range of time.

Users can change the timeline range by clicking on the dates in the time machine header. Users can select some predefined ranges such as Last Day, Last Week, Last 2 weeks. Or choose a custom range by selecting a date range on the calendar. When a range is applied, the timeline will adjust to show only that chosen period of time and it’s on this timeline that users can select a specific point in time.

When on Time Machine Mode, user will always be at the specific point in time represented by a marker "You are here". Users can change the current point by simply clicking in any other point in the timeline.

All data displayed will be related to the point selected and some interval before that point. This interval is configurable, users can select values such as Last 5 minutes, Last 1 hour, Last 24 hours. For instance, if a user selects the point 30 Mars 20 03:00 and select an interval of "Last 2 hours", the information presented on the page will show data between 30 Mars 20 01:00 and 30 Mars 20 03:00.

As a typical use case, if someone reports an error during the previous night, with the Time Machine mode, you are able to go back (with a few clicks) to the precise moment where the error happened, and check the state of your system at that moment.

You can zoom via area selection with the mouse in the Time Machine chart. You can also Pan (option allows you to move the Time Machine date range in any direction within 15 days) by clicking and dragging the mouse. You can switch between zooming and panning using the buttons available in the top right corner of Time Machine.

After a Zoom in you will have available the Reset Zoom option to reset the Time Machine to its initial zoom state.

When there are Stale Metrics, some alerts can be fired from those metrics, especially alerts that depend on a certain duration.

For example, let’s say that the CPU usage alert is configured to be fired once the CPU usage is above 90% for more than 30 seconds, and this metric is collected every 5 seconds. If Fuse collects a metric of 95% at point 00:00, it should be able to collect new metrics at 00:05, 00:10, 00:15, etc…​ If the collections start to fail or delaying, after 30 seconds the last value known to Fuse will still be 95%, so at 00:30 the alert will be fired.

However, Fuse will have a notification on the alert saying that it was generated from a Stale Metric. This happens because Fuse Management Central cannot be sure if that alert is really accurate, since it is based on "delayed" information, so the System Administrator should verify the authenticity of the alert.

The Logs Viewer allows you to browse and visualize any of your system logs, as well as searching for a specific word(s) inside the log opened in the viewer.

Log files are shown at the tree view structure where users can navigate and click the log file to visualize it’s content and select files or folders to download or perform actions. You can sort the tree by name, size or last modification date. You can also search the tree for log names.

When visualizing a log file some reserved words will highlight its line position, helping one to quickly identify any occurred issues:

The footer shows the number of lines as well as counters for warnings and errors in the loaded lines. Clicking in warnings or errors counters allows you to filter the log file to display only warnings and/or error lines.

There’s a button to maximize or minimize the viewer. If the number of lines displayed is less than the total lines, more lines will be loaded as you scroll up the log file. When the log file is updated, a button will be shown informing the user the new number of lines that he can be loaded by clicking the button (there’s also a blue circle indicator showing next to the tab file name). The user can activate the "Auto Refresh" toggle in order to automatically load new lines. New lines will be loaded and marked as new with a separator in the viewer.

Users can search for content inside the opened log file using the search bar in the header of the log viewer.

Fuse Management Central log viewer also allows you to have different log files opened at the same time and navigate through them by a tab system. To close a tab, just click the X button next to the file name.

For trace files, the user has the possibility to view the file with a trace view layout or plain text. A toggle button to switch the view type will be shown in the bottom left corner of the viewer.

System administrators can download/delete one, multiple or an entire log folder, by selecting the log(s) and/or folder(s) and clicking the Download button or Delete under the actions button.
The selected log(s)/folder(s) package will be downloaded in a compressed ZIP file, maintaining its original folder structure.

Availability is a much more simple formula, just having into account the status of Content Server in a certain period and rate.

For example, if you are checking the availability of Content Server for 1 hour with a rate of 1 minute, and if Content Server was offline for 20 minutes, then you’ll have an availability of 67% (40 / 60).

This page provides more in depth information about each thread and all its metrics (queue, requests, …​), while allowing to combine and compare multiple environments using the following filters:

If a thread is generating a log file, it’s possible to quickly open the log by clicking the button under the Log File column. It will open a new tab displaying the log file with the Logs Viewer.

You can see all the configuration settings for a given Content Server and have the ability to change them from this interface.
From here, administrators are able to change most aspects of the Content Server administration or reuse these configurations in a Configuration Policy.

Fuse Management Central recognize which configurations require a system restart, if so, a confirmation message will appear to alert the user.

To apply any configuration just expand the configuration desired change the value/toggle you want, the Apply Changes button will be enabled and you can click it to apply the changes.

To add configurations to a Configuration Policy or other Systems, select the desired configurations by clicking on the box on the left of the configuration (the box will show a check mark when selected). At this point, the Add Configuration Policy and Add to More Systems will be enabled and you can click the button to perform the desired action. After click the button, you will be allowed to choose the Configurations Policies or the Systems you want to apply, after choosing it just click the Add to Configuration Policy or Apply Configurations, according to the action selected.

Policies are created based on existing system configurations (used as template), which you can always customize later. This allows you to clone and distribute configurations across your system landscape.

To create a Configuration Policy:

After that, the policy will be displayed in the left panel list. For each list element, you can:

Adding configurations to a policy already created is also possible. For that you just need to:

If you want to remove one or multiple configurations from a policy, follow these steps:

To delete a Configuration Policy:

After that, the policy will be deleted.

When editing you can opt by 2 different things:

As described previously, policies are created with a configuration based on a specific system. If wanted you can easily apply those policy configurations to all the policy systems. To apply the policy configurations to the policy systems:

To activate or deactivate policy monitoring:

After activated, the monitoring process will display, after a few moments the policy compliance status. The possible status are the following:

In Non-Compliance mode you can see system configurations that are non-compliant with the policy selected.

This mode will be only accessible if policy compliance status is Non-compliant and when this condition is happening, the option View Details will be shown for each system non-compliant. By clicking there, you will enter the non-compliance mode and you would be able to check (side by side) policy configurations against system configurations.

Then on the right panel you’ll have the option to Apply the policy only to the specific system that you are checking.

System Object Volume page is available through any System Object Volume widget, existent in System or Environment details pages. The System Object Volume widget contains a link to System Object Volume details page.

System Object Volume details page presents an overview on System Object Volume organized in 2 major sections:

The Admin Servers section inside System Object Volume details page displays a list of all the Admin Servers and Processes existent in the Environment.

In this page the user will find several indicators that will help to understand the status of the Admin Servers and Processes. Any alerts will also be pinpointed in the specific Admin Server or Process that may be failing.

Hovering the mouse on top of a status or alert will display details about it, when relevant.

The user can easily Suspend, Reset or Resynchronize Admin Servers, using the Actions menu for each Admin Server, or by selecting multiple Admin Servers in the list and using the global Actions button in the top of the Admin Servers list.

Each Admin Server can be expanded in order to view a complete list of all the Processes existent in that Admin Server.

The user can execute multiple actions on top of one or multiple Processes:

These actions can be executed for one or multiple Processes, using the Actions menu of each Process or using the global Actions button in the top of the Processes list.

The available actions will depend on the type of Processes selected by the user.

The Data Sources section inside System Object Volume details page displays all the Data Sources existent in the Environment.

Each Data Source will be presented in a different tab. Inside each Data Source tab the user can find a visual representation of the Data Flow and Partition Map components.

The Data Flow section shows a list of Ipools between Processes. There are multiple status and alert indicators that will help understand the status of the Data Flow and its Processes and Ipools.

Multiple actions can be executed for each process, such as Start, Stop, Restart and Resynchronize, using the menu available in each Process component.

The Partition Map section displays a visual representation of the Partitions, Update Distributors and Search Federators of the Data Source, listing all Index and Search Engines, as well as showing the existent connections between the multiple Processes of the Partition Map.

Multiple status and alert indicators will help understand the status of the Partition Map and its Processes. Multiple actions can be executed for each Process, such as:

These actions can be executed using the menu available in each Process component.

Storage Providers page is available through any Storage Providers widget, existent in System or Environment details pages. The Storage Providers widget contains a link to Storage Providers details page.

The page is divided in 3 sections:

This page has also a filter always available to help users, allowing them to combine and compare multiple storage providers. Users can filter by:

Here users can also Add Storage Provider, Edit Storage Provider, Delete Storage Provider and Update Monitoring List.

In this section users can quickly see how much data is saved in each storage provider. It provides a global overview of all storage providers and their size.

Here users can compare different storage providers throughput. 2 charts are available, one for read throughput and other for write throughput.

Each graphic displays the throughput for each storage provider, allowing to compare speeds between the existent storage providers.

In this section users can see storage providers information in a table format. For example, users can see storage providers name, systems that are monitoring or not the storage provider, average read/write throughput, used disk, path and alerts (with mouse over the storage provider icon)

To add a storage provider users only need to click on the button Add Storage Provider and follow the wizard steps:

To edit a storage provider users only need to click on Edit button that can be found on the storage providers table. The same wizard displayed on Add Storage Provider will be displayed but now it will be filled with the storage provider selected.

To delete a storage provider users only need to click on Delete button that can be found on the storage providers table.

By default, Fuse is not calculating Read and Write Throughput metrics. To calculate these metrics the storage provider must be added to the systems’ monitoring list where the user wants to monitor it.

To update the monitoring list, users only need to click on Update Monitoring List button and fill the wizard fields:

Finally, the user can click Update or schedule the update by clicking Schedule Update.

A complete list of the Business Applications in your system and their status, as well as possible alerts that may be affecting your system.

Hovering the mouse over a Business Application will display a tooltip with more detailed information.

The Scheduled Processing section is only available in the Environment details page, under the OpenText Content Server > Components tabs.

It displays a complete list of Jobs in your environment and their status, as well as possible alerts that may be affecting your schedules.

Hovering the mouse over a Job will display a tooltip with more detailed information.

The Licensing section is only available in the Environment details page, under the OpenText Content Server > Components tabs.

Licensing provides a list of Ecosystems, Licenses and Users existent in your environment, as well as their status and possible issues affecting your Environment.

More details can be found hovering each list entry.

On the Archives widget top-right corner, there’s a context menu that allows you to Add Original Archive.

Give the new Archive a name and you’re ready to add it. As usual, this action can be performed right away or scheduled for later.

When you click on a Logical Archive, a modal window will open providing more details about it, including:

For each Pool listed in the Logical Archive you can see a list of all Disk Volumes attached to it, and make changes to their Status, either Locked or Write Locked.

You can also Detach Volume from the Pool, using the context menu in the Disk Volume entry.

On the Certificates list, it is possible to Enable or Disable each certificate, as well as to Change Certificates Privileges.

From the Infrastructure widget, you can create new Disk Volumes, using the actions context menu in the top-right corner of the widget.

The following properties will be asked to create the Volume:

After filling those fields you’re ready to create the new Volume. This action can be performed immediately or scheduled for later.

Clicking in a Buffer will open a modal window with more details about the Buffer.

Among other details, you’ll see a list of Volumes attached to this Buffer, as well as a list of Pools and Archives where the Buffer is being used.

On the Volumes list, you can change the Volume status (Locked and Write Locked), as well as Detach Volume, using the context menu in the Volume entry.

Clicking in a Volume will open a modal window with more details about the Disk Volume.

Clicking in a Storage Device will open a modal window with more details about the Device.

Among other details, you’ll see a list of Volumes created in the Storage Device. In this list you can check for important information, such as the used space, media type and the file system.

Clicking in a Cache will open a modal window with more details about the Cache.

You can start and stop the scheduler depending by clicking on its context menu.

From the Jobs widget, you can add a new job, using the actions context menu, located on the widget top-right corner.

The following properties will be prompt to create the Job:

From the jobs' widget, you can clear all job protocol list, using the actions context menu in the top-right corner of the widget. This will clear all the protocols for all jobs.

Clicking in a Job will open a modal window with more details about the Job.

Among the job properties, and if the job is executing, you will see a tab with the message from the last job execution (e.g. last protocol) and a tab with a list of protocols for the job.

Protocols are job executions. Protocol entries with a red status are protocols finished with an error and the ones with green status identify jobs that have run successfully.

Each Document Pipeline server entry is followed by a status icon that indicates any currently active alert(s). Hovering over the icon will display a tooltip with more detailed information about each alert. Additionally, an informative icon is provided, that when hovered displays the hostname of the Document Pipeline server. Each Document Pipeline server entry also includes a summary of the total pipelines, input documents, and error documents.

By clicking on a Document Pipeline server, users can expand it to view a comprehensive list of all the configured and deployed pipelines, each Pipeline entry is followed by a status icon that indicates any currently active alert(s) and total input and error documents chart. Hovering over the icon will display a tooltip with more detailed information about each alert.

By expanding a Pipeline, users can view all assigned DocTools as well as their status. Each DocTool entry includes an icon representing its current status, and if there are any alerts, hovering over the icon will reveal more details. Each DocTool entry also displays the total count of input and error documents, along with a contextual button that provides access to a list of available actions:

By selecting the Show Input/Error Documents action, a table displaying all input/error documents in alphabetical order will be displayed. This table allows for easy searching by document name and navigation through pages using pagination. When hovering over a document, its full path will be displayed in a tooltip, and a contextual button provides access to the following actions:

When clicking the document’s Show Protocol action, a modal containing the document’s protocol will be shown. It will also show the document path, the document pipeline hostname and a button with the following actions:

When you select the Show Protocol action for a document, a modal will appear displaying the document’s protocol, its path, and the hostname of the Document Pipeline server. This modal will have two buttons for the following actions: