Do you have feedback on our new interface?
Do you have feedback on our new interface? Let us know HERE
Highlighted
Absent Member.. ChristopherOro Absent Member..
Absent Member..
155 views

BSM RUM

 

Hi Guys,

 

Here are some of my questions:

 

BSM-RUM

 

  1. For the RUM Engine 9.2.4 when can we expect a fix for the “filter by client / IP address” for the probe traffic  capture?

  2. Currently, if a RUM server data collector configuration needs to have SSL disabled due to communication issues, all the RUM applications related to this probe must have the SSL disabled otherwise it won’t communicate to the server data collector we want to reach, the question is, when can we expect a change where a server agent data collector can have SSL disable without affecting the rest of the server collectors related to the probe?

  3. Currently, when an Agent server data collector goes down or the service is not up, the data will stop coming through and the only way to find out is by going to the reports and check for data, the next step is to ask app server owners to restart the service, the question is: is there any plan to implement a feature in BSM that would alert you that the service for the server data collector is down?

  4. For Siteminder RUM, is there any documentation related to the benefit of this feature besides knowing that it has the ability of telling us when a user can’t authenticate through the policy server? What details ca we see? How can this help to my business? What’s the added value of this that other monitoring tools don’t have?

 

I might send more questions during the day. For now, these are my questions.

 

Christopher Orozco

Tags (3)
0 Likes
1 Reply
Micro Focus Expert
Micro Focus Expert

Re: BSM RUM

Hi Chris,

 

R&D responded to your questions as follows (check out the text with "==>" in front of it):

 

- RUM Engine 9.24 - fix for the “filter by client / IP address” for the probe traffic capture?
==> can you please share some details on what is wrong with current IP filter in probe traffic capture ?

         do you have any CR / ER number?


- Currently, if a RUM server data collector configuration needs to have SSL disabled due to communication issues, all the RUM applications related to this probe must have the SSL disabled otherwise it won’t communicate to the server data collector we want to reach, the question is, when can we expect a change where a server agent data collector can have SSL disable without affecting the rest of the server collectors related to the probe?
==> this is a misunderstanding …
rum server collector SSL means that the duplicated traffic is sent encrypted. It has nothing to do with the fact that the monitored traffic / applications should be or should not be using SSL

 

- Currently, when an Agent server data collector goes down or the service is not up, the data will stop coming through and the only way to find out is by going to the reports and check for data, the next step is to ask app server owners to restart the service, the question is: is there any plan to implement a feature in BSM that would alert you that the service for the server data collector is down?

==> yes, it is planned. If you will open an Enhancement Request it will help to properly priorize this request.


- For Siteminder RUM, is there any documentation related to the benefit of this feature besides knowing that it has the ability of telling us when a user can’t authenticate through the policy server? What details ca we see? How can this help to my business? What’s the added value of this that other monitoring tools don’t have?

==> the value of Site Minder monitoring is quite unique to “RUM metrics”
- Extract username based on site minder login for a specific session
- Sessionize based on site minder session “token / handle” which can be quite useful since site minder is a single sign on solution which will help track down user session throughout several applications

 

Greetings

Siggi

Customer Support
Micro Focus

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.