diff --git a/404.html b/404.html index 36cc9929bd..99acb5e0d5 100644 --- a/404.html +++ b/404.html @@ -15,9 +15,9 @@ - - - + + +
Skip to main content

Logging

Logging acts as an essential tool for obtaining insights into code execution and addressing software development challenges. You can configure the verbosity of logs via log levels. Use TAILCALL_LOG_LEVEL or TC_LOG_LEVEL environment variables to set the application's log level. The available log levels include:

error​

This is the highest severity level. It indicates a critical issue that may lead to the failure of the program or a part of it.

TAILCALL_LOG_LEVEL=error tailcall <COMMAND>
# or
TC_LOG_LEVEL=error tailcall <COMMAND>
@@ -45,6 +45,6 @@

off
info

The default log level is info.

Log levels are hierarchical, meaning if you set the log level to a specific level, it includes all the levels above it. For example, setting the log level to info will include logs at the info, warn, and error levels, but exclude debug and trace logs.

Hierarchy of Log Levels

-
info

You can specify log levels in either uppercase or lowercase; both yield the same result. For example, TAILCALL_LOG_LEVEL=DEBUG and TAILCALL_LOG_LEVEL=debug are same.

+
info

You can specify log levels in either uppercase or lowercase; both yield the same result. For example, TAILCALL_LOG_LEVEL=DEBUG and TAILCALL_LOG_LEVEL=debug are same.

\ No newline at end of file diff --git a/docs/guides/n+1/index.html b/docs/guides/n+1/index.html index 57ac30a485..c47b1fc23e 100644 --- a/docs/guides/n+1/index.html +++ b/docs/guides/n+1/index.html @@ -15,15 +15,15 @@ - - - + + +
Skip to main content

Tackling N + 1

The N+1 problem is a pervasive and critical issue in application development that occurs when an application ends up issuing a large number of downstream requests, for a single request from upstream. Let's understand with an example:

+ Star

Tackling N + 1

The N+1 problem is a pervasive and critical issue in application development that occurs when an application ends up issuing a large number of downstream requests, for a single request from upstream. Let's understand with an example:

Scenario​

Consider we're developing a feature that involves consuming data from the JSON Placeholder API. The feature requires fetching posts and the details of the authors of these posts.

Here's an illustration of a typical implementation:

diff --git a/docs/guides/watch-mode/index.html b/docs/guides/watch-mode/index.html index 7ca3979283..60d235c30b 100644 --- a/docs/guides/watch-mode/index.html +++ b/docs/guides/watch-mode/index.html @@ -15,15 +15,15 @@ - - - + + +

Watch Mode

Developers often find themselves in situations where they need to run a server in watch mode to streamline the development process. This guide will introduce you to entr, a versatile file-watcher tool, and how to run your server in watch mode with it. We'll also touch on the installation process and suggest some best practices to optimize your workflow.

+ Star

Watch Mode

Developers often find themselves in situations where they need to run a server in watch mode to streamline the development process. This guide will introduce you to entr, a versatile file-watcher tool, and how to run your server in watch mode with it. We'll also touch on the installation process and suggest some best practices to optimize your workflow.

Use case​

Running a server in watch mode offers a lot of key benefits: