# Logging (StdErr)

All logs that you wish to display to your users should be written to `stderr.`

These logs can be viewed via the In-App Marketplace by users, or from within the Integration Hub on various pages, including the integration level, tenant level, and main run resource.

Below are various examples of how to do this is in multiple languages.

{% tabs %}
{% tab title="C#" %}

```
using System;

Console.Error.WriteLine("Hello World")
```

{% endtab %}

{% tab title="Java" %}

```java
System.err.println("Hello World!");
```

{% endtab %}

{% tab title="NodeJS" %}

```
console.error('Hello World')
```

{% endtab %}

{% tab title="PHP" %}

```php
fwrite(STDERR, 'Hello World' . PHP_EOL);
```

{% endtab %}

{% tab title="Python" %}

```python
import sys

print("Hello World!", file=sys.stderr)
```

{% endtab %}

{% tab title="Ruby" %}

```ruby
require "logger"

log = Logger.new(STDERR)

log.debug('Hello Word!')
```

{% endtab %}
{% endtabs %}


---

# 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.pandium.com/getting-started/anatomy-of-an-integration/environment-variables/stderr.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.