Start influxdb with udp enabled and published, related to #226

Author: majst01

Dockerfile

@@ -11,14 +11,20 @@ do
   echo "Tesing againts influxdb ${version}"
   docker kill influxdb || true
   docker rm influxdb || true
-  docker run -d --name influxdb -p 8086:8086 influxdb:${version}
+  docker run \
+            --detach \
+            --name influxdb \
+            --publish 8086:8086 \
+            --publish 8089:8089/udp \
+            --volume ${PWD}/influxdb.conf:/etc/influxdb/influxdb.conf \
+        influxdb:${version}
 
   docker run -it --rm  \
-         -v $PWD:/usr/src/mymaven \
-         -v $PWD/.m2:/root/.m2 \
-         -w /usr/src/mymaven \
-         --link=influxdb \
-         -e INFLUXDB_IP=influxdb \
+        --volume $PWD:/usr/src/mymaven \
+        --volume $PWD/.m2:/root/.m2 \
+        --workdir /usr/src/mymaven \
+        --link=influxdb \
+        --env INFLUXDB_IP=influxdb \
          maven mvn clean install
 
   docker kill influxdb || true

compile-and-test.sh

@@ -0,0 +1,25 @@
+[meta]
+  dir = "/var/lib/influxdb/meta"
+
+[data]
+  dir = "/var/lib/influxdb/data"
+  engine = "tsm1"
+  wal-dir = "/var/lib/influxdb/wal"
+
+[admin]
+  enabled = true
+
+[[udp]]
+enabled = true
+bind-address = ":8089"
+database = "udp"
+retention-policy = ""
+
+# These next lines control how batching works. You should have this enabled
+# otherwise you could get dropped metrics or poor performance. Batching
+# will buffer points in memory if you have many coming in.
+
+batch-size = 1000 # will flush if this many points get buffered
+batch-pending = 5 # number of batches that may be pending in memory
+batch-timeout = "1s" # will flush at least this often even if we haven't hit buffer limit
+read-buffer = 0 # UDP Read buffer size, 0 means OS default. UDP listener will fail if set above OS max.