[
https://issues.apache.org/jira/browse/FALCON-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14555838#comment-14555838
]
Pallavi Rao commented on FALCON-1205:
-------------------------------------
I gave the patch a quick look and I have a basic question. Seems like patch is
logging the SLA misses into a local file. I'm not sure if that is easy to use
for a monitoring service for the following reasons:
1. Hard for users to find out the delta, or a time window based misses or on a
continuous basis.
2. Since it is a local file, users will need to read the file from each of the
Falcon Server, to get a consolidated view.
Few options we can consider:
1. Falcon anyway has dependencies on Active MQ, why not publish any SLA misses
as messages to JMS endpoints. If we want to keep the logs in the file for
history purpose, we can still do that.
2. Provide a REST API that user can use to query the SLA misses (with a time
window). If we expose this on Prism, it will take care of consolidation from
all the Falcon Servers.
> SLAService to keep track of missing SLAs for feeds
> --------------------------------------------------
>
> Key: FALCON-1205
> URL: https://issues.apache.org/jira/browse/FALCON-1205
> Project: Falcon
> Issue Type: Sub-task
> Reporter: Ajay Yadava
> Assignee: Ajay Yadava
> Attachments: FALCON-1205.patch
>
>
> We need a service to keep track of missing feed instances.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
