# Issue with Key=Value Parser Pipeline for specific log-messages

**URL:** <https://community.graylog.org/t/issue-with-key-value-parser-pipeline-for-specific-log-messages/19606>\
**Category:** Graylog Central (peer support)\
**Tags:** pipeline-rules, debuggingpl\
**Created:** [April 26, 2021, 10:30am UTC](https://community.graylog.org/t/issue-with-key-value-parser-pipeline-for-specific-log-messages/19606 "2021-04-26T10:30:42Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![shoothub](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/shoothub/32/6412_2.png) [@shoothub](https://community.graylog.org/u/shoothub)\
**Post date:** [April 26, 2021, 2:27pm UTC](https://community.graylog.org/t/issue-with-key-value-parser-pipeline-for-specific-log-messages/19606/2 "2021-04-26T14:27:55Z")

</div>

Try to use this, I’ve added parameters to remove "{} from key and values. But, it’s not perfect, because of Country contains json.

```auto
rule "key_value_parser"
when
    has_field("Full_Response")
then
    set_fields(
        fields:
            key_value(
                value: to_string($message.Full_Response),
                delimiters:",",
                kv_delimiters:":",
                trim_key_chars:"\"",
                trim_value_chars: "\"{}")
            );
end

```

---

_[View the full topic](https://community.graylog.org/t/issue-with-key-value-parser-pipeline-for-specific-log-messages/19606)._