verticle-io/apex

http://toolkits.verticle.io - APEX JVM data extraction toolkit

netics-w

@netics-w

Hi guys. I found apexbeat project on Elastic's community beats page. So, now I am trying to build apexbeat. I am using apex's documentation on how to run apexbeat. And I see no abexbeat executable after building. Could anyone please help me?

Jens Saade

@jenssaade

Hi @netics-w, we are currently providing pre-built jars. You can find them on the release page.

http://toolkits.verticle.io/downloads/index.html

Let me know if you need a hand installing apex.

Jens Saade

@jenssaade

You might also want to check out the short quickstart guide here: http://toolkits.verticle.io/docs/index.html#quickstart

netics-w

@netics-w

Thanks for your answer. But I am asking about apexbeat - a beat for integration with ELK-stack.

I've found docker-container with apexbeat which is provided on downloads page, and I don't understand how to start it - there is no executable apexbeat in docker image.

Jens Saade

@jenssaade

the call chain would be: java-application + apex-agent (collector) -> apexbeat -> ELK

so you would need both components - apex and apexbeat

apexbeat is a receiver beat

it will push metrics from the apex-agent to ELK

Jens Saade

@jenssaade

concerning the apexbeat installation, this should help http://toolkits.verticle.io/docs/index.html#elasticsearch-apexbeats

or, if you prefer to use the docker image instead of compiling the beat yourself, you can use this image: https://hub.docker.com/r/verticleio/apexbeat/

netics-w

@netics-w

Yes, I understand the call chain and that I must have moth apex-agent and apexbeat. But I don't understand how to start apexbeat. I don't see any executable file named "apexbeat". I have everything using documentation.

This is a directory listing of apexbeat after make setup && make: .git .travis.yml LICENSE README.md apexbeat apexbeat.template-es2x.json apexbeat.test beater config fields.yml libbeat.yml main_test.go vendor
.gitignore CONTRIBUTING.md Makefile _meta apexbeat.full.yml apexbeat.template.json apexbeat.yml build docs libbeat.full.yml main.go tests vio-apex-isometric5.svg

as u can see - there is no file named apexbeat

sorry, in my previous message there is file name apexbeat - I tried to rename apexbeat.test and start it as apexbeat. but it doesn't work as beat

and this is docker container listing: /go # ls src/github.com/verticle-io/apexbeat/
CONTRIBUTING.md README.md apexbeat.template-es2x.json beater main.go
LICENSE _meta apexbeat.template.json config main_test.go
Makefile apexbeat.full.yml apexbeat.yml docs tests

netics-w

@netics-w

there is also no apexbeat executable file

Jens Saade

@jenssaade

If you want to build it from scratch your GO environment should be set up properly

when making apexbeat it will be copied to the corresponding directory

netics-w

@netics-w

My GO-environment is set properly. No any error or warning during build. All test are passing.

Jens Saade

@jenssaade

so in my case I see the apexbeat executable in the ${GOPATH}/bin dir

Jens Saade

@jenssaade

when I run 'make' I get it created here ${GOPATH}/src/github.com/verticle-io/apexbeat

Jens Saade

@jenssaade

if building from scratch does not work out you can also try running the docker image, it will connect to Elasticsearch on localhost

is that suitable for you scenario?

netics-w

@netics-w

it is suitable for me. I've done docker pull verticleio/apexbeat . then I start container from that image in interactive shell - docker run -i -t verticleio/apexbeat /bin/sh. Then I see that no any apexbeat executable file on container's filesystem

Jens Saade

@jenssaade

$  docker run verticleio/apexbeat
starting apexbeat
2017/05/17 14:45:44.702564 beat.go:276: INFO Home path: [/go/src/app] Config path: [/go/src/app] Data path: [/go/src/app/data] Logs path: [/go/src/app/logs]
2017/05/17 14:45:44.702823 beat.go:182: INFO Setup Beat: apexbeat; Version: 6.0.0-alpha1
2017/05/17 14:45:44.702869 processor.go:44: DBG  Processors:
2017/05/17 14:45:44.702902 beat.go:188: DBG  Initializing output plugins
2017/05/17 14:45:44.704363 metrics.go:23: INFO Metrics logging every 30s
2017/05/17 14:45:44.703196 output.go:254: INFO Loading template enabled. Reading template file: /go/src/app/apexbeat.template.json
2017/05/17 14:45:44.711508 output.go:265: INFO Loading template enabled for Elasticsearch 2.x. Reading template file: /go/src/app/apexbeat.template-es2x.json
2017/05/17 14:45:44.711839 client.go:123: INFO Elasticsearch url: http://elasticsearch:9200
2017/05/17 14:45:44.711969 outputs.go:108: INFO Activated elasticsearch as output plugin.
2017/05/17 14:45:44.712115 publish.go:238: DBG  Create output worker
2017/05/17 14:45:44.712248 publish.go:280: DBG  No output is defined to store the topology. The server fields might not be filled.
2017/05/17 14:45:44.712342 publish.go:295: INFO Publisher name: 4e6e3be15ebd
2017/05/17 14:45:44.712977 async.go:63: INFO Flush Interval set to: 1s
2017/05/17 14:45:44.713020 async.go:64: INFO Max Bulk Size set to: 50
2017/05/17 14:45:44.713037 async.go:72: DBG  create bulk processing worker (interval=1s, bulk size=50)
2017/05/17 14:45:44.716309 beat.go:212: INFO apexbeat start running.
2017/05/17 14:45:44.716481 apexbeat.go:47: INFO apexbeat is running (port 8089)! Hit CTRL-C to stop it.

this is what it looks like on my machine

opening port 8089

should look similar on your machine

Jens Saade

@jenssaade

btw, you were looking for the binary, it's renamed/relocated to /go/bin/app:

FROM golang:alpine

MAINTAINER Jens Saade "jens@verticle.io"

RUN apk update && \
    apk upgrade && \
    apk add git

RUN cd /go/src/
RUN git clone https://github.com/verticle-io/apexbeat.git

RUN mv apexbeat /go/src/app
ADD beatconfig/apexbeat.yml /go/src/app/apexbeat.yml

RUN go get -d -v app
RUN go install -v app

ADD entrypoint.sh /entrypoint.sh
RUN chmod a+x /entrypoint.sh

VOLUME /go/src/app

CMD ["/entrypoint.sh"]

creating that is quite some days ago, but now I remembered ;)

Jens Saade

@jenssaade

you might want to change /go/src/app/apexbeat.yml though, I see it points to "elasticsearch:9200"

used that within a docker-compose scenario I guess

netics-w

@netics-w

Yes, that works. Thanks!

Jens Saade

@jenssaade

perfect ;)

Where communities thrive

People

Repo info

Activity