Trisul Network Analytics
Developer Zone

User Tools

Site Tools

You are here: Home » docker » Using the TrisulNSM Docker appliance
Trace:
docker:intro

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Last revisionBoth sides next revision
docker:intro [2017/11/17 00:06] – veeradocker:intro [2017/11/17 00:08] – [All in one NSM and Traffic monitoring] veera
Line 14: Line 14:
   - github [[https://github.com/trisulnsm/docker|trisulnsm/docker]] : Quick instructions on running the appliance    - github [[https://github.com/trisulnsm/docker|trisulnsm/docker]] : Quick instructions on running the appliance 
   - [[https://trisul.org/blog/docker/post.html|Blog post]] announcing the release    - [[https://trisul.org/blog/docker/post.html|Blog post]] announcing the release 
 +  - Devzone article [[docker:pcap_analysis|"Importing PCAPS"]] explaining how you can import PCAP dumps 
  
 ===== Advantages of the Docker NSM appliance ===== ===== Advantages of the Docker NSM appliance =====
Line 26: Line 27:
 ===== Next steps ===== ===== Next steps =====
  
-If you are a point solution , this Docker image should be good enough for most deployments.  Here are some advantages of installing the packages directly on the host instead of Docker.+If you need a 'point' solution , this Docker image should be good enough for most deployments.  Here are some advantages of installing the packages directly on the host instead of Docker.
  
   - Trisul packages allow a Hub+Probe architecture. The Docker image bundles them all in one ball. If you want to deploy a distribute probe network. You need to use the packages.   - Trisul packages allow a Hub+Probe architecture. The Docker image bundles them all in one ball. If you want to deploy a distribute probe network. You need to use the packages.
docker/intro.txt · Last modified: 2017/11/17 00:08 by veera