---
title: Remap Custom Severity Values to the Official Log Status
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: >-
  Docs > Log Management > Logs Guides > Remap Custom Severity Values to the
  Official Log Status
---

# Remap Custom Severity Values to the Official Log Status

By default, the [Log Status Remapper](https://docs.datadoghq.com/logs/log_configuration/processors/#log-status-remapper) relies on the [Syslog severity standards](https://en.wikipedia.org/wiki/Syslog#Severity_level). However there might be other systems having different severity values that you might want to remap on the official log status. This is possible thanks to the [Category Processor](https://docs.datadoghq.com/logs/log_configuration/processors/#category-processor) that defines a mapping between your custom values and the expected ones.

This page describes how to do this with 2 examples: Bunyan levels and web access logs.

## Web access logs{% #web-access-logs %}

The status code of the request can be used to determine the log status. Datadog integrations use the following mapping:

- 2xx: OK
- 3xx: Notice
- 4xx: Warning
- 5xx: Error

Assume the status code of your log is stored in the `http.status_code` attribute. Add a Category Processor in your Pipeline that creates a new attribute to reflect the above mapping:

{% image
   source="https://datadog-docs.imgix.net/images/logs/guide/category_processor.ef6baf86465a4a08d5f017b460492a97.png?auto=format"
   alt="Category Processor " /%}

Then add a status remapper that uses the newly created attribute:

{% image
   source="https://datadog-docs.imgix.net/images/logs/guide/log_status_remapper.1269f6ff6677c2ada87be725a985147f.png?auto=format"
   alt="log status remapper" /%}

## Bunyan levels{% #bunyan-levels %}

Bunyan levels are similar to those of Syslog, but their values are multiplied by 10.

- 10 = TRACE
- 20 = DEBUG
- 30 = INFO
- 40 = WARN
- 50 = ERROR
- 60 = FATAL

Assume the bunyan level is stored in the `bunyan_level` attribute. Add a Category Processor in your Pipeline that creates a new attribute to reflect the above mapping:

{% image
   source="https://datadog-docs.imgix.net/images/logs/guide/category_processor_bunyan.8d895519dc827ad9ed541575148f9dcf.png?auto=format"
   alt="category Processor bunyan" /%}

Then add a status remapper that uses the newly created attribute:

{% image
   source="https://datadog-docs.imgix.net/images/logs/guide/status_remapper_bunyan.9c854759cc42dff5d0e63a4fd4be2abb.png?auto=format"
   alt="log status remapper bunyan" /%}

## Further Reading{% #further-reading %}

- [Learn more about Log collection with the Agent](https://docs.datadoghq.com/logs/log_collection/#custom-log-collection)
- [Learn how to process your logs](https://docs.datadoghq.com/logs/log_configuration/processors)
- [Learn more about parsing](https://docs.datadoghq.com/logs/log_configuration/parsing)