metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mmiklavc <>
Subject [GitHub] incubator-metron pull request #417: METRON-659 Emulate Sensors in Developmen...
Date Mon, 16 Jan 2017 21:23:24 GMT
Github user mmiklavc commented on a diff in the pull request:
    --- Diff: metron-deployment/roles/sensor-stubs/templates/start-bro-stub ---
    @@ -0,0 +1,55 @@
    +#!/usr/bin/env bash
    +# Licensed to the Apache Software Foundation (ASF) under one
    +# or more contributor license agreements.  See the NOTICE file
    +# distributed with this work for additional information
    +# regarding copyright ownership.  The ASF licenses this file
    +# to you under the Apache License, Version 2.0 (the
    +# "License"); you may not use this file except in compliance
    +# with the License.  You may obtain a copy of the License at
    +# Unless required by applicable law or agreed to in writing, software
    +# distributed under the License is distributed on an "AS IS" BASIS,
    +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    +# See the License for the specific language governing permissions and
    +# limitations under the License.
    +# simulates the behavior of a sensor by sending canned telemetry data
    +# to a Kafka topic.
    +# a subset of the canned data is randomly selected and is sent in 
    +# batches.  the timestamp of the message is altered to match current
    +# system time.  the number of messages sent in each batch, along with 
    +# the time delay between batches can be configured.
    +# start-bro-stub <DELAY> <COUNT>
    +# how long to delay between each 'batch' in seconds. defaults to 2 seconds.
    +# how many messages to send in each 'batch'.  the messages are drawn randomly
    +# from the entire set of canned data. defaults to 1000.
    --- End diff --
    This is default 100 not 1000, no? I noticed the same for the other stubs.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message