Report server clusters

A cluster is a set of nodes (report servers) that share the same configuration, data sources, and a number of specific report server settings.

Cluster configuration is performed for the primary cluster, which then propagates its configuration and settings to all clusters within the farm. The primary node of a cluster is also responsible for collecting the analyzed data from all nodes within its cluster.

Note

We recommend that the primary node has the most resources as it will perform functions that the other nodes do not, such as processing of NAM Probe diagnostics data files and aggregating data for reporting. Nodes attached to a cluster are not required to contain the same hardware specifications. Also, hardware specifications are not taken in consideration during the load balancing process. For more information, see Report server load balancing.

Any report server recognized and supported as a NAM component can operate as a cluster node. Each type of report server attached to a cluster must have a primary node of its type within that cluster. For example, if there are NAM Server and ADS report servers within a cluster, there must be a primary NAM Server and a primary ADS in that cluster. The primary node for each node type is responsible for synchronizing the configuration between all other nodes of that type. For example, the NAM Server primary node in a cluster delivers any configuration updates to all other NAM Server nodes within that cluster.

Each cluster analyzes data received from defined data sources and automatically balances the unique users between all nodes belonging to the cluster. Additional nodes within the cluster increase load balancing, which boosts analysis performance.

Adding a cluster to a farm makes it possible to:

  • Monitor and analyze observed traffic using a different set of data sources

  • Monitor different software services

  • Maintain separate alerts per cluster

  • Maintain different user protocol mappings for various data sources

  • Easily scale current deployment by creating a load balancing cluster and attaching additional nodes to the cluster.

Note

If the primary node you selected for the new cluster contains already defined client or server ranges, the new cluster and all secondary nodes within it will limit their monitoring in accordance with the accepted IP address ranges defined on the primary node. Monitoring limits defined by client or server ranges will propagate to all nodes within a given cluster. If you want the new cluster to monitor all available traffic, you must remove the ranges from the primary node.For more information, see Accepted client or server IP address ranges.

Figure 1. Cluster with NAM Server and ADS report servers

Mixed report server cluster
Mixed report server cluster

Cluster actions

Each farm contains one primary cluster and one or more secondary clusters reporting to the primary cluster. Click the action icon icon within a cluster to perform the following actions:

Farm cluster actions
Farm cluster actions

Add node

Enables you to select an additional node from a list of standalone report servers and add it to this cluster.

Open configuration

Enables you to define options that affect all nodes assigned to the edited cluster. For more information, see Cluster Configuration.

Delete cluster

Enables you to remove the cluster and all of its nodes from the farm. All nodes attached to a deleted cluster automatically become standalone report servers.

Note

Report servers removed from an active cluster retain the data and options that were set while operating within a farm.

The Report Server service packs do not need to be applied in any specific order within the cluster. As a general rule, the software service packs and patches should first be applied to the Primary Node and then all other Nodes. It is recommended to keep the same software version on all Nodes within the cluster. If all Nodes share the same database server, it is recommended to deploy the service packs successively as not to overload the database server.

Cluster configuration

Cluster configuration enables you to set options that pertain to the whole cluster. These settings are propagated to all nodes of the same type located within the edited cluster. The number of options available for editing and synchronization varies based on the cluster that is being edited. Primary clusters contain all available options and settings. Secondary clusters contain only the options that are available as a result of settings defined in the Synchronization options panel for that cluster .

Configuring a secondary cluster, you can instruct the cluster to acquire specific settings and configurations from the primary cluster of that farm. You can choose which settings should be acquired from the primary cluster in the Synchronization options section of the Cluster configuration. For example, settings for Sending Mail defined in the primary cluster configuration will automatically propagate to the secondary clusters as long as the secondary cluster configurations have the Acquire mail server configuration selected in the Synchronization options section of Cluster configuration. The secondary cluster configuration indicates already synchronized settings by marking the panels that are Synchronized. Settings that are synchronized or are set to be acquired from the primary cluster can be modified only via the primary cluster configuration.

The typical options for NAM Server report server located in the primary cluster are:

  • Data Sources
    Lists data sources for this particular cluster. Enables you to assign new sources, remove existing sources, and enable or disable data feed.

  • Synchronization options
    Enables you to select which settings to synchronize with the primary cluster.
    For more information, see Synchronization Options.

  • Server Configuration
    Enables you to define site options, user options, and user activity details on demand.
    For more information, see NAM Server configuration.

  • Sending Mail
    Enables you to specify the SMTP Server for Scheduled Report Mailing.

  • Report Mailing Management
    Lists reports scheduled for mailing.

  • User-Protocol Mapping
    Enables you to map user names or client IP addresses to special protocol IDs of synthetic agents.
    For more information, see User-protocol mapping.

  • Business Hours
    Enables you to define business hours and distinguish them from non-business hours.
    For more information, see Business hours.

  • Report Data Servers
    Enables you to associate a number of report servers to be used as data sources for the DMI.
    For more information, see Report data servers.

  • DMI Custom Time Range
    Enables you to define custom time ranges for the reports.

  • Locations
    Enables you to define and view the hierarchy of sites, areas, and regions for the monitored network.

  • Baselines and Trends
    Enables you to configure advanced settings for baselines and trends.

  • Tenants
    Enables you to define the NAM system (NAM Probes, RUM Console, and NAM Server and ADS report servers) to be used to monitor several separate networks (tenants).

  • Dynatrace SaaS/Managed data export
    Enables you to define the scope of the NAM monitoring data that is exported to Dynatrace SaaS/Managed.
    For more information, see Unifying NAM data with Dynatrace SaaS and Managed

Synchronization options

While all nodes within a cluster use an identical configuration that is periodically synchronized, clusters within a farm can be configured to monitor particular areas of your deployment. For example, one secondary cluster may be configured to analyze data from a specific data source, while another secondary cluster may be configured to monitor a specific software service, and yet another secondary cluster may be configured to monitor and trigger an alarm for a specific user or connection. In such deployments, synchronization of all settings between clusters may not be desired.

Note

Alerts are not synchronized between the clusters. You must create and enable alerts individually for each cluster.

Because the primary cluster within a farm is the source of the configuration and settings, the Synchronization Options are available only while managing a secondary cluster configuration. The following synchronization options can be defined:

Configure Data Access Permission

Selecting Data Access Permission enables you to choose a dimension to filter data displayed on the reports. You can control data access by assigning specific dimension values to individual users or user groups. When Data Access Permission is selected, users have access only to those DMI views and reports where the chosen dimension filter is available. If the edited cluster should filter the data for individual users and groups as the primary cluster, select this synchronization option.

Acquire traps configuration

Alert notification recipients can be configured individually per cluster. If this cluster processes alarms and distributes notifications in the same manner as the primary cluster, select this synchronization option.

Acquire alert definitions from the primary cluster

This option creates a centralized location on the primary node of the primary cluster for the alert definitions. Specific clusters monitoring particular software service or business unit can maintain their own alert definitions specific to the analyzed data. If the same software services or business units are known to the primary cluster and the edited cluster, select this synchronization option.

Acquire Dynatrace server list from the primary cluster

A number of Dynatrace servers can be used as data sources for a farm of report servers. Some clusters may be configured to use a specific Dynatrace server for analysis only within the edited cluster. If your Dynatrace servers contain data that should be analyzed by the primary cluster and the edited cluster, select this synchronization option.

Acquire script configuration from the primary cluster

Each cluster is able to run command line notification scripts (for example, batch files) with a set of parameters defined by a user. If the edited cluster uses the same scripts located in the same local path as the primary cluster, select this synchronization option.

Acquire server configuration from the primary cluster

This server configuration includes site options, user options such as tracking user IPs and user aggregation, and settings for user activity details and server statistics on demand.

Acquire baselines and trends configuration from the primary cluster

Clusters are capable of having different manual baselines or generating different set of trends and baselines per cluster. If the edited cluster uses the same baselines and trends as the primary cluster, select this synchronization option.

Acquire business hours definitions from the primary cluster

This option creates a centralized location on the primary node of the primary cluster for the business hours definitions. If the edited cluster monitors and reports data based on the same business hours model as the primary cluster, select this synchronization option.

Acquire error names from the primary cluster configuration

Individual clusters are capable of monitoring and analyzing specific applications. If your monitoring application error names or operation attributes do not vary depending on cluster-configured data sources, users, or transactions, select this synchronization option.

Acquire locations configuration

This option allows the configuration of locations to be obtained from the primary cluster. It is possible for an individual cluster to monitor and analyze specific site, region or area. If the edited cluster monitors the same sites, areas or regions as the primary cluster, mark this synchronization option.

Acquire mail server configuration

Each report server is capable of sending out e-mail messages, reports, and alerts. The report server uses an existing SMTP server, and the configuration for the mail server can differ from cluster to cluster. One cluster can use one SMTP server sending specific reports while another cluster can use another SMTP server to send out other reports. If the cluster you are editing should use the same SMTP configuration as the primary cluster, or if you have only one SMTP server available for the entire farm, select this synchronization option.

Tenant Configuration

By default, the NAM Server processes data from all tenants configured on the NAM Probes assigned to it, but you can configure it to process data from only a selection of the tenants configured on those NAM Probes. If the edited cluster should process the same selection of the tenants as defined for the primary cluster, select this synchronization option.

Acquire the Dynatrace SaaS/Managed configuration from the primary cluster

This options instructs the edited cluster to obtain a Dynatrace SaaS/Managed configuration from the primary cluster. As a result, the primary cluster and the edited cluster export the same data to data destinations (Export all, by analyzer group or by software service options). If you want the edited cluster to export the same data as the primary cluster, select this synchronization option.

Acquire the Dynatrace SaaS/Managed list from the primary cluster

This options instructs the edited cluster to obtain a list of Dynatrace SaaS/Managed data destinations from the primary cluster. As a result, the primary cluster and the edited cluster export data to the same data destinations. If you want the edited cluster to export data to the same data destinations as the primary cluster, select this synchronization option.

Acquire the data source and destination list from the primary cluster

This option instructs the edited cluster to obtain a list of data sources and destinations (excluding Dynatrace SaaS/Managed) from the primary cluster. As a result, the Primary cluster and the edited cluster will receive data from the same data sources and send it to the same destinations. If the edited cluster must process and direct data the same way as the primary cluster, mark this synchronization option and check if you also need to synchronize the Dynatrace SaaS/Managed list.

Acquire user properties from the primary cluster

This option synchronizes properties for regular users and special system users with the primary cluster. For example, if all of your users should have the same password expiration time, or the same session timeout length, select this synchronization option.

Acquire user protocol mapping from the primary cluster

This option creates a centralized location on the primary node of the primary cluster for the user protocol mapping. This property specifies a mapping of a user name or a client IP to special protocol IDs of synthetic agents. The mapping helps to classify the synthetic traffic correctly in the instances where the automatic recognition cannot be performed. If the edited cluster monitors data where the same user protocol mapping can be applied as in the primary cluster, select this synchronization option.

Acquire list of reporting groups, transactions and applications from the primary cluster

Typically a single cluster can be configured to monitor specific applications or transactions based on attached data sources for that particular server. If your application or transaction monitoring needs span data sources from multiple clusters, or you have business units that are defined for the entire farm, select this synchronization option.

Acquire report definitions from the primary cluster (NAM Server and ADS)

During synchronization, the report definitions created and residing on the primary node of the primary cluster are copied to the primary node of the cluster being edited. If you need report definitions available in this cluster, and such definitions already exist on the primary cluster, select this synchronization option.

Acquire storage period configuration from the primary cluster configuration

This option creates a centralized location on the primary node of the primary cluster for the storage period settings.

Cluster database capability may vary from cluster to cluster. Some clusters operating with limited database size may require a shorter storage period for a quicker data rotation. If you are certain that this cluster is able to retain the same amount of data in the database as the primary cluster, select this synchronization option.

Acquire ToS from the primary cluster

Each cluster can independently analyze and report on traffic based on a traffic identifier contained in an 8-bit field in the IP packet header. The use of this field is software service specific; it is used by software services to denote special types of traffic. If the edited cluster monitors and reports within software services the same type of service as the primary cluster, select this synchronization option.

Acquire username mappings from the primary cluster

This option creates a centralized location on the primary node of the primary cluster for the username mapping. If the edited cluster monitors data where the same users can be recognized as in the data monitored in the primary cluster, select this synchronization option.