GitHub user jmakes opened a pull request:
https://github.com/apache/samza/pull/241
SAMZA-1356: Improve monitoring for state restore
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jmakes/samza samza-1356
Alternatively you can re
On Fri, Jun 30, 2017 at 7:25 AM, Evgeny wrote:
> Sorry didn't understand this question: "Is the container able to keep up
> with its inputs?" What do you mean keep up with its inputs?
>
Apologies for the vague phrasing. I meant to ask if the input topics have a
high volume of messages. If that's
Hey Jeremiah,
Here's how metrics reporting works:
1. Metrics like (gauges , timers, counters) are registered and created with
a "registry".
2. Metrics are then incremented / set based on business logic.
3. Metrics are reported using "reporters".
I see 3 alternatives:
1. You can contribute the p
I am using the Snapshot Metrics Reporter and a samza.metrics.timer to
instrument code blocks. The metrics are sent to a kafka topic via the metrics
reporter.
I can see the value of the timer in the topic ({"timerName":12.3}). I would
like to get the entire snapshot (timer.getSnapshot()) so I c
Hi. The input stream is kafka and samza is running on mesos using this
framework https://github.com/Banno/samza-mesos
Samza version - 0.12. Sorry didn't understand this question: "Is the container
able to keep up with its inputs?" What do you mean keep up with its inputs?
>Пятница, 30 июня
