> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/setup-and-configuration/troubleshooting-faq/golang/how-to-confirm-my-deployed-golang-app-binary-is-instrumented.md). # How to Confirm My Deployed Golang App Binary Is Instrumented When deploying a Go application instrumented with Sealights, you may want to verify whether the final binary actually contains the Sealights instrumentation code. ## 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 | grep "__sealights__" ``` {% endtab %} {% tab title="Powershell" %} ```powershell go tool nm | Select-String "__sealights__" ``` {% endtab %} {% endtabs %} If no output appears, the binary is not instrumented. Otherwise, you'll see lines such as:
## **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 --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.sealights.io/knowledgebase/setup-and-configuration/troubleshooting-faq/golang/how-to-confirm-my-deployed-golang-app-binary-is-instrumented.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.