Activity and Logs

Applies to: all AppWizzy projects

AppWizzy shows different records for hosted VMs and generated applications. The selected template controls which log interface is available.

The AppWizzy log page does not replace logs that your operating system or application stores inside a VM.

Find the available records

  1. Open the AppWizzy project.
  2. Select Logs or Usage & Activity.
  3. Review the tabs and filters shown for that project.

Use the project overview to check current provisioning or VM status. Use project billing to review credit charges and refunds.

Hosted VM activity

Hosted VM projects show Tokens and Events when these records exist.

The Tokens tab can show:

  • event time.
  • model name.
  • prompt token count.
  • completion token count.
  • total token count.
  • totals for the selected project scope.

The Events tab can show:

  • event time.
  • event type.
  • success or error status.
  • a short event message.

Events can include project changes, deployments, restarts, and other recorded operations. The available event types depend on project activity.

Token counts describe measured AI use. Open project billing to review the related AppWizzy credit transactions.

Generated application service logs

App Generation projects can show service logs for development and stable environments.

Available filters can include:

  • severity: Error, Warning, Info, or All.
  • environment: Development or Stable.
  • start time.
  • end time.

Select Refresh to load the latest matching records. Select Reset to restore the default filters.

These service logs apply to generated application environments. They do not describe every AppWizzy hosted VM.

Logs inside a hosted VM

Use SSH or a supported workspace terminal to inspect operating system and application logs inside a VM.

The commands and file paths depend on the installed operating system, runtime, and application. Follow the selected template and application documentation.

The AppWizzy activity page does not currently provide a general operating system log viewer for hosted VMs.

Read an error record

Record this information before you make changes:

  • project name and status.
  • event time.
  • event type or log source.
  • complete error message.
  • action that occurred before the error.
  • affected URL or service.

Search nearby records for the first error. A later error can be a result of the first failure.

Do not publish logs without review. Logs can contain file paths, email addresses, request data, or authentication information.

When no records appear

Complete these checks:

  1. Confirm that the project has finished provisioning.
  2. Confirm that you selected the correct environment or tab.
  3. Expand the selected time range.
  4. Select All when a severity filter is available.
  5. Refresh the page once.
  6. Confirm that the relevant operation occurred.

If the problem continues, contact AppWizzy support. Include the project name, time, status, and error text.

Do not send passwords, private keys, provider keys, or complete access tokens.