Fuse Management Central: User Guide

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

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

Charts indicators are shown as a blinking bar over the widget.

Components and processes color is changed according to the alert level.

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.

Resolved states are only listed in the events bar when the alert stops being triggered.

Fuse Management Central can send email notifications for every alert that is triggered. Those emails are sent to all owners of the corresponding systems and / or environments, and will include useful information regarding the type of alert, its severity and observed value.

Alerts notifications can include more than one alert, if they have the exact same type, system and / or environments, date and severity. That means that if two agents that belong to a specific system trigger the exact same alert at the same time, only an email is sent that aggregates those two alerts.

Currently, an audit event is created every time a user created, 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.

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.

Threads are parts of OpenText ™ Content Server process that allow it to perform multiple functions concurrently, serving several requests at the same time.
When a thread is spawned, it loads all of installed modules and patches, persisting their own OScript objects in memory.

Fuse Management Central allows to monitor in real time all system threads, allowing a constant and thorough analysis of all dimensions of thread metric data, effectively allowing you to profile your system.

Clicking on the double arrow to the top right of the widget will take you to the thread details page, increasing the level of detail of this component.

The Threads widget also allows you to quickly apply settings, by clicking the wrench icon on the top right of the widget.

Processes show you the agents and the loaded processes within Content Server which are loaded.

You can enable or disable individual processes by clicking directly on them, displaying its full details, such as name, status, alerts, etc..
Whenever an administrator modify a process, the Apply Changes button becomes activated allowing to push those changes immediately, or schedule them, to be applied on your system.

The Configurations widget allows the user to view how many configurations are applied to the system as well Configuration Polices and their compliance state.
To access a configuration policy just expand the Configuration Polices and click the policy desired.

To view the configurations with more detail click on the double arrow to the top right of the widget.

Content Server storage providers are listed here and clicking on each provider will expand its details, displaying its read and write throughput and also providing an graphical representation over time of its performance.

Although Fuse Management Central does not require any logging enabled, it allows one to manage and view your system log files if desired.
The logs widget gives you an overview of your system logs, allowing you to see the number of log files being generated and if there are any trace files (exceptions) being generated.

Clicking the wrench icon will allow you to quickly change your different system log levels.

You can access the Log viewer by clicking the double arrow icon to the top right of the widget.

If a trace file exists, you can open it quickly just by expanding the trace files and clicking at the trace file. When clicked, a new tab will be opened with the trace file displayed on the Logs Viewer.

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.
These actions where described in detail in the previous chapters for each widget or page.

Any issues Fuse has detected with your Content Server will be shown as described here Errors & Alerts.

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

The Environments page is where you can view the list of environments and manage them. This page can be accessed by clicking on Environments on the left bar.

On the top, this page shows the averages of some metrics gathered from the systems, including performance, availability, memory and cpu usage, requests, queue time, queue depth and threads usage. Also includes information about the number of errors and warnings in the systems.

Below, there’s a table listing all the environments. The results in this table can be filtered using the search bar above the table or the dropdown next to the search bar. The search bar allows to filter the results in the table by doing a full text search over the name and tags of the systems. The dropdown next to the search bar allows to filter the environments by tag.

You can click on the names of the environments in the table to view more information about a particular environment.

It’s also possible to sort the systems by name by clicking on the arrows after the Name header. On the bottom of the table you can navigate between the result pages and change the number of environments shown per page.

To create a new environment:

To delete an environment:

To edit an environment:

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:

Add configurations to a policy already created it’s 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 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 compliancy status. The possible status are the following:

On 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.

For 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 individually result of each system job that belong 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 of the configuration selected, notifications will be send 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 in execution or already executed are listed here and can be filtered by:

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

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 in some cases. 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.

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.

To access the Dashboard, click Dashboard on the navigation menu.

When you open the Time Machine mode, you will see a timeline at the top of the page with a range of 2 days. On this timeline, you will have an overview of errors (red bars) and warnings (yellow bars) over the selected range of time. You can change the timeline range by clicking on the dates below the timeline:

.

Here you can select some predefined ranges such as Last Day, Last Week, Last 2 weeks. Or you can choose a custom range by selecting a date range on the calendar. When you apply a range the timeline will adjust to show only that chosen period of time and it’s on this timeline that you can select a specific point in time.

When you are on Time Machine Mode, you will always be at the specific point in time (represented by a marker "You are here")

Observing an interval of time before that specific point (represented by the grey area on the previous figure). This interval is configurable, you can select values such as Last 5 minutes, Last 1 hour, Last 24 hours. For instance, if you select the point 30 Mars 20 03:00 and you 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 button on 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.