# How to Confirm My Deployed Golang App Binary Is Instrumented

## Problem

You do **not** see any Sealights‑related instrumentation output in your application logs, and your service does **not** appear listed in the **Live Agents** page in the Sealights Cockpit.

You’re unsure whether:

* the binary was properly instrumented, or
* the environment prevents the agent from activating

## Solution

### Quick Environment Checks

#### **Enable verbose Sealights logs**

Make the agent print startup information:

```bash
export SEALIGHTS_LOG_LEVEL=debug
export SEALIGHTS_DISABLE_ON_INIT=false
```

Restart the app (or container) and check logs.

#### **Check the token and connectivity**

* Ensure a valid Sealights token is provided (env var, config, secret).
* Confirm the app can reach the Sealights endpoint (network, proxy, DNS).

*A missing token or blocked network path prevents the agent from initializing.*

### Binary Level Verification

To confirm whether the binary was correctly instrumented, inspect it for the internal Sealights probe symbols. Run

{% tabs %}
{% tab title="Bash" %}

```bash
go tool nm <your-executable> | grep "__sealights__"
```

{% endtab %}

{% tab title="Powershell" %}

```powershell
go tool nm <your-executable> | Select-String "__sealights__"
```

{% endtab %}
{% endtabs %}

If no output appears, the binary is not instrumented. Otherwise, you'll see lines such as:

<figure><img src="https://4057366433-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAjqTCMRYvHhDgsdPLUnc%2Fuploads%2FhR6UbtI7NTjvDaJIfCC3%2Fimage.png?alt=media&#x26;token=6c25ebf7-f5cd-47b0-9bf8-a90eb33060a9" alt=""><figcaption></figcaption></figure>

## **If the Binary Is Not Instrumented**

Check the following in your build pipeline:

* Sealights instrumentation step actually ran
* Instrumentation was executed **on the final compiled binary**, not an intermediate artifact
* The correct artifact was deployed
* No stripping/minification removed symbols