 |  |  |  |  |
| | | | |
 |  |
Fuse HQ is a set of tools that let you monitor a wide range of activity on any group of machines that you can access via HTTP. It is highly customizable, letting you determine what activity you want to see, what conditions cause alerts and what actions are taken in response, and who has access to the tools.
This book focuses on using Fuse HQ to monitor other components of the , Fuse Message Broker and Fuse ESB. As installed, Fuse HQ can automatically detect and monitor these and many other processes, including, for example, Web servers, database servers, and CPU activity. In addition, you can develop plugins that enable monitoring of other processes that are not automatically supported.
A Fuse HQ system comprises one or more agents, a server, and a database.
Agent — An agent runs on each machine that you want to monitor. Each agent discovers resources and monitors activity on its host machine, and sends information about the resources and activity to the server. In the context of a system, typically a Fuse HQ agent runs on each machine that hosts a Fuse Message Broker.
Server — The server runs on a single host. The server gathers information from the agents and manages the database. It includes the browser-based user interface component, called the HQ Portal, which displays metrics and alerts and provides the necessary tools for configuration, administration, and reporting. (A command line interface, not described in this book, is also available.)
Database —The database stores all HQ-related data, including system inventory information, data gathered by the agents, and configuration data governing behavior and access. You have the option of using a built-in PostgreSQL database installed with Fuse HQ, or a standalone database (Oracle, PostgreSQL, or MySQL). In this guide, it is assumed that you are using the built-in database, which requires no setup or configuration.
The components of your system that Fuse HQ can monitor are called resources. From the resources available on your system, you choose the specific ones that you want to monitor. This set of resources is your inventory. The inventory comprises both basic resources and composite resources.
Basic resources include platforms, servers, and services.
Platform — A platform is typically a computer (a combination of a machine and an operating system). It can also be a network device or a storage device. Platforms host servers.
Server — A server is a process, running on a platform, that provides services. Each server provides multiple services. In the , the Fuse Message Broker and the Fuse ESB container are servers.
Service — A service is a server component that provides a specific, discrete function. In the , services include the connectors, topics, and queues running on a Fuse Message Broker, and the various services deployed in a Fuse ESB container.
You combine selected basic resources, according to your own criteria, to define and add to your inventory two types of composite resources: groups and applications.
Group — A group can consist of any combination of platforms, servers, and services. Groups can be mixed or compatible. If a group is compatible, meaning that its member resources share the same metrics and control actions, you can monitor and act on all of those resources as a single entity. Groups have an important function in setting permissions, as the groups assigned to a user's role determine the resources that are visible to that user.
Application — Any set of services can be aggregated as an application, as appropriate. This allows you to focus logically on the actual work that your deployed services perform.
| |  | |
 |
