while we can land a pr and accept the regressions, I do not think we should
do a release with our default sample environment broken.
-1
On April 27, 2019 at 18:11:42, Justin Leet (justinjl...@gmail.com) wrote:
> Mike is correct, that is because of the combination of full dev
> restrictions and
Mike is correct, that is because of the combination of full dev
restrictions and the lack of support in the configuration UI for parser
aggregation. This was introduced in
https://github.com/apache/metron/pull/1207 and also was true of the last
release. Currently, parser aggregation is an
I can confirm that I've seen the Mgmt UI shows the sensor status correctly when
they run as single topologies.
-Anand
On 4/27/19, 11:37 PM, "Michael Miklavcic" wrote:
I believe that is bc of parser aggregation. The UI does not support it
currently. IIRC there was a PR to change the
Hey Otto,
I believe that should be possible. I currently rely on Cloudera's openstack
infrastructure and framework to spin up VMs, after which I deploy the cluster
by going through the install wizard manually.
-Anand
On 4/26/19, 7:34 PM, "Otto Fowler" wrote:
Curious Anand,
are your
I believe that is bc of parser aggregation. The UI does not support it
currently. IIRC there was a PR to change the bro, snort, and yaf sensors to
aggregated bc full dev didn't have enough resources. The upshot is that the
UI still works for single sensors, but the feature for enabling aggregated
-1
Ran the script and ran full dev, all good.
In the configuration ui, the status of the sensors is not correct. It does
not show any running, but they are running in storm and the data was moved
correctly.
On April 26, 2019 at 09:58:02, Otto Fowler (ottobackwa...@gmail.com) wrote:
Curious
