# Creating Logs

One way to debug apps is by logging information in the code. This enables seeing which code was run when a problem occurred and what the value of variables were. You can directly call [`GLib.Log ()`](https://valadoc.org/glib-2.0/GLib.log.html) or use the convenience functions listed below.

{% hint style="info" %}
To view logs from all your applications you can use [`journalctl`](https://www.digitalocean.com/community/tutorials/how-to-use-journalctl-to-view-and-manipulate-systemd-logs).
{% endhint %}

## Debug

Debug logs usually give detailed information on the flow through the system and are not printed to Terminal or logs by default.

Log functions, like `debug` use [`printf`](http://www.cplusplus.com/reference/cstdio/printf/) style formatting and can be called like this:

```vala
string name = "Bob";
int age = 30;
debug ("Person: %s %i", name, age);
```

{% hint style="info" %}
Start your app with `G_MESSAGES_DEBUG=all` to print debug messages
{% endhint %}

## Info

Use info log level to log informational messages as well as interesting runtime events. These logs are also immediately visible on a status console, and should be kept to a minimum.

```vala
info ("An event occurred");
```

## Message

Use the message log level to output a message.

```vala
message ("An event occurred");
```

## Warning

The warning log level outputs messages that warn of, for example, use of deprecated APIs, 'almost' errors, or runtime situations that are undesirable or unexpected, but not necessarily "wrong". These logs are immediately visible on a status console.

```vala
warning ("Something potentially problematic happened!");
```

{% hint style="info" %}
Start your app with `G_DEBUG=fatal-warnings` to exit the program at the first call to `warning ()` or `critical ()`
{% endhint %}

## Critical

Critical log level is used when there is a severe application failure that should be investigated immediately.

```vala
critical ("A major issue occurred! Uh oh!");
```

{% hint style="info" %}
Start your app with `G_DEBUG=fatal-criticals` to exit the program at the first call to `critical ()`
{% endhint %}

## Error

Error log level includes logs for runtime errors or unexpected conditions. These errors are immediately visible on a status console and cause your app to exit.

```vala
error ("Some catastrophic happened and the app had to exit!");
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.elementary.io/develop/writing-apps/logging.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.