Skip to main content
This documentation outlines how to configure logging with the AppSignal for Go integration.

Configure Logging

🔐 Do not send Personal Identifiable Information (PII) to AppSignal. Filter PII (e.g., names, emails) from logs and use an ID, hash, or pseudonymized identifier instead.

For HIPAA-covered entities, more information about signing a Business Associate Agreement (BAA) can be found in our Business Add-Ons documentation.
You do not need to create a log source to send logs from the AppSignal for Go integration. An “application” log source will be created automatically. The Go integration uses OpenTelemetry’s logging capabilities to send logs to AppSignal.

Stand-alone usage

To use logging with OpenTelemetry in Go, you need to set up the logger using OpenTelemetry’s logger provider.

Usage with slog

You can configure the standard slog package to send structured logs to AppSignal using the OpenTelemetry handler.

Usage

Sending Logs

Using the OpenTelemetry logger directly, you can define the severity level of your logs:
You can define custom attributes to send log information that can be used when filtering and querying logs:
You can query and filter on message contents and attribute values from within the Log Management tool. Once configured, the desired attributes will be sent to AppSignal as log tags, and be queryable in the AppSignal logging interface.

Filtering Logs

You can use the ignore_logs configuration option to ignore log lines. See our Ignore Logs guide to learn more.

Need Help?

After configuring your Go application to send logs, logs should appear in AppSignal. If you are unsure about this step or AppSignal is not receiving any logs, you can always reach out for assistance. We’ll help get you back on track!