# Setup & access Deno logs


Zerops provides 3 different logs for your deno service:

- [Build log](#build-log) - Output from your build process
- [Prepare runtime log](#prepare-runtime-log) - Custom runtime image creation
- [Runtime log](#runtime-log) - Operational output from your running service

## Quick access to logs

### Build log
- **GUI**: Service detail → **Pipelines & CI/CD settings** → Pipeline detail → **Build log**
- **CLI**: `zcli service log --showBuildLogs`

### Prepare runtime log
- **GUI**: Service detail → **Pipelines & CI/CD settings** → Pipeline detail → **Prepare runtime log**
- **CLI**: *Not currently supported*

### Runtime log
- **GUI**: Service detail → **Runtime log**
- **CLI**: `zcli service log`

:::note
For severity levels to work properly in Zerops, your application must log to syslog.
:::

## Beyond basic logging

Zerops offers additional observability options to help you monitor and debug your application:

### Log Forwarding
Forward logs to [external services](/references/log-forwarding) for advanced analysis and long-term storage, including Better Stack, Papertrail, self-hosted ELK stack with Logstash, or any syslog-ng compatible software.

### Full Observability Stack
Deploy [self-hosted observability solutions](/references/metrics) for comprehensive monitoring with ELK Stack (centralized logging with Kibana + application tracing with APM) or Prometheus & Grafana (metrics collection, visualization, and custom dashboards).