---
title: Configure mobile network request settings
source: https://docs.newrelic.com/docs/mobile-monitoring/new-relic-mobile/maintenance/configure-network-request-settings
---

The mobile network request settings page can help you customize how network metrics and events are reported. You can [block or allow hostnames](#blockallow-hostnames), [ignore HTTP status codes from certain hosts](#ignore-status-codes), and [create aliases to rename hosts or group subdomains](#group-into-alias).

To configure these settings, go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Mobile > (select a mobile app) > Settings > Network settings**.

## Block/allow hostnames [#blockallow-hostnames]

You can allow or block certain hostnames from being monitored. For example, if you want to only allow subdomains of `ecommerce.com`:

1.  On the **Network settings page**, select the **Show only hostnames** tab.
2.  Click **Add a hostname**.
3.  Enter the hostname `*.ecommerce.com` and click **Add to list**.

![Allow a hostname](https://docs.newrelic.com/images/mobile_screenshot-full_show-hostname.webp "Allow a hostname")

Wait up until 2 hours for the rule to be applied.

## Ignore HTTP status codes [#ignore-status-codes]

You can ignore specific HTTP error status code on a hostname. For example, if you want to ignore `401`, `403`, and `404` errors from all `ecommerce.com` subdomains:

1.  On the **Network settings page**, select the **Status codes** tab.
2.  Click **Create a status code rule**.
3.  Enter the host `*.ecommerce.com`.
4.  Enter status codes `401`, `403`, and `404`  and click **Add to list**.

![Create a status code rule in the UI](https://docs.newrelic.com/images/mobile_screenshot-full_new-status-rule.webp "Create a status code rule")

Wait up until 2 hours for the rule to be applied.

## Create aliases for hostnames [#group-into-alias]

You can create aliases to rename or group hostnames that make the most sense to you. For example, if you want to create an alias that groups all subdomains of `ecommerce.com`:

1.  On the **Network settings** page, select the **Aliases and groups** tab.
2.  Click **Create an alias**.
3.  Enter `*.ecommerce.com` to group all subdomains of `ecommerce.com`.
4.  Enter the alias `ecommerce.com` and click **Save alias**.

![create an alias](https://docs.newrelic.com/images/mobile_screenshot-full_create-alias.webp "Create an alias")

Wait up until 2 hours for the rule to be applied.

### Recommendations for using wildcards [#about-wildcards]

When using `*` (a wildcard), the regex rules are slightly different. The wildcard is used for a whole segment, or the values between two dots in a hostname (i.e., the whole segment for `hostname.1219.com` is `1219`).

Here are some examples of successfully using wildcards to create an alias:

| Hosts                 | Alias                | Example domain              | Result               |
| --------------------- | -------------------- | --------------------------- | -------------------- |
| `192.168.*.100`       | LOCAL                | `192.168.10.100`            | LOCAL                |
| `tbr.*.something.com` | tbr.\*.something.com | `tbr.gh99898.something.com` | tbr.\*.something.com |
| `api1.mydomain.co.uk` | API                  | `api1.mydomain.co.uk`       | API                  |
| `api2.mydomain.co.uk` | API                  | `api2.mydomain.co.uk`       | API                  |

Now that you've seen some example of how this works, let's look at some examples of _what won't work_.

| Hosts                   | Alias                  | Example domain              | Result                    |
| ----------------------- | ---------------------- | --------------------------- | ------------------------- |
| `tbr.gh*.something.com` | tbr.gh\*.something.com | `tbr.gh99898.something.com` | tbr.gh99898.something.com |
| `cs-*.company.jp`       | cs-\*.company.jp       | `cs-23.company.jp`          | cs-23.company.jp          |
| `cs-*.company.jp`       | customer_survey        | `cs-*.company.jp`           | customer_survey           |

Remember, a wildcard will only affect a whole segment. Since the `*` can only be used for a full segment, the `*` here will be taken literally and not as a wildcard.