You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Dmytro Sen (JIRA)" <ji...@apache.org> on 2016/06/15 13:35:09 UTC
[jira] [Updated] (AMBARI-17255) AMS collector not coming up in 2.5
cluster blueprint deployment
[ https://issues.apache.org/jira/browse/AMBARI-17255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmytro Sen updated AMBARI-17255:
--------------------------------
Attachment: AMBARI-17255_1.patch
> AMS collector not coming up in 2.5 cluster blueprint deployment
> ---------------------------------------------------------------
>
> Key: AMBARI-17255
> URL: https://issues.apache.org/jira/browse/AMBARI-17255
> Project: Ambari
> Issue Type: Bug
> Components: alerts, ambari-metrics, blueprints
> Affects Versions: 2.4.0
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17255_1.patch
>
>
> After updating the property timeline.metrics.service.webapp.address to 0.0.0.0:6188 (earlier it was localhost:6188), I am able to access metadata using the command curl http://host1:6188/ws/v1/timeline/metrics/metadata
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)