-
Bug
-
Resolution: Done
-
Blocker
-
EAP70 1.5.0.GA
-
jboss-mm-7-tech-preview/middleware-manager:7.0.0-16
jboss-mm-7-tech-preview/middleware-manager-datastore:7.0.0-4
jboss-eap-7/eap70-openshift:1.5-5
With EAP7 eap70-openshift:1.5-5 , the hawkular agent doesn't seem to push any metrics to the hawkular server. Same scenario works fine with eap70-openshift:1.5-4
- name: AB_HAWKULAR_REST_PASSWORD
value: phawk
- name: AB_HAWKULAR_REST_TENANT_ID
value: devel-support
- name: AB_HAWKULAR_REST_KEYSTORE_PASSWORD
value: password
- name: AB_HAWKULAR_REST_KEYSTORE
value: truststore
- name: AB_HAWKULAR_REST_USER
value: uhawk
- name: AB_HAWKULAR_REST_URL
value: https://mms.foobar.example.com
- name: AB_HAWKULAR_REST_KEYSTORE_DIR
value: /ssl/hawkular
curl -s -k -H 'Hawkular-Tenant: devel-support' https://uhawk:phawk@mms.foobar.example.com/hawkular/metrics/metrics | python -m json.tool
shows only
[
{
"dataRetention": 14,
"id": "hawkular-feed-availability-devel-support-1-b425d",
"tenantId": "devel-support",
"type": "availability"
}
]
instead of the expected huge list of metrics that can be seen when eap70-openshift:1.5-4 is used instead. (so it seems that it did create at least that, so the connection seems to work)
