Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E2537200C07 for ; Sun, 22 Jan 2017 22:54:33 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id E10DB160B45; Sun, 22 Jan 2017 21:54:33 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 37263160B39 for ; Sun, 22 Jan 2017 22:54:33 +0100 (CET) Received: (qmail 61196 invoked by uid 500); 22 Jan 2017 21:54:32 -0000 Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@falcon.apache.org Delivered-To: mailing list dev@falcon.apache.org Received: (qmail 61185 invoked by uid 99); 22 Jan 2017 21:54:32 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 22 Jan 2017 21:54:32 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id E3246C0C53 for ; Sun, 22 Jan 2017 21:54:31 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.199 X-Spam-Level: X-Spam-Status: No, score=-1.199 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id cXBbURWu0ALD for ; Sun, 22 Jan 2017 21:54:31 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 263835F30D for ; Sun, 22 Jan 2017 21:54:31 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 6ED04E0350 for ; Sun, 22 Jan 2017 21:54:27 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 874DB25289 for ; Sun, 22 Jan 2017 21:54:26 +0000 (UTC) Date: Sun, 22 Jan 2017 21:54:26 +0000 (UTC) From: "Ajay Yadava (JIRA)" To: dev@falcon.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (FALCON-436) Addition of a feed monitoring service in Falcon to report the feed SLAs breach MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sun, 22 Jan 2017 21:54:34 -0000 [ https://issues.apache.org/jira/browse/FALCON-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Yadava updated FALCON-436: ------------------------------- Assignee: (was: Ajay Yadava) > Addition of a feed monitoring service in Falcon to report the feed SLAs breach > ------------------------------------------------------------------------------ > > Key: FALCON-436 > URL: https://issues.apache.org/jira/browse/FALCON-436 > Project: Falcon > Issue Type: New Feature > Reporter: Rohit Kochar > > I have a use case where i want to monitor whether a particular instance of a feed was published before a pre defined time and report this metrics to some central service. > I believe this can be achieved by defining a SLA parameter of each feed and by addition of feed monitoring service in the Falcon which monitors the feed instances. -- This message was sent by Atlassian JIRA (v6.3.4#6332)