Skip to content

Removed the 'Deploying the Hawkular OpenShift Agent' Section per BZ #8726

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 16, 2018
Merged

Removed the 'Deploying the Hawkular OpenShift Agent' Section per BZ #8726

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
53 changes: 0 additions & 53 deletions install_config/cluster_metrics.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -624,59 +624,6 @@ $ oc adm diagnostics MetricsApiProxy
----


[[deploying-hawkular-openshift-agent]]
== Deploying the Hawkular OpenShift Agent

[NOTE]
====
The Hawkular OpenShift Agent is currently in Technology Preview.
====

The link:https://github.com/hawkular/hawkular-openshift-agent[Hawkular OpenShift
Agent] can be used to gather application metrics from pods running within the
{product-title} cluster. These metrics can then be viewed from the console or
accessed via the Hawkular Metrics REST API.

In order for these metrics to be gathered, your pod needs to expose a Prometheus
or Jolokia endpoint and create a special ConfigMap, which defines where the
metric endpoint is located and how the metrics should be gathered. More
information can be found under the
link:https://github.com/hawkular/hawkular-openshift-agent[Hawkular OpenShift
Agent documentation].

The agent runs as a daemon set in your cluster and is deployed to the `default`
project. By deploying to the `default` project, the agent continues to monitor
all your pods even if the `ovs_multitenant` plug-in is enabled.

To deploy the agent, you will need to gather two configuration files:
ifdef::openshift-origin[]
----
$ wget https://raw.githubusercontent.com/openshift/origin-metrics/enterprise/hawkular-openshift-agent/hawkular-openshift-agent-configmap.yaml
$ wget https://raw.githubusercontent.com/openshift/origin-metrics/enterprise/hawkular-openshift-agent/hawkular-openshift-agent.yaml
----
endif::[]
ifdef::openshift-enterprise[]
----
$ wget https://github.com/openshift/origin-metrics/blob/enterprise/hawkular-openshift-agent/hawkular-openshift-agent-configmap.yaml
$ wget https://github.com/openshift/origin-metrics/blob/enterprise/hawkular-openshift-agent/hawkular-openshift-agent.yaml
----
endif::[]

To set up and deploy the agent into your {product-title} cluster, run:
----
$ oc create -f hawkular-openshift-agent-configmap.yaml -n default
$ oc process -f hawkular-openshift-agent.yaml | oc create -n default -f -
$ oc adm policy add-cluster-role-to-user hawkular-openshift-agent system:serviceaccount:default:hawkular-openshift-agent
----

[[Undeploying-the-hawkular-openshift-agent]]
=== Undeploying the Hawkular OpenShift Agent

To undeploy the Hawkular Metrics Agent, run:
----
$ oc delete all,secrets,sa,templates,configmaps,daemonsets,clusterroles --selector=metrics-infra=agent -n default
----

[[install-setting-the-metrics-public-url]]
== Setting the Metrics Public URL

Expand Down