Logs & troubleshooting

Use the Logs page to filter, live-tail and export system activity, and troubleshoot common errors.

The Logs page lets you view system activity and debug issues with your APIs and connections. Only organization admins can access this page.

Accessing the Logs page

Go to the sidebar and click Logs (visible only if you're an admin)
You'll see the system logs viewer with all recorded activity

Reading system logs

Logs are displayed in a terminal-style format with:

Timestamp - When the event occurred (YYYY-MM-DD HH:MM:SS in your local time)
Level - Severity of the event:
- INFO - General informational messages (gray)
- WARN - Warning messages that don't stop functionality (amber)
- ERROR - Error events that need attention (red)
- DEBUG - Detailed diagnostic information (blue)
Message - Description of what happened
Latency - How long the operation took (if applicable)

Filtering and searching logs

Filter by level

Use the tabs at the top to view specific log types:

All - Show all log entries
Errors - Only ERROR level messages
Warnings - Only WARN level messages

Search logs

Type in the Filter logs... search box to find specific messages. Searches are applied in real-time as you type.

Pagination

Logs are shown 50 entries per page. Use the Previous and Next buttons at the bottom to navigate between pages. The button text shows "Page X of Y" so you know where you are.

Live tail

Toggle the Live tail button to automatically refresh logs every 5 seconds. When enabled, you'll see an animated indicator on the button. This is useful for monitoring real-time activity:

Click Live tail to enable
New entries appear automatically every 5 seconds
Click Live tail again to stop monitoring

Exporting logs

To save logs to a file:

Make sure at least one log entry is visible (use filters if needed)
Click the Export button
A CSV file downloads with all visible log entries

The exported file includes timestamp, level, message, and latency for each entry.

Common log messages and what they mean

Connection and database errors

"Failed to connect to database" - RestWard can't reach your database. Check that your connection credentials are correct and the database is online.
"Connection timeout" - The database took too long to respond. This may indicate network issues or a slow/overloaded database.
"Authentication failed" - The username or password for your database connection is incorrect.

API and endpoint errors

"API endpoint not found" - The endpoint configuration is missing or deleted. Check the Endpoints page to recreate it.
"Rate limit exceeded" - Too many requests hit the API in a short time. Requests are rejected to protect your infrastructure.
"Invalid request payload" - The request body didn't match the expected schema. Check the API documentation for correct formatting.

Request errors

"Request timeout" - The API or database didn't respond within the time limit. Try again, or check if your database is overloaded.
"HTTP 500 - Internal Server Error" - An unexpected error occurred. Check the logs for more details or contact support.
"HTTP 403 - Forbidden" - The API key or credentials used don't have permission for this request.
"HTTP 404 - Not Found" - The endpoint or resource doesn't exist.

Authentication and security

"API key revoked" - An API key was disabled or expired. Generate a new one in Auth & Keys.
"Unauthorized access attempt" - Someone tried to access an endpoint with invalid credentials.
"CORS policy violation" - A request from an unauthorized domain was blocked for security.

Troubleshooting

"You don't have permission to view logs"

Only organization admins can access the Logs page. Contact your organization admin if you need log access.

Logs not loading

If you see "Failed to load logs" error:

Click Retry to try again
Refresh the page if the issue persists
Check that you have a stable internet connection

Can't find a specific log entry

Use the search box to filter by keywords
Use the level tabs to narrow by severity
Logs are paginated; use Previous/Next to browse older entries
Export logs to search offline if you need historical data

Live tail not updating

Make sure the Live tail button is enabled (animated)
Check your internet connection
Try toggling it off and back on

Understanding log patterns

Look for these patterns when troubleshooting:

API is slow

Check for timeout or latency messages in Errors. Your database may be overloaded, or there's a network issue.

APIs return errors frequently

Filter logs to Errors and look for repeating patterns. Common causes:

Database connection problems (fix the connection settings)
Rate limiting (your API is getting more traffic than configured)
Schema mismatches (your database changed but the API definition didn't)

Recent changes broke something

New ERROR entries after a recent change are a clue. Review what changed on your Endpoints and Connections pages.

Tenants - For provisioning and tenant-level issues
Dashboard & navigation - For general navigation