Visor (Logs)

The Deta Visor offers a user interface for you to see a live view of all the events (logs) processed by your Micro. You can use it to monitor and debug your requests, test your endpoints by sending requests, and more.

By default, Visor is disabled, to enable it run deta visor enable in your terminal inside you Micro's source code.

Opening Visor#

Start by logging into your console at You should be redirected to the following screen:


Once that's done, choose a micro to view by clicking on its name (under the "Micros" tab).


Now click on "Visor"


Navigating the Visor#

The Visor page has the link to your Micro in the top right, a button named "HTTP Client" in the bottom left, and a list of all the events handled by your Micro!


The Event List#

The Visor logs every single event made to your Micro, each event has the HTTP Status Code, the HTTP Method, and the time logged above it. Under this information are three tabs, letting you view the response, request, and logs of the event.



The Request sent to the Micro:


And logs (normally displaying errors if they were to occur):


On the top right of every event are two icons:


The "pen" icon lets you edit the request before re-sending it to your micro and the "redo" icon lets you send the same request again.

The HTTP Client#

Visor also has a built in "HTTP Client" to make requests to your Micro. You can use this by clicking on the "HTTP Client" button.

HTTP Client

Simply specify the request method, path, headers and body and hit the "Send" button to send it off!

HTTP Client Modal

The content-type can be changed from JSON to Text, using the selection box on the bottom left of this window.

HTTP Client JSON to Text

Video overview#

Logs Retention#

Visor logs are retained for two weeks (14 days).

Visor doesn't show the error#

Sometimes you will get a 500 response from our server and no errors will show up in Visor, in that case you could quickly check our system logs for you Micro with deta logs.


If you run into any issues, consider reporting them in our Github Discussions.