HTTP header extractor enrichment

For engineers Enrichment
1

Hi, as per this document HTTP header extractor enrichment | Snowplow Documentation

I have added the “http_header_extractor_config.json” as it is and with the events I’m not seeing the “headers” data in the “derived context”. Could anyone please tell me what I might be missing?

2

Hi @cheluvesha ,

Derived contexts are added only in case the regex defined in regexPattern matches some header.

Could you share your http_header_extractor_config.json please ?

3

Hi @BenB here is the content of that json file

{
  "schema": "iglu:com.snowplowanalytics.snowplow.enrichments/http_header_extractor_config/jsonschema/1-0-0",

  "data": {

    "vendor": "com.snowplowanalytics.snowplow.enrichments",
    "name": "http_header_extractor_config",
    "enabled": true,
    "parameters": {
      "headersPattern": ".*"
    }
  }
}

Now I’m able to see the data in the Derived_contexts but I have one question to ask.
I’m expecting these below fields with the data but unfortunately I’m not seeing these fields.
USERNAME
CUSTOMER_GROUP_ID
SUBSCRIPTION_GROUP_ID
CUSTOMER_NAME
USERAUTHTYPE

Any idea how to get these above fields with http_headers enrichment and Thanks.

4

Hi @cheluvesha ,

HTTP requests typically contain headers like Accept-Encoding , Content-Type, Host, User-Agent etc.

Are you also specifically adding the fields that you mention to the headers of the HTTP requests made to the collector ?

5

The issue is resolve and Thank you @BenB

1 Like