![]() Download and Read Hp Sitescope Manual Hp Sitescope Manual Title Type hp sitescope manual PDF sitescope user guide PDF sitescope 11 user guide PDF hp sitescope. Migration of monitors from HP sitescope 9.51 to 11.23. Migration of monitors from HP sitescope 9.51 to 11.23. Integrate Site. Scope Data with BSM's Configuration Items. Open topic with navigation. When a monitor instance is added to a Site. Scope reporting data to BSM, that monitor creates a corresponding (CI) in Run- time Service Model (RTSM). For details on understanding configuration items, see the introduction section in the RTSM Administration Guide. The Site. Scope monitors that populate RTSM include both actual monitors and the groups in which they are created. Actual monitors instances are represented in RTSM as monitor CIs. Monitor CIs receive data from the corresponding Site. Scope monitor instance and use the data, along with s (HIs) and s (ETIs) that are assigned to Site. Scope monitor metrics, to calculate status. These indicators provide a more detailed view of the health of a CI. For details on understanding indicators, see Health Indicators and KPIs. Site. Scope groups are represented as group CIs in RTSM and receive KPI status from the monitor CIs created by the monitors they are running. Site. Scope reports different levels of topology data to RTSM depending on the type of monitor and the options selected for the monitor. Site. Scope forwards the topology to create or update a CI under the following conditions: When the CI is created in Site. Scope for the first time as a result of the monitor retrieving data, regardless of whether the CI exists in RTSM. If there were any changes to any of the CI's properties. This prevents overloading RTSM with CI updates coming from the monitor. When working with specific monitors, you do not select a topology and the topology is preconfigured with the necessary data for the integration. The types of monitors are as follows: Technology Integration Monitors. These monitors report data based on the topology settings script you select and edit for the monitor. The data they report is tightly integrated with BSM. You can create a custom topology or use a predefined script to forward the relevant data. For details on these monitors and how to work with their topology settings, see Topology Settings for Technology Integration Monitors in the Using Site. Scope Guide in the Site. Scope Help. Monitors of Supported Environments. HP SiteScope Adapter Installation and Configuration Guide. HP SiteScope Adapter Installation and Configuration. 10u8-11,RedHatLinux5.8,6.0,6.1,HP-UX11iv3,andAIX7.0. SiteScope.Fordetails,see'InstallingSiteScopeonanOracle. Install HP SiteScope 11.00. Install HP SiteScope 11.00. Skip navigation Upload. Yeah, keep it Undo Close. For these supported environments, Site. Scope acts like a discovery probe when the monitor is created or its configuration is changed. When topology reporting is enabled, Site. Scope automatically discovers the application's topologies and populates RTSM with the relevant CIs and monitor CIs. For details and a list of supported environments, see Report Discovered Topologies to BSM. You can create a custom topology for monitors of a supported environment (except for monitors where the CI type is per metric as described in Monitors Reporting CI Per Metric). For details on creating a topology, see How to Configure Topology Reporting. Sitescope 11 user guide PDF hp sitescope installation guide PDF hp sitescope manual PDF user manual book 2009 toyota highlander hybrid user guide for user guide PDF.![]() Monitors Not Reporting Topology Data By Default. Site. Scope includes monitors that do not report hosts or servers and, therefore, it is not possible to know the CI type that is being monitored in advance. To include topology data for these monitors when reporting to BSM, you must select the CI type, define CI type key attributes, and map metrics related to the monitor type to specific indicators. Site. Scope then creates a CI for the monitor in RTSM and forwards monitor CI data to BSM. For the list of monitors that do not have a default topology defined, see Monitors Not Reporting Topology Data By Default. For details on how to create a topology for these monitors, see How to Configure Topology Reporting. Installation,and8443forSiteScopeenabledforSSL). HP SiteScope Failover Guide. In RTSM, CIs that have had no activity over a period of time are removed from the database. The CIs created from Site. Scope data are also subject to this aging policy. To prevent the aging policy from acting on CIs that Site. Scope has sent to BSM, Site. Scope synchronizes the data it sends to BSM. The synchronization refreshes the data for those CIs and creates activity on the CIs. For details on setting the time interval for topology synchronization, see Topology Settings. For details on the aging mechanism, see Working with CIs in the Modeling Guide. Note: Synthetic monitors and groups created by the EMS integration monitors that use Measurement are subject to the aging process regardless of the synchronization. To prevent CIs for EMS integration monitors being removed from RTSM when aging is enabled, EMS topology is resent during a hard synchronization of Site. Scope. In addition, you can enable topology resending as part of an anti- aging process by adding the property . This is due to the CI cache in Site. Scope that prevents Site. Scope from sending an unchanged CI twice. For details, see the section on BSM Integration Preferences in the Using Site. Scope Guide in the Site. Scope Help. Note: This section is relevant only to those users connecting to Site. Scope version 1. 1. When configuring monitor instances, you can also map a metric to an indicator. Indicators provide a more detailed view of the health of a CI when Site. Scope is reporting data to BSM. Site. Scope monitor metrics are mapped to indicators on a monitor type basis as follows: Monitors of supported environments and monitors that have a defined topology have indicators assigned to metrics by default. For details of these monitors, see Monitor Types and Topology Reporting above. For the list of default indicator assignments, see Indicator Mapping Alignment. For Site. Scope monitors that do not have a defined topology, there are no default indicator mappings, since these monitors can be linked to different CI types, and a single mapping cannot be set. For these monitors, you can map metrics to the appropriate indicators for the CI type linked to the monitor. For a list of monitors that do not have a defined topology, see Monitors Not Reporting Topology Data By Default. You can change the default metrics mappings in Site. Scope. If indicator mappings are modified locally in Site. Scope, these mappings are not overridden by the centralized repository mappings when Site. Scope downloads the latest mappings from BSM. This enables you to: Override indicators for a monitor instance or some metrics of a monitor. Configure non- default indicators in templates. Note that the CI type for custom topology and metric mappings is not configurable through variables in templates (they should be predefined in a template). Configure indicators for alerts. Since the CI type of a triggered alert is not always known when configuring an alert for groups or for monitors reporting a CI per metric (see Monitors Reporting CI Per Metric), you can manually enter the indicator and indicator state for an alert. For details, see HP Operations Manager Integration Settings in the Using Site. Scope Guide in the Site. Scope Help. For task details on mapping Site. Scope metrics to indicators, see Map Indicators to metrics. For user interface details, see Indicator Settings in the Using Site. Scope Guide in the Site. Scope Help. The scripts that enable Site. Scope to act as a discovery probe are stored on the BSM server in the Site. Scope package. When Site. Scope is configured to discover an application's topology, Site. Scope downloads the appropriate script from the BSM server. It then uses the script to perform the discovery while monitoring the application. The Site. Scope package includes scripts and other Site. Scope- related RTSM resources, such as views and enrichments. You can access this package in BSM in Admin > RTSM Administration > Administration > Package Manager. The package is a factory package, meaning that the out- of- the- box configurations for the package enable it to perform the discoveries in Site. Scope. For details on working with packages, see Package Administration in the Modeling Guide. Note: Advanced users may want to modify the topology scripts within the package. Be warned that the Site. Scope package uses scripts from other packages which may be shared by Site. Scope and Data Flow Management. Any changes made to the scripts in the package can also affect Data Flow Management. Any changes made to the topology script that influence the way a topology is reported to BSM can affect all the applications that use those topologies, including BSM applications and Operations Management. If you are working in a secure BSM installation that has a certificate, you may have to insert the following line into the < Site. Scope root directory> \discovery\discovery. If you want to find out what realm a given URL belongs to, you can open the URL with a Web browser and see the first line in the popup box. Note: When you modify the discovery. If a group or monitor description contain more than this number, Site. Scope truncates the description to the first 6.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
October 2016
Categories |