There have been a couple of changes to host mapping in the Chrome 56 update.
Host-to-host and host-to-IP mapping function is now restricted to a one-to-one mapping
This release introduces changes to host-to-host and host-to-IP mapping that may impact existing scripts. In earlier versions of the Dynatrace engines, we supported a one-to-many mapping for host mapping, allowing you to define up to 3 alternative hosts to map to (if one host fails, tool will automatically try the next). This function is now restricted to a one-to-one mapping. More information here: Chrome 56 - Deprecated Functions and Known Issues/Changes.
Scripts need to be updated so the first host-to-host or host-to-IP mapping is the correct one.
Host-to-host and host-to-IP mapping function now uses a redirect mechanism
For Chrome 46 and earlier versions, host-to-IP mapping was done inside Chromium and was not visible to users. In later versions (including Chrome 56), we are using a redirect mechanism to send traffic to the IP you have mapped your host to.
This has two effects for customers:
- The hostname that is set in the host mapping will show a 307 redirect with 0 bytes in the waterfall. The next object will be the Destination in the host mapping.
- Filters 'excluding all URLs not matching the above filters' need to be updated to include host mappings. This is often used when users would like to only see objects from the root object. In previous versions, only the host needed to be added to a filter set to 'exclude all URLs not matching the above filters'. Beginning with Chrome 56, you will need to add both the host and the IP address or destination host to your filters.