Component that allows users to interface with Hawkular. One rest call to it's endpoint will probably end up with multiple requests to the individual components.



Hawkular Services

Build Status

Hawkular Services is the main distribution for base level Hawkular components, such as Metrics, Alerts and Inventory.


Hawkular is released under Apache License, Version 2.0 as described in the LICENSE document

Getting Started

To get started with Hawkular Services, you’ll need to download the latest distribution (or build one), unzip, create a user and set the Agent to use this password.

You’ll also need a Cassandra server up and running. Please, refer to Cassandra’s official instructions on how to set it up. NOTE: If you build your own Hawkular Services distribution, you do not need to install and run Cassandra yourself if you build with the -Pembeddedc Maven profile, which deploys an embedded Cassandra node within the Hawkular Services server itself.

The following script shows how to accomplish all those steps. Please, don’t use this script to setup a production instance, as it has several flaws (like catching error conditions, insecure password setting, …​).


export HAWKULAR_RELEASE="0.39.0.Final"
export HAWKULAR_PASSWORD="password" ## on production systems, you'd want to better protect the password
#export CASSANDRA_NODES=localhost ## set this variable to the location of cassandra

export HAWKULAR_BASEDIR="/opt/hawkular-services"
export HAWKULAR_HOME="${HAWKULAR_BASEDIR}/hawkular-services-dist-${HAWKULAR_RELEASE}"
export HAWKULAR_DIST="hawkular-services-dist-${HAWKULAR_RELEASE}.zip"
export HAWKULAR_SHASUM="hawkular-services-dist-${HAWKULAR_RELEASE}.zip.sha1"

if [ ! -d "${HAWKULAR_BASEDIR}" ] ; then
  mkdir -p "${HAWKULAR_BASEDIR}"
  if [ $? -ne 0 ]; then
    echo "Unable to create HAWKULAR_BASEDIR: ${HAWKULAR_BASEDIR}"
    exit 1

if [ -f "${HAWKULAR_DIST}" ] ; then
  echo "Using existing distribution"

if [ ! -f "${HAWKULAR_SHASUM}" ] ; then

export ACTUAL_SUM=`sha1sum ${HAWKULAR_DIST} | awk '{print $1}'`

if [ "${EXPECTED_SUM}" != "${ACTUAL_SUM}" ] ; then
  echo "Something is wrong. The checksum is not a match. Expected sum: ${EXPECTED_SUM}, actual sum is ${ACTUAL_SUM}"

if [ -d "${HAWKULAR_HOME}" ] ; then
  echo "Existing Hawkular found at ${HAWKULAR_HOME}. Moving it to ${HAWKULAR_HOME}.bkp"
unzip -q "hawkular-services-dist-${HAWKULAR_RELEASE}.zip"

echo "Hawkular Home is: ${HAWKULAR_HOME}"
"${HAWKULAR_HOME}/bin/" \
  -a \
  -g read-write,read-only
"${HAWKULAR_HOME}/bin/""${HAWKULAR_USERNAME}""${HAWKULAR_PASSWORD} -Dhawkular.agent.enabled=true"

Building and Releasing

Hawkular Services uses a standard Maven build.

mvn install

The fabric8 docker maven plugin is used to build the docker container.

cd docker-dist
mvn docker:build

For more information about the Docker container, see docker-dist/README.adoc

Continuous Integration builds are performed for each newly merged commit via the Torii Jenkins server

Release Process

The release process requires an account on the Torii Jenkins server Once logged in, the option "Perform Maven Release" will become available. Select this option, make any changes to the relesae settings if necessary, and then select "Schedule Maven Release Build". This will run a mvn release:prepare release:perform, which builds the project and releases the artifacts to the Nexus Maven repository. The job also triggers some post-release tasks, such as creating a GitHub release with the appropriate assets.