-
Story
-
Resolution: Done
-
Minor
-
DO280 - OCP 3.9 1 20181010
-
None
-
en-US (English)
URL: https://role.rhu.redhat.com/rol-rhu/rhz/rhls/course/do280-3.9/ch08
Reporter RHNID: rhn-support-ocasalsa, msameer-admin
Section: 8 - Installing and Configuring the Metrics Subsystem
Language: en-US (English)
Workaround: we should change the HEAPSTERAPI by HEAPSTER
We could define it as NODE=<node name>
We could definte it as START=$(date -d '1 minute ago' -u +%FT%TZ')
Description: https://role.rhu.redhat.com/rol-rhu/rhz/rhls/course/do280-3.9/ch08
In the Training DO280 Red Hat OpenShift Administration I Chapter 8. Installing and Configuring the Metrics Subsystem [1] subsection "Accessing Heapster and Hawkular", it's possible to read:
"# Assumes MASTERURL, NODE and START env vars are defined in the user environment
APIPROXY=${MASTERURL}/api/v1/proxy/namespaces/openshift-infra/services
HEAPSTERAPI=https:heapster:/api/v1/model
TOKEN=$(oc whoami -t)
curl -k -H "Authorization: Bearer $TOKEN" \
-X GET $APIPROXY/$HEAPSTER/$NODE/metrics/memory/working_set?start=$START
"
- The HEAPSTERAPI variable is not used. The curl is using a variable call HEAPSTER. Then, we should change the HEAPSTERAPI by HEAPSTER
- The NODE variable is never defined. We could define it as NODE=<node name>
- The START variable is never defined. We could definte it as START=$(date -d '1 minute ago' -u +%FT%TZ')
If we don't do it. This example is not valid anymore.