1.9) OPERACIONES MINERAS
2.2.2) GASES DE LA ATMOFERA DE MINA Y CONTAMINANTES
Each software service can have a number of specific rules that define what is to be monitored and what additional options are in effect.
Before You Begin
It is assumed for this task that you are already familiar with the concept of software services and that you know how to create and edit software services and how to open the Rules window.
After a user-defined software service is created, create a group of settings that comprise the rules for the software service. It is necessary to specify, at minimum, the IP addresses and port numbers for the software service.
To configure rules for a user-defined software service:
1. In the Rules table, right-click to open the context menu and choose Add or Open. The Rule Configuration window will open.
2. On the Services tab, select or clear Enabled to activate or de-activate the service definition. 3. In Rule description, type a brief description that will later help to identify the rule.
The description you enter at this point will be shown in the Rules table, in the column Rule Name. If no text is entered here, the IP address specified later will be used as a description for this rule.
4. Right-click in the Services table and select Add or Open from the context menu. The Service Details window appears when adding or editing rules.
5. In the Service Details window, in the IP address(es) fields, enter the server IP address, or enter a range of IP addresses if you plan to monitor more than one server.
6. In the Port(s) fields, enter the port number of the monitored service.
You can provide a range of port numbers if such a range of ports is used in your environment. Some software services may be active on a number of predefined ports or may change ports dynamically. To allow for this, you can specify a range of ports. Note, however, that specifying more than one port for a service prevents the port number from being reported for that service. If you define more than one port for a particular service name and server IP address (by either specifying a range of ports or by creating two or more distinct rules for the same service name and server IP address but with different port numbers), the AMD will report the port number for this service as 0, causing the port number to be ignored in traffic reports.
NOTE
You can define up to 5000 definitions containing a server and a port. Each association of a server and a port counts as a single definition. Specifying a range of ports counts as providing many individual definitions.
On CAS, the number of processed server definitions is limited by the license. For more information, see Per-Measurement Licensing in the Data Center Real User Monitoring
Administration Guide.
7. Optional: Select Client port(s) for reversed-direction protocols.
This option makes sense only for protocols such as X-Window whose client-server meanings are reversed. If you are uncertain, leave this option cleared.
8. Optional: Enter a virtual IP address if your network uses a pool of virtual IP addresses.
For more information, see virtual IP address [p. 122].
9. Optional: Enter the IP address of the server masking the addresses of monitored servers. Chapter 5 ∙ Oracle Forms Monitoring Configuration
If the servers you intend to monitor reside behind an appliance that masks and replaces the addresses of the target servers, you need to set NLB NAT masking IP address to the IP address of the masking server.
Without doing so, the AMD will see two unidirectional conversations instead of one bi-directional conversation between the servers and appliance:
• The conversation between the client and server is observed and recorded (IP address A talking to IP address B)
• When a response travels to the client, a different session (IP address C talking to IP address A) is recorded due to the server's IP address being replaced by the load balancer's IP address.
Unless you account for this, CAS reports will return reports with ambiguously granulated data. Using the NLB NAT masking IP address option will ensure that the AMD monitors contiguous conversations.
10. Click OK to confirm your changes and close the Service Details window. 11. Go through all available tabs and fine-tune the monitoring conditions.
The number of available configuration options depends on the analyzer. See the analyzer-specific section for more information.
12. Optional: On the Options tab, define analyzer-specific options. Enable monitoring of persistent TCP sessions
When this is selected, TCP sessions that do not start with SYN packets are monitored. By default, this is selected.
Persistent TCP sessions are TCP sessions for which the start was not recorded. They are also referred to as non-SYN sessions. These sessions can be included in the TCP statistics, based on the configuration properties you enable in RUM Console. The inclusion of these sessions may render the statistics somewhat inaccurate and must be undertaken with care.
Page load time threshold
An operation that takes more than this many seconds is considered slow. When Inherit from global setting is selected, the global setting is used. To edit the global setting, open the AMD configuration, go to Global ➤ General and set the Operation time threshold.
Generate sequenced transactions and ADS data
Select this option to provide data to the report server that consists of low-level protocol information, such as raw HTTP traffic data, which enables you to view the full HTTP request-response dialog.
13. Click OK to save the configuration.
14. Publish the draft configuration on the monitoring device.