Changes in 2017 May releases

DC RUM 2017

New AMD architecture

Since the 2017 release, the AMD is available only in the new architecture we referred to as AMD.
  • There's no direct upgrade from a Classic AMD. However, you can migrate your Classic AMD configuration.
See Upgrading Classic AMD.
  • AMD 2017 release supports Red Hat Enterprise Linux 7.3 only.
See Updating Linux.
In the context of the 2017 release, whenever we mention AMD, we mean new architecture AMD.

AMD network configuration using a tool of your choice

When setting up your AMD, the rtminst program will accept the network configuration performed with any system tool. We no longer handle the network configuration in rtminst.
See Configuring AMD communication interface where we show you how to use nmtui to configure the network.

AMD installation options

Upgrade.bin , the AMD installation program has now two installation modes, automatic and manual. There's no default option. You must choose one using --automatic or --manual parameters.
When you test your system compatibility using upgrade.bin with the --test-system parameter, we now also indicate if the firewalld service is enabled on Red Hat 7. AMD expects it to be disabled.
See Installation and upgrade options.

User access and security handled by RUM Console

We drop CSS. Now, you will manage your users and security using RUM Console.
The RUM Console installation program will import all your users and settings from a current CSS installation.
See Upgrading the RUM Console. We introduce a concept of API tokens for authorizing the safe communication between the DC RUM concepts.
See API tokens.
Once the upgrade process is complete and your DC RUM is up and running, you can uninstall the CSS and delete the database.

Browser support

We're adding support for Edge and dropping support for Internet Explorer 10.
See Supported browsers.

Bulk insert properties

The bulk insert source and destinations were controlled by the advanced properties and RtmJob.bulk.write and corresponding user properties and bulk.write . Since the 2017 release, we rely only on the user properties. If your current configuration used the advanced properties, we will convert and RtmJob.bulk.write to and bulk.write during the upgrade to 2017 and delete them.

Data access permission

The Transaction,Tier, and Reporting group dimensions are considered as deprecated for data access permission. You can still use these dimensions to control data accesses in DC RUM 2017, however won't be able to do so in future releases. Consider changing your configuration now.
See Data access permission.

Server think time

The Server think time metric is considered as deprecated. It's available in the current version DMI, but you can expect it to disappear in the future releases. Modify your reports to use the Server time metric instead. Server time provides more refined measurements and deals better with complex operations.
See Calculating primary reason for slow operations to learn how we calculate server time.

Reorder of request breakdowns

To make it consistent with other breakdowns, we changed the order of components for a number of request breakdowns. Now the order is Failures/Failed, Aborts [if exists], Slow, Fast. The affected metrics are:
  • In Application, transaction, and tier data view: Requests breakdown, Requests percentage breakdown (with tooltip), Requests breakdown (with tooltip)
  • In Application, transaction, and tier data view: Requests breakdown, Requests percentage breakdown (with tooltip), Requests breakdown (with tooltip)
  • In Synthetic and sequence transaction data view: Transaction requests breakdown
  • In Synthetic Monitoring page data view: Pages executed breakdown
  • In RUM Browser data view: User actions attempts breakdown, User actions breakdown

Dimension name changes in RUM browser data view

To make it consistent across all data views, we changed Browser name to Client type . This dimension stores the browser names used to collect the UEM monitoring data. Consequently, we changed the name of the old Client type to Client platform . This dimension has four possible values: Desktop, Mobile, Synthetic, and Unknown.

SAP GUI operation name change

SAP GUI Operation name now contains the Screen Id. You can expect the change both, in fresh installations and after you upgrade your AMD to the 2107 release.

ACK RTT measurement improvements

We improved the algorithm used to calculate ACK RTT. Expect slight changes in the ACK RTT metrics values.

SSL connection setup time

We no longer treat SSL Connection Setup Time as a part of SSL Handshake . We noticed that a particularly long setup time could confuse the analyst, as it would unnecessarily affect the SSL Handshake and overall Operation time measurements. Consequently, the SSL Connection Setup Time metric is no longer available and we report it as a separate operation.