Ah, I see I mis-read METRON-897, and Nick specifically says
"lo:ipv4","eth0:ipv4" did not work for him, but ["_lo:ipv4_","_eth0:ipv4_"] did
work.
So I went back and dug a little deeper, and realized that in the environment
where "lo:ipv4","eth0:ipv4" worked for me, I had modified the yaml.j2
Hi, there have been widely varying statements about what needs to be in the
Elasticsearch config parameter “network_host”. I think I may have a rationale
for what works and what doesn’t, but I’d like your input or correction.
I am focusing on what worked in terms of punctuation (quotes and
Github user justinleet commented on the issue:
https://github.com/apache/incubator-metron/pull/556
Updated with the Bro split, removing aggregate paragraphs, and Snort
verbiage. Working on histogram.
---
If your project is set up for it, you can reply to this email and have your
You would supply Ambari credentials when you make the Ambari (not ours)
REST call.
On Mon, May 1, 2017 at 3:14 PM, Otto Fowler wrote:
> But we don’t have SSO, so that would required the ambari credentials be
> available to the rest api
>
>
> On May 1, 2017 at 16:10:03,
Github user merrimanr commented on the issue:
https://github.com/apache/incubator-metron/pull/500
@justinleet, METRON-909 and METRON-910 have both been addressed in the
latest commit.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user justinleet commented on the issue:
https://github.com/apache/incubator-metron/pull/500
I was able to run this up in a nonkerberized cluster, and then set up
Kerberos. Mostly things worked, but I spun out two tickets from this,
Github user mmiklavc commented on the issue:
https://github.com/apache/incubator-metron/pull/507
I didn't have any problems using the Kafka shell commands without a JAAS
file. That was on single node Vagrant, but I'm not sure there should be much of
a difference in this case.
---