# Data for browser, location is not populating

**URL:** <https://discuss.elastic.co/t/data-for-browser-location-is-not-populating/344751>\
**Category:** User Experience\
**Created:** [October 10, 2023, 3:10pm UTC](https://discuss.elastic.co/t/data-for-browser-location-is-not-populating/344751 "2023-10-10T15:10:41Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![sameer7](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sameer7/32/126426_2.png) [@sameer7](https://discuss.elastic.co/u/sameer7)\
**Post date:** [October 10, 2023, 3:10pm UTC](https://discuss.elastic.co/t/data-for-browser-location-is-not-populating/344751/1 "2023-10-10T15:10:41Z")

</div>

Hi, we've an integration with apm rum js agent and are tracking metrics with User Experience dashboard. But it seems the data for browser, location, is not getting populated. Not sure what we're missing here.

 ![Screenshot 2023-10-10 at 8.37.49 PM](https://us1.discourse-cdn.com/elastic/original/3X/5/1/51fb1844b2b214bd26592246228fc5e7f576afa9.png)

We do see other metrics such as page load times, errors but these details don't seem to populate. In the server yaml file we have used the default flag for `capture_personal_data`.

---

<div class="post-metadata">

**Author:** ![emilioalvap](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/emilioalvap/32/99310_2.png) [@emilioalvap](https://discuss.elastic.co/u/emilioalvap)\
**Post date:** [October 11, 2023, 3:55pm UTC](https://discuss.elastic.co/t/data-for-browser-location-is-not-populating/344751/2 "2023-10-11T15:55:48Z")

</div>

Hi @sameer7,

Can you please start by checking whether the data is available on your APM data by running the next query?

```auto
GET traces-apm*,apm-*,logs-apm*,apm-*,metrics-apm*,apm-*/_search
{
  "query": {
    "bool": {
      "filter": []
    }
  },
  "size": 0,
  "aggs": {
    "values": {
      "terms": {
        "field": "client.geo.country_iso_code",
        "size": 10
      }
    }
  }
}

```

You should see some results come back.

---

<div class="post-metadata">

**Author:** ![sameer7](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sameer7/32/126426_2.png) [@sameer7](https://discuss.elastic.co/u/sameer7)\
**Post date:** [October 11, 2023, 5:00pm UTC](https://discuss.elastic.co/t/data-for-browser-location-is-not-populating/344751/3 "2023-10-11T17:00:24Z")

</div>

Hi @emilioalvap, I don't get any data from this, this is the response

```auto
{
  "took" : 82,
  "timed_out" : false,
  "_shards" : {
    "total" : 125,
    "successful" : 125,
    "skipped" : 0,
    "failed" : 0
  },
  "hits" : {
    "total" : {
      "value" : 10000,
      "relation" : "gte"
    },
    "max_score" : null,
    "hits" : []
  },
  "aggregations" : {
    "values" : {
      "doc_count_error_upper_bound" : 0,
      "sum_other_doc_count" : 0,
      "buckets" : []
    }
  }
}

```

how should we proceed here?

---

<div class="post-metadata">

**Author:** ![sameer7](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sameer7/32/126426_2.png) [@sameer7](https://discuss.elastic.co/u/sameer7)\
**Post date:** [October 12, 2023, 1:25pm UTC](https://discuss.elastic.co/t/data-for-browser-location-is-not-populating/344751/4 "2023-10-12T13:25:14Z")

</div>

@emilioalvap can you please help here? Is it due to the ingest pipelines not working?

---

<div class="post-metadata">

**Author:** ![emilioalvap](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/emilioalvap/32/99310_2.png) [@emilioalvap](https://discuss.elastic.co/u/emilioalvap)\
**Post date:** [October 13, 2023, 2:25pm UTC](https://discuss.elastic.co/t/data-for-browser-location-is-not-populating/344751/5 "2023-10-13T14:25:41Z")

</div>

Hi @sameer7,

I would start by making sure the required data is where it needs to be. Can you check if the field `client.ip` is set for documents that are being ingested in `apm-*` indices? It should look something like this:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/1/2/129fd629ae26b9f495e48f88d58222d7ff6bd28e.jpeg)

If `client.ip` is set, I'd recommend checking the setup for APM ingest pipeline, making sure that `traces-apm.rum-<version>` contains the following processor and that no custom pipeline is overriding it:

```auto
{
    "geoip": {
      "database_file": "GeoLite2-City.mmdb",
      "field": "client.ip",
      "ignore_missing": true,
      "on_failure": [
        {
          "remove": {
            "field": "client.ip",
            "ignore_failure": true,
            "ignore_missing": true
          }
        }
      ],
      "target_field": "client.geo"
    }
  },

```

You can also check geoip database stats by running the following query on Kibana Dev Tools. These stats should not contain any errors:

```auto
GET _ingest/geoip/stats

```

---

<div class="post-metadata">

**Author:** ![sameer7](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sameer7/32/126426_2.png) [@sameer7](https://discuss.elastic.co/u/sameer7)\
**Post date:** [October 13, 2023, 2:47pm UTC](https://discuss.elastic.co/t/data-for-browser-location-is-not-populating/344751/6 "2023-10-13T14:47:41Z")

</div>

Hi @emilioalvap i can see `client.ip` is set. And this is the config in `ingestion.json`

```auto
{
    "id": "apm_user_geo",
    "body": {
      "description": "Add user geo information for APM events",
      "processors": [
        {
          "geoip": {
            "database_file": "GeoLite2-City.mmdb",
            "field": "client.ip",
            "target_field": "client.geo",
            "ignore_missing": true,
            "on_failure": [
              {
                "remove": {
                  "field": "client.ip",
                  "ignore_missing": true,
                  "ignore_failure": true
                }
              }
            ]
          }
        }
      ]
    }
  },

```

Also we're not directly ingesting data in elasticsearch, we first do it in kibana and then in elasticsearch is this the reason the default pipeline are not working?

`output.elasticsearch` is set to false to facilitate the same.

I see that it's mentioned here to enable it: [Parse data using ingest node pipelines | APM Server Reference [7.13] | Elastic](https://www.elastic.co/guide/en/apm/server/7.13/configuring-ingest-node.html#register-pipelines-apm-server)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 10, 2023, 2:48pm UTC](https://discuss.elastic.co/t/data-for-browser-location-is-not-populating/344751/7 "2023-11-10T14:48:18Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
