Versions Compared

Old Version 53

changes.mady.by.user Marc Amouyal

Saved on

compared with

New Version Current

changes.mady.by.user Marc Amouyal

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Tip

When the application is up and running and the Sealights Listener agent configured, you can it is properly running from the Cockpit -> Agent Monitor screen.
You also have the ability to validate the JVM parameters in use with your application via the following command

  • Linux:  ps -ef | grep java

  • Windows: Get-CimInstance Win32_Process | Where-Object { $_.Name -like '*java*' } | Select-Object CommandLine, ProcessId (Powershell)

    • CMD Promt: C:\\Windows\\System32\\wbem\\WMIC.exe process where "name like '%java%'" get commandline,processid

    (CMD prompt)

Warning

If the agent does not appear in the Cockpit Agent Monitor when your application is up and running, you can turn on the logging of the Sealights agent by adding one or both of the following parameters:

  • Console Output: -Dsl.log.level=info -Dsl.log.toConsole=true

  • File Output: -Dsl.log.level=info -Dsl.log.toFile=true -Dsl.log.folder=<path/to/folder/with/writing/permissions/>

More details about these parameters are detailed in a dedicated documentation section https://sealights.atlassian.net/wiki/spaces/SUP/pages/1933323/SeaLights+Java+agent+-+Command+Reference#Logging

...