doc.overops.com

Naming Your Application and Deployment

Naming your applications and deployment allows us to aggregate your data and to sort, view, and compare them from version over version. The data then feeds into our dashboards (without using a naming convention your data loses value):

  • Give the application a name you'll be able to easily track
  • Give your deployment a distinct name so that whenever you deploy new code to your application, you'll be able to distinguish between different deployments that will show up in the OverOps Dashboard

Use these arguments for the application name and deployment name:
-Dtakipi.application.name=<APPLICATION_NAME>
-Dtakipi.deployment.name=<DEPLOYMENT_NAME>

To learn more, see Naming the Application, Server, Deployment.

Attaching the OverOps Agent to a JVM Running Java 10 or 11

When attaching an OverOps Agent to a JVM that is running Java 10 or 11 or any IBM java versions, follow these guidelines:

  1. Turn off Class Sharing: This can be done using the following flags:
    for IBM Java
    ‑Xshareclasses:none
    for HotSpot
    -Xshare:off -XX:-UseTypeSpeculation

  2. Increase ReservedCodeCache to at least 512mb by adding the following flag
    -XX:ReservedCodeCacheSize=512m

  3. The Agent should appear last in the VM arguments list before specifying the main class or jar.

  4. When adding/removing 3rd party packages, the Agent should be restarted.

Additionally, if you wish to upgrade your own compiler to target Java 10/11, then you'll have to upgrade your Collector (SaaS) or Collector + backend (On-Premises) to support it.

There are two scenarios to connect OverOps to Jetty: the Jetty Server can be embedded or the existing Jetty server on which customer application is running.

Embedded Jetty

To connect OverOps to embedded Jetty:

  • Add the following argument to your JVM startup arguments:
    -agentlib:TakipiAgent

Rootless Agent Installation Method (Linux only)

When Using the Rootless Agent Installation Method replace the
-agentlib:TakipiAgent JVM startup Argument
with
-agentpath:<TAKIPI_HOME>/lib/libTakipiAgent.so JVM startup Argument

Important

The -agentlib is a JVM argument and should be written before the -jar / -cp arguments. For example:
java -Xmx2G -agentlib:TakipiAgent -jar myapp.jar
or respectively
java -Xmx2G -agentpath:<TAKIPI_HOME>/lib/libTakipiAgent.so -jar myapp.jar

Standalone Jetty

To connect OverOps to Jetty running on Linux, add the following argument to your JVM startup arguments:


1. In the /bin/ directory, locate the jetty.sh file used to run Jetty.
2. Go to the following line:

JAVA_OPTIONS="$JAVA_OPTIONS -Djetty.home=$JETTY_HOME -Djetty.base=$JETTY_BASE -Djava.io.tmpdir=$TMPDIR"

3. Below this line, add the following:
```JAVA_OPTIONS="-agentlib:TakipiAgent $JAVA_OPTIONS"
  1. Restart Jetty.
  2. Test your Installation.

Updated 5 months ago

Jetty


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.