The Real User Analyzer pulls data from Real User Collector components.
You can manage the connections between Analyzer and Collectors on the Administration > Data flow settings > Analyzer & Collectors management page of the Real User Analyzer by using the following options:
The Status tab
Configure the Maximum Wait Time on the Analyzer settings tab.
A configurable delay period called Maximum Wait Time defines out of sync. For example, if you set the Maximum Wait Time to 15 minutes, a Collector feed that is more than 15 minutes behind other Collectors is considered out of sync. Additionally, Real User Analyzer stops pulling data from all Real User Collectors for a maximum of 15 minutes before dropping the delinquent feed and starting to pull data again through other feeds.
The Maximum Wait Time is also used to determine how much historical data is pulled from Real User Collectors after a period of Real User Analyzer unavailability has ended. Real User Collector components can retain up to 2 hours of historical data.
Warning
If the connection between the Real User Analyzer and one of its Real User Collectors is temporarily broken, or if one of the Collector feeds seems to be out of sync with other Collector feeds, the Real User Analyzer stops pulling data from all Collectors until the connection is restored, the synchronization issue is resolved, or a configurable delay period has expired.
Note
The system automatically disconnects the Collector feeds that have been inactive for seven days. To remove an inactive component from the components list, use the Disconnect command on the Status page for a specified data-receiving component.
On the Real User Analyzer, open the Administration > Data flow settings > Analyzer & Collectors management page.
In the Name and Description boxes, type a meaningful name and description to identify the Real User Collector that you want to feed data from.
The name and description identify the component throughout the system.
In the IP/DNS namebox, type the name or IP address (IPv4 only) of the Real User Collector.
To permit this Real User Analyzer to handle system alerts generated by this Real User Collector, select the Accept Alerts from Collector box.
To set the priority of this Real User Collector, in the Priority section, click High or Low. The Real User Analyzer does not reject data (via sampling) from high-priority feeds.
To feed all traffic that this component collects to the Real User Analyzer, select Capture all traffic from the Collector.
To feed only a specific subset of traffic that this component collects to the Real User Analyzer, add a filter expression to identify the traffic that you want to capture.
To compose an expression using the Expression Builder, click Build a filter expression.
The new Real User Collector feed appears in the list of Collector feeds. An icon in the Connection column shows the status of the connection to the Real User Collector:
To turn the feed on immediately, click ON in the row for the Real User Collector.
Note
You can either add different Real User Collector feeds or set up multiple feeds from a single Collector by using filters to differentiate the data that is pulled through each.
Warning
If you change the settings for an existing Real User Collector feed, the system purges all data from the associated Real User Analyzer.
4 Comments
Craig Jackson
It would be useful to describe the data on the Status tab. In particular, what do the "Status" and "Discarded Traffic" fields mean? How should apparent problems be troubleshooted?
Yuriy Koziy
Hi Craig,
I added descriptions for the fields you can see on the Status tab. Let me know if this is what you were looking for.
As for the troubleshooting, I suggest contacting your BMC Support representative.
Regards,
Yuriy
Craig Jackson
Yuriy,
I have more questions about the Status screen. When one hovers over a block in the "Traffic Capture Rate" graph, one gets a ToolTip that indicates how many "hits per second" were seen in the relevant period. Could you document what "hits" means? My initial guess was that it was "HTTP Transactions", but looking further I'm guessing it means "IP packets".
Yuriy Koziy
Hi Craig,
Your initial assumption is correct — "hits" are HTTP transactions (HTTP request and response). I think we need to restore our Glossary topic and document it there.