WARNING: With the release of the new 5.0 set of Elastic.co products, Topbeat will be deprecated and replaced by Metricbeat.
A Metricbeat Docker image is available right now: https://hub.docker.com/r/athieriot/metricbeat/
Please acknowledge that, at the moment (October 2016), the configuration of Metricbeat container can't be done via environment variables. You will need to provide a config file for further customisation.
1.3.0,1.3.11.2.3-alpine
1.2.0,1.2.1,1.2.2,1.2.31.1.2,1.1.1,1.1.01.0.1,1.0.0
Docker image for Elastic Topbeat
docker run -d \
--link=elasticsearch:elasticsearch \
--name=topbeat \
--pid=host \
athieriot/topbeat
docker run -d \
-e PROFILE=logstash \
--link=logstash:logstash \
--name=topbeat \
--pid=host \
athieriot/topbeat
docker run -d \
-e PROFILE=file \
-v /path/to/data/:/topbeat/data/ \
--name=topbeat \
--pid=host \
athieriot/topbeat
docker run \
-e PROFILE=console \
--name=topbeat \
--pid=host \
athieriot/topbeat
docker run -d \
-e PROFILE=custom \
-v /path/to/config/topbeat.yml:/topbeat/config/topbeat.yml \
--name=topbeat \
--pid=host \
athieriot/topbeat
docker run -d \
-e HOST=elasticsearch.in.aws.com \
-e PORT=80 \
-e CPU_PER_CORE=false \
-e INDEX=topbeat \
-e PROCS=.* \
-e PERIOD=10 \
-e SHIPPER_NAME=super-app \
-e SHIPPER_TAGS="qa", "db" \
--name=topbeat \
--pid=host \
athieriot/topbeat
In the event you are usage a custom configuration or logstash but want to add Topbeat templates to your own Elasticsearch instance:
docker run -d \
-e PROFILE=logstash \
-e EXTERNAL_ELASTIC_HOST=my.elasticsearch.com \
-e EXTERNAL_ELASTIC_PORT=9200 \
--link=logstash:logstash \
--name=topbeat \
--pid=host \
athieriot/topbeat
Somehow, when Elasticsearch is launched inside a container it is inaccessible from another linked container. A configuration has to be set for it to work properly. Change IP as needed.
docker run --name=elasticsearch elasticsearch elasticsearch -Des.network.bind_host=0.0.0.0
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent