overops/collector repository overview

⁠OverOps Collector

OverOps analyzes your application in real-time, providing code-level insights in QA, Staging and Production. Monitor your applications, not your logs. Visit overops.com⁠ to learn more.

⁠Supported tags and respective Dockerfile links

• latest (Dockerfile)⁠

⁠Run the Collector

This image requires an Installation Key⁠ provided by OverOps.

docker run -d -p 6060:6060 \
--name overops-collector \
-e TAKIPI_BASE_URL=https://backend.overops.com \
-e TAKIPI_LISTEN_PORT=6060 \
-e TAKIPI_SECRET_KEY=your-installation-key-here \
-e TAKIPI_SERVER_NAME=docker \
overops/collector

⁠Advanced Configuration

1. Create a private folder

2. In the private folder, create the file installation.key containing your installation key.

3. In the private folder, create the collector.properties file based on the following template. Additional templates can be found on GitHub⁠.

   jvmPath=${JAVA_HOME}/lib/amd64/server/libjvm.so
   libraryPath=/opt/takipi/lib
   
   takipi.backend.url=https://backend.overops.com
   takipi.storage.test.url=https://s3.amazonaws.com/app-takipi-com/ConnectionTest
   takipi.jvm.heap.size=1G
   takipi.listen.port=6060
   takipi.server.name=docker
   

   Copy

4. Run the overops/collector container

   ℹ️ Tip Run from directory that contains the private directory. Otherwise you will get an error response: invalid mount config for type "bind": source path does not exist: /private/private

   docker run -d -p 6060:6060 \
   --mount type=bind,source="$(pwd)"/private,target=/opt/takipi/private overops/collector
   

   Copy

5. Verify connectivity on https://app.overops.com/⁠ in your browser

⁠Rootless

Starting with version 4.56.0, all published images are now "rootless." Images are now using the base image openjdk:8-jre-slim and running with user ID 1000 and group ID 1000 instead of the root user. The rootless tag is no longer used for future releases.