GitHub user justinleet opened a pull request:
https://github.com/apache/incubator-metron/pull/573
METRON-943: Create traffic connections report in zeppelin
## Contributor Comments
Adds a Zeppelin dashboard that lets the user get connection counts filtered
by a CIDR block.
The implementation is a little kludgy because Spark/Hive don't have easy
operations to handle things like IPs and CIDRs. I'd have liked to keep it in
one paragraph, but the clunkiness around handling the ips and cidr made that a
pain that seemed significantly worse. If someone knows an easy way to take
care of it, I can quick try it.
Do we want/need similar paragraphs for the other sources? Given that we're
primarily looking for volume of connections, it seems unnecessary, but it might
be nice to have (possibly as a follow-on?) It's pretty to repeat the
paragraphs as needed.
Also, let me know if there are any verbiage changes (since that came up on
another dashboard), or other adjustments that should be made.
## Test Plan
To test, spin up full-dev. To get Yaf data, it'll be necessary to start
the sensor-stub
```
service sensor-stubs start yaf
```
It'll also be necessary to add Yaf to the list of sensors run in Ambari. To
do so, stop Metron, edit "Metron Parsers" to include "yaf" (or be yaf only).
Start Metron and ensure a yaf topology is present.
Let data flow through.
Once some data has gone through, we'll need to have an instance of
Zeppelin. Because of the size of the Vagrant instance, we'll want to shut down
unneeded services. Shutdown Metron, Kibana, Storm, Kafka, and HBase.
Install Zeppelin from "Actions - Add Service". It'll prompt you to install
Spark and Hive, do so. Configuration is pretty trivial, all that's necessary
is to set an arbitrary Hive database password. Let this run. The Hive service
check likes to fail on our Vagrant, but it's benign (some impersonation
configuration issue unrelated to actually running our queries). Ignore it and
accept the installation.
From Metron's "Service Actions", run the "Zeppelin Notebook Import", to
load our notebooks into Zeppelin. Use the quick links to navigate to the
Zeppelin UI.
Go into the "Metron - Connection Volume Report" notebook. Queries can be
made by CIDR, e.g. 192.0.0.0/8 to get total amount of traffic by source or by
destination IP range.
## Pull Request Checklist
Thank you for submitting a contribution to Apache Metron.
Please refer to our [Development
Guidelines](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61332235)
for the complete guide to follow for contributions.
Please refer also to our [Build Verification
Guidelines](https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds?show-miniview)
for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow
these guidelines and ask you to double check the following:
### For all changes:
- [x] Is there a JIRA ticket associated with this PR? If not one needs to
be created at [Metron
Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel).
- [x] Does your PR title start with METRON-XXXX where XXXX is the JIRA
number you are trying to resolve? Pay particular attention to the hyphen "-"
character.
- [x] Has your PR been rebased against the latest commit within the target
branch (typically master)?
### For code changes:
- [x] Have you included steps to reproduce the behavior or problem that is
being changed or addressed?
- [x] Have you included steps or a guide to how the change may be verified
and tested manually?
- [x] Have you ensured that the full suite of tests and checks have been
executed in the root incubating-metron folder via:
```
mvn -q clean integration-test install && build_utils/verify_licenses.sh
```
- [x] Have you verified the basic functionality of the build by building
and running locally with Vagrant full-dev environment or the equivalent?
#### Note:
Please ensure that once the PR is submitted, you check travis-ci for build
issues and submit an update to your PR as soon as possible.
It is also recommended that [travis-ci](https://travis-ci.org) is set up
for your personal repository such that your branches are built there before
submitting a pull request.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/justinleet/incubator-metron zepp_conn_vol
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-metron/pull/573.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #573
----
----
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
