This is a series about a slack related app where we use ES as the backend for every event we would possibly like to store for analysis.
There are few things we need to consider and the first is related to the fields provided by the slack api that are related to dates and timestamps.
Most of them are ending with ts.
By storing all events in ES we can then go and identify them.
running an apm-server for testing purposes in your local machine (here is mac)
$GOPATH/bin/apm-server run -v -e -c ~/citrix/testing-apm/apm-server.yml -E apm-server.expvar.enabled=true
https://www.elastic.co/guide/en/apm/server/current/configuration-monitor.html#_bulk_max_size_6 https://www.elastic.co/guide/en/apm/server/current/elasticsearch-output.html https://www.elastic.co/guide/en/apm/server/current/apm-server-configuration.html https://www.elastic.co/guide/en/apm/server/current/running-on-docker.html
https://www.elastic.co/guide/en/apm/server/current/common-problems.html https://www.elastic.co/guide/en/apm/server/current/common-problems.html#queue-full https://www.elastic.co/guide/en/apm/server/current/common-problems.html#request-timed-out https://www.elastic.co/guide/en/apm/server/master/common-problems.html#io-timeout
https://www.elastic.co/guide/en/apm/server/current/sizing-guide.html https://www.elastic.co/guide/en/apm/server/current/processing-performance.html https://www.elastic.co/guide/en/apm/server/current/tune-apm-server.html https://www.elastic.co/guide/en/apm/get-started/7.6/transaction-spans.html
https://github.com/elastic/hey-apm https://github.com/elastic/apm-server/issues/1414
https://www.elastic.co/guide/en/apm/agent/python/4.x/configuration.html
Make 2 files for running the server and the hey-apm benchmarking tool for it