Adding the Sealights java agent into you Pivotal Cloud Foundry / VMWare Tanzu Application Services is done by using the standard java buildpack.

Info
Complimentary information is detailed in https://github.com/cloudfoundry/java-buildpack/blob/main/docs/framework-sealights_agent.md

Prerequisite: Installing CF Java buildpack

...

hard-code them in manifest.yml:

Code Block

language	yaml

env:
  JBP_CONFIG_SEALIGHTS_AGENT: '{lab_id: yourLabId}'

pass them as environment variables for the application:

Code Block
cf set-env [my-application] JBP_CONFIG_SEALIGHTS_AGENT: '{lab_id: myLabId}'

...

Available configuration keys are

Name	Description
`build_session_id`	Sealights' Build Session ID for the application. Leave blank to use the value embedded in the jar/war artifacts
`proxy`	Specify a HTTP proxy used to communicate with the Sealights backend. Required when a corporate network prohibits communication to cloud services. The default is to have no proxy configured. This does not inherit from `http_proxy`/`https_proxy` or `http.proxyHost/https.proxyHost`, you must set this specifically if a proxy is needed.
`lab_id`	Specify a Sealights Lab ID
`auto_upgrade`	Enable/disable agent auto-upgrade. Off by default.
`version`	The version of Auto-reconfiguration to use. Candidate versions can be found in this listing. If `auto_upgrade` is turned on, a different version may be downloaded and used at runtime

Versions Compared