Log Formatting

Log Formatting

Your log data must not contain any personal data, such as names, email addresses, etc. It is your responsibility to ensure this data is filtered out before being sent to AppSignal, and when identifying a person is necessary that your application uses alternative forms of identification such as a user ID, hash, or pseudonym.

How you can format your logs will vary depending on which configuration you are using with Logging. The table below outlines the currently available configurations and the log formats which they support

PlatformJSONLogfmtNDJSONPlaintextSyslog (RFC 5424)
AWS Kinesis / CloudWatch
Clever Cloud
Gigalixir Log Drain
Heroku Log Drain

When using Logfmt, JSON and NDJSON as your log format, you can add searchable attributes to your logs. Attributes can be any of the following types:

  • string
  • integer (e.g. 10)
  • double (e.g. 10.01)
  • boolean (true/false)

Supported Log Formats


When specifying Plaintext as your log format, the log line will be used as the message as-is, and AppSignal will not parse attributes from the log line. If you want to have searchable attributes in your application's logs, we recommend formatting your logs in Logfmt, JSON and NDJSON.

Need more help?

Contact us and speak directly with the engineers working on AppSignal. They will help you get set up, tweak your code and make sure you get the most out of using AppSignal.

Contact us

Start a trial - 30 days free

AppSignal is a great way to monitor your Ruby, Elixir & Node.js applications. Works great with Rails, Phoenix, Express and other frameworks, with support for background jobs too. Let's improve your apps together.

Start a trial