The BMC Real End User Experience Monitoring Cloud Probe component connects to a running Real User Collector. The following system requirements are necessary to install and use the Cloud Probe:
The Cloud Probe supports the following operating systems:
Each server where the Cloud Probe is installed requires the following minimum hardware:
Note
In the table below, see the approximate percentage of CPU and RAM capacity used by the Cloud Probe on the tenant computer (tested with 2 virtual CPUs and 4Gb RAM on Linux, and with 4 virtual CPUs and 16Gb RAM on Windows).
Cloud Probe CPU and RAM usage
Operating system | Expected volume of traffic | CPU consumption | RAM consumption |
---|---|---|---|
Red Hat Enterprise Linux 6.3 | ~1000 hits/sec | ~5% | ~10% |
Microsoft Windows 2008 Server (R2) | ~800 hits/sec | ~5% | ~10% |
The Cloud Probe must connect to an instance of the Real User Collector using HTTPS. You can
change the default port
(443), if necessary.
For a list of the supported cipher suites, see 749852611.
Warning
The data handled by application monitoring components, including all server components and agents, is time sensitive. If the time between components is not synchronized, you might see incorrect or partial data, or you might not see any data.
Consult your operating system documentation to synchronize each component's internal clock with an NTP server on your network or on the Internet. Ensure that the clocks are regularly synchronized.
This applies to all Real End User Experience Monitoring Software Edition components and integrated App Visibility Monitoring components.
For Linux operating systems, you must have the following libraries installed:
Note
Exact names of the libraries may vary depending on your operating system and version.
If you do not have these libraries installed, the installation will not run properly.
Before installing the Cloud Probe on a Windows operating system, you must download and install the
WinPcap
tool installed on the Cloud Probe machine.
If the Cloud Probe component monitors HTTPS traffic on the network, it supports the following SSL and TLS protocols versions:
The following table lists the ciphers suites supported by the Cloud Probe:
Supported SSL/TLS cipher suites
Cipher suite name | Cipher suite ID | Cipher | MAC |
---|---|---|---|
TLS_RSA_WITH_NULL_MD5 | 0x000001 | NULL | MD5 |
TLS_RSA_WITH_NULL_SHA | 0x000002 | NULL | SHA |
TLS_RSA_EXPORT_WITH_RC4_40_MD5 | 0x000003 | RC4_40 | MD5 |
TLS_RSA_WITH_RC4_128_MD5 | 0x000004 | RC4_128 | MD5 |
TLS_RSA_WITH_RC4_128_SHA | 0x000005 | RC4_128 | SHA |
TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 | 0x000006 | RC2_CBC_40 | MD5 |
TLS_RSA_WITH_IDEA_CBC_SHA | 0x000007 | IDEA_CBC | SHA |
TLS_RSA_EXPORT_WITH_DES40_CBC_SHA | 0x000008 | DES40_CBC | SHA |
TLS_RSA_WITH_DES_CBC_SHA | 0x000009 | DES_CBC | SHA |
TLS_RSA_WITH_3DES_EDE_CBC_SHA | 0x00000A | 3DES_EDE_CBC | SHA |
TLS_RSA_WITH_AES_128_CBC_SHA | 0x00002F | AES_128_CBC | SHA |
TLS_RSA_WITH_AES_256_CBC_SHA | 0x000035 | AES_256_CBC | SHA |
TLS_RSA_WITH_NULL_SHA256 | 0x00003B | NULL | SHA256 |
TLS_RSA_WITH_AES_128_CBC_SHA256 | 0x00003C | AES_128_CBC | SHA256 |
TLS_RSA_WITH_AES_256_CBC_SHA256 | 0x00003D | AES_256_CBC | SHA256 |
TLS_RSA_WITH_CAMELLIA_128_CBC_SHA | 0x000041 | CAMELLIA_128_CBC | SHA |
TLS_RSA_EXPORT1024_WITH_RC4_56_MD5 | 0x000060 | RC4_56 | MD5 |
TLS_RSA_EXPORT1024_WITH_RC2_CBC_56_MD5 | 0x000061 | RC2_CBC_56 | MD5 |
TLS_RSA_EXPORT1024_WITH_DES_CBC_SHA | 0x000062 | DES_CBC | SHA |
TLS_RSA_EXPORT1024_WITH_RC4_56_SHA | 0x000064 | RC4_56 | SHA |
TLS_RSA_WITH_CAMELLIA_256_CBC_SHA | 0x000084 | CAMELLIA_256_CBC | SHA |
TLS_RSA_PSK_WITH_RC4_128_SHA | 0x000092 | RC4_128 | SHA |
TLS_RSA_PSK_WITH_3DES_EDE_CBC_SHA | 0x000093 | 3DES_EDE_CBC | SHA |
TLS_RSA_PSK_WITH_AES_128_CBC_SHA | 0x000094 | AES_128_CBC | SHA |
TLS_RSA_PSK_WITH_AES_256_CBC_SHA | 0x000095 | AES_256_CBC | SHA |
TLS_RSA_WITH_SEED_CBC_SHA | 0x000096 | SEED_CBC | SHA |
TLS_RSA_WITH_AES_128_GCM_SHA256 | 0x00009C | AES_128_GCM | SHA256 |
TLS_RSA_WITH_AES_256_GCM_SHA384 | 0x00009D | AES_256_GCM | SHA384 |
TLS_RSA_PSK_WITH_AES_128_CBC_SHA256 | 0x0000B6 | AES_128_CBC | SHA256 |
TLS_RSA_PSK_WITH_AES_256_CBC_SHA384 | 0x0000B7 | AES_256_CBC | SHA384 |
TLS_RSA_PSK_WITH_NULL_SHA256 | 0x0000B8 | NULL | SHA256 |
TLS_RSA_PSK_WITH_NULL_SHA384 | 0x0000B9 | NULL | SHA384 |
SSL2_RC4_128_WITH_MD5 | 0x010080 | RC4_128 | MD5 |
SSL2_RC4_128_EXPORT40_WITH_MD5 | 0x020080 | RC4_128_EXPORT40 | MD5 |
SSL2_RC2_CBC_128_CBC_WITH_MD5 | 0x030080 | RC2_CBC_128_CBC | MD5 |
SSL2_RC2_CBC_128_CBC_WITH_MD5 | 0x040080 | RC2_CBC_128_CBC | MD5 |
SSL2_IDEA_128_CBC_WITH_MD5 | 0x050080 | IDEA_128_CBC | MD5 |
SSL2_DES_64_CBC_WITH_MD5 | 0x060040 | DES_64_CBC | MD5 |
SSL2_DES_192_EDE3_CBC_WITH_MD5 | 0x0700C0 | DES_192_EDE3_CBC | MD5 |
SSL2_RC4_64_WITH_MD5 | 0x080080 | RC4_64 | MD5 |
Cloud Probe deployment use cases
8 Comments
Sergey Kleyman
Michael Taslitz
Alexandre Boyer
Michael Taslitz
Alexandre Boyer
Michael Taslitz
Mohamed Eraky
Dears,
regarding the approximate percentage of CPU and RAM capacity used by the Cloud Probe.
if I have 4000 hits per second last 5 mins this is mean the agent will consume 25% percentage form CPU and Memory
Sara Kamen
Hi Mohamed,
Yes, the Cloud Probe uses approximately the proportional amount of CPU and memory capacity. If the machine has the same specifications as the one documented above—on Linux, 2 virtual CPUs and 4Gb RAM—and the hit rate is about 4000 hits per second, then the agent uses approximately 20% CPU and 40% RAM.
Alternatively, you can use a machine with four times the resources—on Linux, 8 virtual CPUs and 16Gb RAM)—so that the Cloud Probe supports four times the hit rate (4 x 1000 hit/sec) with 5% CPU and 10% RAM.
Hope this helps!
--Sara