Send a Diagnostic Snapshot to Stibo Systems

SPOT can be used to pull diagnostic information about the STEP environment and subsequently upload the snapshot automatically so that Stibo Systems Support can quickly identify any issues. If a Jira ticket has already been created with Stibo Systems, there is an option to assign the snapshot directly to a ticket number.

Note: To use this capability, the STEP environment must be able to access Stibo Systems’ updates server (https://updates.stibosystems.com).

Pull all diagnostic information and upload it to Stibo Systems

  1. Go to the directory where STEP is installed. The default path is /opt/stibo/step
  1. Run the SPOT command as follows:

./spot –d

or alternatively,

./spot --diag

Pull all diagnostic information and store it in a file

  1. Go to the directory where STEP is installed. The default path is /opt/stibo/step
  1. Run the SPOT command as follows:

./spot –d --output=<FILE_NAME>

or alternatively,

./spot --diag --output=<FILE_NAME>

Pull all diagnostic information and include profiling data or heap dumps

  1. Go to the directory where STEP is installed. The default path is /opt/stibo/step
  1. Run the SPOT command as follows to include Profiling Data:

./spot –d --target=profiling

or alternatively,

./spot --diag --target=profiling

  1. Run the SPOT command as follows to include Heap Dumps:

./spot –d --target=heapdumps

or alternatively,

./spot --diag --target=heapdumps

  1. Run the SPOT command as follows to include All Data:

./spot –d --target=all

or alternatively,

./spot --diag --target=all

Additional options

  • --issue=<JIRA_ISSUE> – the Stibo Jira issue (e.g., STIBO-1) to which this diagnostics snapshot relates
  • --history=<TIME_PERIOD> – sets how far back in time to collect diagnostics; the default is 1 day. The history option takes days, hours, minutes, and seconds – e.g., 2d, 3h, 60m, 86400s