[
https://issues.apache.org/jira/browse/AMBARI-23524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16514941#comment-16514941
]
Hudson commented on AMBARI-23524:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9474 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9474/])
AMBARI-23524. There are no alerts for logfeeder (#1564) (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=648fdaa217b7483e89fb482ef436bd88978825d3])
* (edit)
ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/alerts.json
* (add)
ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/package/alerts/alert_logfeeder.py
> There is no alerts for logfeeder
> --------------------------------
>
> Key: AMBARI-23524
> URL: https://issues.apache.org/jira/browse/AMBARI-23524
> Project: Ambari
> Issue Type: Bug
> Components: logsearch
> Affects Versions: trunk
> Reporter: zhangxiaolu
> Assignee: zhangxiaolu
> Priority: Major
> Labels: patch, pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-23524.patch, screenshot-1.png, screenshot-2.png
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> h1. There is no alerts for logfeeder.
> when one logfeeder is down,there is no alert.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
