> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/continuous-error-tracking/get-started/overops-cet-migration.md).

# Upgrade from OverOps to CET

Upgrading your service from OverOps to CET involves the following steps:

1. Choose a service suitable for onboarding to CET, preferably starting with a non-production service.
2. Create a project in the CET.
3. Set up a monitored service.
4. Install the Harness Error Tracking Agent and configure it with the monitored service.

   After successfully installing the agent and ensuring that your application is running, you'll be able to view the events reported by the agent.
5. Configure notifications for timely event alerts.

### Select a service for CET onboarding <a href="#select-an-appropriate-service-for-onboarding-to-cet" id="select-an-appropriate-service-for-onboarding-to-cet"></a>

Follow the steps below to choose an appropriate service for onboarding to CET.

1. Select non-production service to onboard onto Harness CET. For instance:
   * Name: cet-migration
   * Environment: Staging2
2. Get a Harness account from the CSM by submitting a request using <support@harness.io>.
3. Request a CET license for your Harness account.

### Set up a project <a href="#setup-project" id="setup-project"></a>

Follow the steps below to set up a project:

1. Log in to your Harness account and navigate to the Error Tracking module.

   ![Setup New Project](/files/iVHbHKdBmrfIeqhE6DoJ)
2. Create a project under the ‘default’ organization.

   ![Create New Project](/files/XBpybBBx2eljFNIrWHsu)
3. Once your project is created, navigate to it to continue the setup.

   ![Select New Project](/files/3yyRR1JHwlBvX8ScKMig)

### Add a monitored service <a href="#add-a-monitored-service" id="add-a-monitored-service"></a>

A Harness monitored service combines a specific service with an environment to monitor code-level exceptions and errors collected by the Error Tracking Agent. Follow these steps to create a monitored service and specify the service and environments for tracking code errors and exceptions:

1. In your Harness project, navigate to the **Continuous Error Tracking** module, and then select **Monitored Services**.
2. Select **+ Create Monitored Service**.

   The Create New Monitored Service page appears.

   ![Navigate to Monitored Services](/files/Njt9ROSuI8aC9fuFgq0b)
3. Select a service. A Service represents your microservices or other workloads. To add a new service do the following:
   1. Select **+ New Service**. ![Add New Service](/files/nGjp8NYdlA2qWmU9nnnE)
   2. In the New Service dialog, enter a **name** for the service, optional **tag**, and optional **description**, and then select **Save**. ![Select Service Name](/files/GKk7lcNHfYyiKPjGkxZf)
4. Select an environment where the Harness Service is deployed (QA, prod, and so on). To create a new environment:

   1. Select **+ New Environment**. ![Select New Environment](/files/xTOnExRvMxE0uHc5CVwD)
   2. In the Create Environment dialog, enter a name for the new environment, select an environment type such as production or pre-production, and then select **Save**. ![Create New Environment](/files/xwNMbg4W8kODaEQZhjRN)

   Harness auto creates the monitored service name by combining the service and environment names that you have entered.

   ![Navigate to Monitores Services](/files/9R9cHDhVqJSBnW1jQtmn)
5. Select **Save**.

   The new monitored service appears on the Monitored Services page. ![Navigate to Monitores Services](/files/KMakGG0G6AkN1dBexv4L)

### Create a token for the Error Tracking Agent <a href="#create-a-token-for-the-error-tracking-agent" id="create-a-token-for-the-error-tracking-agent"></a>

Follow these steps to create a token for the Error Tracking Agent:

1. Expand **PROJECT SETUP** and then select **Tokens**.
2. On the Code Error Settings page, select **Generate New Token**.

   ![Create Token](/files/AVGgd6rI3fVD8zptbO0b)
3. In the New Token dialog, enter a name for the token and select **Generate**.

   A new authentication token is generated and displayed in the **Key** field.
4. Copy the token to clipboard. This token is used in the Error Tracking Agent configuration file.

   ![Generate new token](/files/kZ4KDmyaInNQIMsNFkHl)
5. Select **Close**.

   The newly created token appears on the list of tokens.

{% hint style="info" %}
**NOTE**

You can copy the token anytime by selecting the clipboard icon.
{% endhint %}

### Install an Error Tracking Agent <a href="#install-an-error-tracking-agent" id="install-an-error-tracking-agent"></a>

The Harness Error Tracking Agent must be installed on a Java application to capture application code and variables. This native agent library is attached to the Java Virtual Machine (JVM)/Common Language Runtime (CLR) during runtime. It can be deployed into any Kubernetes container without altering the image. The Agent fingerprints the program code loaded into the JVM/CLR and captures the complete state of the code and the host/container in order to identify anomalies. The Harness Error Tracking Agent must be installed on Java applications, allowing it to capture application code and variables. This native agent library attaches itself to the Java Virtual Machine (JVM) or Common Language Runtime (CLR) during runtime. It can be deployed within any Kubernetes container without altering the image. The Agent profiles the program code loaded into the JVM/CLR and captures the complete state of the code and the host/container to identify anomalies.

The following sections provide details about:

* Compatibility and requirements to install an Error Tracking Agent.
* Latest releases
* Instructions to install the Error Tracking Agent on a Java Application.

### Compatibility and requirements <a href="#compatibility-and-requirements" id="compatibility-and-requirements"></a>

To learn about supported operating systems such as Java Virtual Machine (JVM) and JVM containers, go to [Continuous Error Tracking Agent compatibility](/continuous-error-tracking/whats-supported.md).

### Latest releases <a href="#latest-releases" id="latest-releases"></a>

| **OS**   | **Download Link**                                                                    |
| -------- | ------------------------------------------------------------------------------------ |
| Linux    | [Download](https://get.et.harness.io/releases/latest/nix/harness-et-agent.tar.gz)    |
| Alpine   | [Download](https://get.et.harness.io/releases/latest/alpine/harness-et-agent.tar.gz) |
| Graviton | [Download](https://get.et.harness.io/releases/latest/arm/harness-et-agent.tar.gz)    |
| Windows  | [Download](https://get.et.harness.io/releases/latest/win/harness-et-agent.zip)       |
| AIX      | [Download](https://get.et.harness.io/releases/latest/aix/harness-et-agent.tar.gz)    |
| Mac      | [Download](https://get.et.harness.io/releases/latest/osx/harness-et-agent.tar.gz)    |

### Install an Error Tracking Agent <a href="#install-an-error-tracking-agent" id="install-an-error-tracking-agent"></a>

Depending on your setup and needs, there are multiple ways to install and deploy an Error Tracking Agent on a Java application. You can install the Agent to monitor your application in the following ways:

* As a standalone installation outside Harness.
* By modifying your Docker image.
* Using an init container.

If you have additional agents running on your application, the Error Tracking Agent should appear at the end of the VM arguments list before specifying the main class or jar.

{% tabs %}
{% tab title="Standalone" %}
This option lets you install the Error Tracking Agent as a standalone. Perform the following steps to install the Agent:

1. Download the latest version of the Agent from [here](#latest-releases).
2. Extract this version to a folder of your choice. For example`/home/user`. The contents of the archive will be inside a folder named Harness. You'll require the path to the Agent when starting your application. An example for the Agent path would be, `/home/user/harness/lib/libETAgent.so`.
3. Add JVM arguments which instruct the JVM to load the Agent.

This is done by adding `-agentpath:/home/user/harness/lib/libETAgent.so` to the application startup. For example:

```
`java -agentpath:/home/user/harness/lib/libETAgent.so -jar yourapp.jar`.
```

This parameter can also be specified using `JAVA_TOOL_OPTIONS`. For example:

```
`export JAVA_TOOL_OPTIONS=-agentpath:/home/user/harness/lib/libETAgent.so`.
```

4\. Set the Agent environment variables so that your application can map to a Harness Service.

| **Required Environment Variable** | **Description**                                                                                                                                                                                                                                                  | **Example**                              |
| --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------- |
| `ET_COLLECTOR_URL`                | URL to the Error Tracking collector.                                                                                                                                                                                                                             | `https://collector.et.harness.io/prod1`  |
| `ET_APPLICATION_NAME`             | Name of your application or Service.                                                                                                                                                                                                                             | `cetmigration`                           |
| `ET_DEPLOYMENT_NAME`              | Deployment or version number of your application or Service. When your application or Service is updated to a new version, it's recommended that you update this variable as well, so that the Error Tracking Agent can identify when new errors are introduced. | `1`                                      |
| `ET_ENV_ID`                       | ID of your Harness Environment.                                                                                                                                                                                                                                  | `staging`                                |
| `ET_TOKEN`                        | ET Agent Token created on Harness.                                                                                                                                                                                                                               | `b34*****-****-****-****-***********42a` |

For example:

```
ENV ET_COLLECTOR_URL=https://collector.et.harness.io/prod1/
ENV ET_APPLICATION_NAME=cetmigration
ENV ET_DEPLOYMENT_NAME=1
ENV ET_ENV_ID=staging
ENV ET_TOKEN=b34*****-****-****-****-***********42a
```

5. Restart your application after installing the Error Tracking Agent.
   {% endtab %}

{% tab title="Docker image" %}
This option uses a Dockerfile to copy an Error Tracking Agent to the Docker image at build time. When your Java application is running using Docker, perform the following steps to install the Agent:

1. Download and extract the Agent in your Dockerfile. For example:

```
RUN wget -qO- https://get.et.harness.io/releases/latest/nix/harness-et-agent.tar.gz | tar -xz
```

2. Set the Agent environment variables in the Dockerfile.

| **Required Environment Variable** | **Description**                                                                                                                                                                                                                                                  | **Example**                              |
| --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------- |
| `ET_COLLECTOR_URL`                | URL to the Error Tracking collector.                                                                                                                                                                                                                             | `https://collector.et.harness.io/prod1`  |
| `ET_APPLICATION_NAME`             | Name of your application or Service.                                                                                                                                                                                                                             | `cetmigrationpoc`                        |
| `ET_DEPLOYMENT_NAME`              | Deployment or version number of your application or Service. When your application or Service is updated to a new version, it's recommended that you update this variable as well, so that the Error Tracking Agent can identify when new errors are introduced. | `1`                                      |
| `ET_ENV_ID`                       | ID of your Harness Environment.                                                                                                                                                                                                                                  | `staging`                                |
| `ET_TOKEN`                        | ET Agent Token created on Harness.                                                                                                                                                                                                                               | `b34*****-****-****-****-***********42a` |

For example:

```
ENV ET_COLLECTOR_URL=https://collector.et.harness.io/prod1
ENV ET_APPLICATION_NAME=cetmigrationpoc
ENV ET_DEPLOYMENT_NAME=1
ENV ET_ENV_ID=staging
ENV ET_TOKEN=b34*****-****-****-****-***********42a
```

3. Add JVM arguments to the Docker image, which instructs the JVM to load the Agent. This is done by adding `agentpath:/harness/lib/libETAgent.so`to the application `ENTRYPOINT`. For example, `ENTRYPOINT java -agentpath:/harness/lib/libETAgent.so -jar yourapp.jar`. This parameter can also be specified using `JAVA_TOOL_OPTIONS`, for example `ENV JAVA_TOOL_OPTIONS="-agentpath:/harness/lib/libETAgent.so"`.
4. Once the Dockerfile is updated, rebuild the Docker image and restart any containers running on it to start monitoring using Error Tracking.

```
 FROM openjdk:8-jre
ENV JAVA_TOOL_OPTIONS="-agentpath:/harness/lib/libETAgent.so"
ENV ET_COLLECTOR_URL=https://collector.et.harness.io/prod1/
ENV ET_APPLICATION_NAME=cetmigrationpoc
ENV ET_DEPLOYMENT_NAME=1
ENV ET_ENV_ID=staging
ENV ET_TOKEN=b34*****-****-****-****-***********42a
RUN wget -qO- [https://get.et.harness.io/releases/latest/nix/harness-et-agent.tar.gz](https://get.et.harness.io/releases/latest/nix/harness-et-agent.tar.gz) | tar -xz
ENTRYPOINT java -jar yourapp.jar
```

{% endtab %}

{% tab title="Init container" %}
When your Java application is running on Kubernetes, you can use an init container to automatically install the Agent at runtime without changing the existing images. The image is publicly hosted in [Docker Hub](https://hub.docker.com/r/harness/et-agent-sidecar).

Consider the following Kubernetes deployment example for a Java application:

```
kind: Deployment
spec:
  template:
    spec:
      volumes:
        - name: et-agent
          emptyDir: {}
      initContainers:
        - name: init-et-agent
          image: harness/et-agent-sidecar
          imagePullPolicy: Always
          volumeMounts:
            - name: et-agent
              mountPath: /opt/harness-et-agent

      containers:
        - name: my-javaapp-container
          image: my-javaapp-image
          env:
            - name: JAVA_TOOL_OPTIONS
              value: "-agentpath:/opt/harness-et-agent/harness/lib/libETAgent.so"
            - name: ET_COLLECTOR_URL
              value: "https://collector.et.harness.io/prod1/"
            - name: ET_APPLICATION_NAME
              value: cetmigrationpoc
            - name: ET_DEPLOYMENT_NAME
              value: 1
            - name: ET_ENV_ID
              value: staging
            - name: ET_TOKEN
              value: b34*****-****-****-****-***********42a
          volumeMounts:
            - name: et-agent
              mountPath: /opt/harness-et-agent
```

By using a shared volume, the init-container executes and installs the harness-et-agent in the path `/opt/harness-et-agent`. This installation is then mounted into the target container `my-javaapp-container` using the volume mount. To properly configure and optimize the functionality of the Agent, ensure to set the variables listed in the following table:

| **Required Environment Variable** | **Description**                                                                                                                                                                                                                                                  | **Example**                                                  |
| --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------ |
| `JAVA_TOOL_OPTIONS`               | JVM Option which instructs the JVM to load the Agent at the mounted volume location.                                                                                                                                                                             | `-agentpath:/opt/harness-et-agent/harness/lib/libETAgent.so` |
| `ET_COLLECTOR_URL`                | URL to the Error Tracking collector.                                                                                                                                                                                                                             | `https://collector.et.harness.io/prod1`                      |
| `ET_APPLICATION_NAME`             | Name of your application or Service.                                                                                                                                                                                                                             | `cetmigrationpoc`                                            |
| `ET_DEPLOYMENT_NAME`              | Deployment or version number of your application or Service. When your application or Service is updated to a new version, it's recommended that you update this variable as well, so that the Error Tracking Agent can identify when new errors are introduced. | `1`                                                          |
| `ET_ENV_ID`                       | ID of your Harness Environment.                                                                                                                                                                                                                                  | `staging`                                                    |
| `ET_TOKEN`                        | ET Agent Token created on Harness.                                                                                                                                                                                                                               | `b34*****-****-****-****-***********42a`                     |

If the agent is already installed as part of your docker image, simply set the corresponding environment variables without the need of an init container.
{% endtab %}
{% endtabs %}

{% hint style="info" %}
**NOTE**

If you are using the Self-Managed Enterprise Edition, make sure to set the ET\_COLLECTOR\_URL to your Load Balancer URL. For instance, if your Helm value is `loadbalancerURL: https://example.harness.io/`, then set the `ET_COLLECTOR_URL` as `ET_COLLECTOR_URL=https://example.harness.io/et-collector`.
{% endhint %}

### Verify agent connection <a href="#verify-agent-connection" id="verify-agent-connection"></a>

After installing Error Tracking Agent, you should verify that it is connected to Harness. To verify the Error Tracking Agent connection, do the following:

* Expand **PROJECT SETUP** and then select **Agents**.

  A comprehensive list of Error Tracking Agents is displayed along with the information such as service name, environment, deployment version, Agent version, Agent status, token name, and so on. Ensure that the Agent that you installed is listed, and the status is **CONNECTED**.

### Configure notifications <a href="#configure-notifications" id="configure-notifications"></a>

Configure notifications for timely event alerts. To learn how to notifications, go to [Notifications](/continuous-error-tracking/cet-notifications.md).

### Next steps <a href="#next-steps" id="next-steps"></a>

Identify and prioritize error events using [Events dashboard](/continuous-error-tracking/get-started/cet-event-dashboard.md).