Resource Types

A resource type is defined on a per-plugin basis, but a single plugin may define multiple resource types. A resource type is a fairly generic concept that tries to identify and delineate a construct, whether that be an entire operating system, a program running in some operation system, or a tiny little service running inside that program. All resources have exactly one resource type, usually just referred to as its type.

Resource Category

As hinted above, there are three major categories that any resource type falls into: an operating system, a program, or a service. The vocabulary RHQ uses for these three groups is platform, server, and service, respectively. Each of these resource categories is discussed in more detail below in the context of how they are arranged hierarchically.

Resource Hierarchies

The resource hierarchy attempts to mimic, as closely as possible, how programs and processes are physically and/or programmatically structured on a platform. Below are the supported ways resources can be related by category.

Although a picture is worth a thousand words, below is a full text description for those that want to know precisely what this one says:

• A server can be a child of a platform (e.g. JBoss AS on Linux)

  • A platform can have many children servers

• A service can be a child of a server or a platform (e.g. JMS Queue on JBoss AS)

  • A platform can have many children services

  • A server can have many children services

• A server can be a child of another server (e.g. Tomcat embedded in JBoss AS)

  • A server can have many children servers

• A service can be a child of another service (e.g. Table inside a Database)

  • A service can have many children services

It's worth mentioning that a resource can only have one parent. Thus, the resource hierarchy we're dealing with in RHQ actually takes the form of a directed, acyclic graph (DAG). The graph's root is its platform, and the servers and services beneath it help to form a shallow, yet relatively wide tree.

Resources

Each resource is a concrete instance of one of the plugin-defined resource types. Thus, each resource will have exactly one resource type. Resources are the actual instances of the platforms, servers, and services that are installed on the boxes where the RHQ Agents reside.

Inventory states

Resources can be in the following states within RHQ:

NEW

• most resources will be automatically discovered by RHQ

• the auto-discovery portlet on the dashboard will show discovered resources that have not yet been either ignored or imported (a.k.a committed)

IGNORED

• this state is used to "hide" one or more auto-discovered resources; instead of being imported into inventory, these resources can instead be "ignored"

• this feature is useful if the discovery process found servers that you're not interested in managing / monitoring at this time

• resources in this state will not show up in inventory nor in the auto-discovery portlet

  • to see resources that have previously been ignored (as well as to unignore them), click the "View All..." button of the auto-discovery portlet

• unignoring a resource will put it back into the NEW state

  • a resource must be unignored before it can be imported into inventory

COMMITTED

• resources that have been imported successfully are marked as committed

  • note: importing a resource will implicitly import (a.k.a commit) all of it's children resources recursively

• when using the resource browser, only committed resources will be shown

Discovery Queue Portlet

The usual way of taking resources into inventory is by using the Discovery Queue Portlet. As soon as you connect a new RHQ Agent to the RHQ Server, it will send information about the platform and servers it discovers (usually via a process table scan). This scan is performed when the RHQ Agent first starts up, and then is done periodically to discover newly added resources in the system.

The discovered resources will be shown in the Discovery Queue Portlet on the Dashboard:

From there you can press the import button to commit the resource and take it into inventory. For each platform or server committed, it will trigger another type of scan which will search recursively for all nested servers and services.

The time it takes to find all of the nested resources beneath a parent resource may vary; it largely depends on the number of resources there are to be discovered. Each server or service scanned in this way will be automatically committed beneath its respective parent resource.

Discovery Queue

In the Inventory view, the Discovery Queue is useful when dealing with larger inventories, as the auto-discovery portlet doesn't wield very much screen real estate on the dashboard.
Here you can unignore resources or import any resources that are in new state.

Manual discovery

If for some reason it is not possible to auto-discover some resource in your enterprise, you may still have the option of manually adding it to inventory. This is determined by whether it is a type of resource that includes support for being manually added.

To add a new resource, use the resource browser to find what should be its logical parent resource. Remember, since the resource browser only shows committed resources, you must first import the parent in order to manually add a child resource to the inventory.

Click over to the inventory tab of this parent resource. Under the "Child Resources" section, the drop-down button "Import" is the first step towards bringing a resource into inventory manually; select the type of resource you want to add.

The next page will display all properties that the plugin requires (each resource type in the system has a different set of required properties) in order to be able to uniquely identify and successfully connect to this new resource.

After submitting the form, the resource will start in the committed state, and thus be available for viewing in the resource browser.

Now the resource is ready to be monitored and managed like any other auto discovered resource.

Resource details

On the resource page, there is an arrow which you can toggle to see the resources details:
Clicking on name, description and location fields lets you edit the values.

Child Resources

This section shows the children of current resource with their availability.

Import

Below the list of children you see the "Import" button referred to above in the Manual discovery section. This function serves to add child resources that were not autodiscovered.

The drop down will contain all resource types that can be manually added for this parent.
Selecting a type and clicking "OK" will lead to a template selection page:

Here you can select a template that fills in some default values. After that you are forwarded to a page where you can fill in the remaining values.

Create new child resources

Some resources also allow to create new children. This means that the new child resource will be created on the target resource as a new child. This way you can, for example, create a new JMS destination directly from your RHQ console. If the managed resource allows the creation of child resources, you will also see a "Create Child" button:

As with manually adding a child resource, you will be forwarded to pages that are specific to the respective resource type.

Note, it may take as long as a few minutes for the newly added child Resource to show up in your inventory.

Deleting resources

It is possible for some resource types to be physically deleted through RHQ. This is defined in the plugin descriptor of the plugin handling the resource.

When you press the delete button, you will be presented with a warning where you can cancel the action:

If you click on Yes, a few things will happen:

• the resource will be removed from inventory (along with any metric history, operational history, etc)

  • all of its child resource will also be removed from inventory (along with all history too)

  • the resource and its children will be removed from any resource groups they are in

• the agent will delete the physical entity on the managed box

Groups Containing this Resource

This section shows the list of groups that this resource is part of.

In the example it is a DynaGroup group named "Down resources" with 3 members. The group availability is down (i.e. all members are down).

Clicking on the group name will lead you to a page where you see the group members and more group-specific things. See Groups for more information.

Connection Settings

The Connection Settings subtab allows you to edit the Resource's connection properties. Connection properties tell Agent plugin associated with the Resource how to connect to the underlying managed resource. For example, here is the Connection subtab for a JBoss AS 7 Standalone Server Resource:

The Hostname and Port are the informations the JBoss AS 7 plugin will use to connect to AS7 http management interface.

Most of the properties are editable. The Home Directory, ...etc are not editable, because those properties are read-only; their values were automatically set by the Agent plugin associated with the Resource at the time the Resource was first discovered. Click the Save button to save the connection properties. Note, the Agent associated with the Resource must be running in order to successfully save the connection properties.

To view the history of revisions made to the Resource's connection properties, go to the conne

To view a particular revision, click the version number link in that revision's Version column.

To delete a revision from the history, select the revision line then click the Delete button.

Agent

The Agent subtab shows information about the Agent that is managing this Resource. This will help you debug cases where you, for example, set up everything correctly, but you aren't receiving any metric data for the Resource.

The section lists the IP address of the Agent along with the port the Agent is listening on for commands from the Server.