Quickly Launching the eG Monitoring Console from a Third-party Monitoring Console

By default, you cannot launch the eG monitoring console from any other thid-party console. To enable this capability, do the following:

  1. Edit the eg_services.ini file in the <EG_INSTALL_DIR>\manager\config directory.
  2. Set the quick_lauch flag in the [quick_launch] section of the file to true (default: false).
  3. Finally, save the file.

  4. Once this is done, you can proceed to configure the third-party solution with the URLs that allow quick access to specific pages of the eG monitoring console. The URL should be of the following format:

    http://<eGManagerIP>:<eGManagerPort>/final/monitor/egQuickLaunch.jsp?user=<UserName>&pass=<Password>&access=<NameofWebPage>&name=<ElementName>

    As you can see, the URL supports a user and pass (i.e., password) parameter, which will have to be configured with the credentials of a user with rights to access the eG monitoring console. The access parameter has to be configured with the name of the specific web page (in the eG monitoring console) or a pointer to the specific element (i.e., a component, segment, service, or zone) that is to be launched from the third-party console, and the name parameter should be configured with the name of the infrastructure element of interest.

  5. For now, users to third-party monitoring consoles can launch only the following pages of the eG monitoring console:

    • The component server page listing all servers assigned to a specific user;
    • The component server page listing all components of a specific component type;
    • The systems list page listing all systems assigned to a specific user or a specific system;
    • The zone list page
    • The Zone Dashboard of a specific zone
    • The segment list page
    • The segment topology page of a specific segment
    • The service list page
    • The service topology page of a specific service
    • The layer model page displaying the layer model of a specific component;
    • The layer model page displaying the measurements reported by a specific test mapped to a particular layer of a component;
    • The layer model page displaying the measurements reported by a specific descriptor supported by a test mapped to a particular layer of a component;
    • The layer model page displaying the tests mapped to a particular layer of a component;

  6. Given below are sample URLs for accessing each of the above mentioned pages. These samples conform to the following specifications:

    • eG Manager IP: 192.168.10.64
    • eG Manager Port: 7077
    • User name: admin
    • Password: admin
    • Zone to be accessed: zone1
    • Segment to be accessed: seg_new
    • Service to be accessed: myservice

    • Component to be accessed:

      • Internal name of Component type: Oracle_server
      • Component Name: oradb:1521:egurkha
      • System Name: win32

    • To access the component server page listing all components assigned to user admin:

      http://192.168.10.64:7077/final/monitor/egQuickLaunch.jsp?user=admin&pass=admin&access=componentList&name=All

      (OR)

      http://192.168.10.64:7077/final/monitor/egQuickLaunch.jsp?user=admin&pass=admin&access=component&name=All

    • To access the systems list page listing all systems monitored by user admin and the components managed on each system:

      http://192.168.10.64:7077/final/monitor/egQuickLaunch.jsp?user=admin&pass=admin&access=systemList&name=All

    • To view the state of the system, win32, in the systems list page and the components managed on that system:

      http://192.168.10.64:7077/final/monitor/egQuickLaunch.jsp?user=admin&pass=admin&access=systemList&name=win32

    • To view the current state of all components of type Oracle in the component server page:

      http://192.168.10.64:7077/final/monitor/egQuickLaunch.jsp?user=admin&pass=admin&access=componentList&name=Oracle_server

      Make sure the name parameter is configured with the internal name of the component type.

    • To access the zone list page:

      http://192.168.10.64:7077/final/monitor/egQuickLaunch.jsp?user=admin&pass=admin&access=zoneList&name=All

    • To access the segment list page:

      http://192.168.10.64:7077/final/monitor/egQuickLaunch.jsp?user=admin&pass=admin&access=segment&name=All

    • To access the service list page:

      http://192.168.10.64:7077/final/monitor/egQuickLaunch.jsp?user=admin&pass=admin&access=service&name=All

    • To access the dashboard of zone1:

      http://192.168.10.64:7077/final/monitor/egQuickLaunch.jsp?user=admin&pass=admin&access=zone&name=zone1

    • To access the topology page of the segment, seg_new:

      http://192.168.10.64:7077/final/monitor/egQuickLaunch.jsp?user=admin&pass=admin&access=segment&name=seg_new

    • To access the topology page of the service, myservice:

      http://192.168.10.64:7077/final/monitor/egQuickLaunch.jsp?user=admin&pass=admin&access=service&name=myservice

    • To access the layer model of the Oracle database server, oradb:1521:egurkha:

      http://192.168.10.64:7077/final/monitor/egQuickLaunch.jsp?user=admin&pass=admin&access=component&name=Oracle_server:oradb:1521:egurkha

      (OR)

      http://192.168.10.64:7077/final/monitor/egQuickLaunch.jsp?user=admin&pass=admin&access=system&name=Oracle_server:oradb:1521:egurkha

    • To access only the host-level layers, tests, and measurements of the Oracle database server, oradb:1521:egurkha:

      http://192.168.10.64:7077/final/monitor/egQuickLaunch.jsp?user=admin&pass=admin&access=component&name=Host_system:oradb:1521:egurkha

      (OR)

      http://192.168.10.64:7077/final/monitor/egQuickLaunch.jsp?user=admin&pass=admin&access=system&name=Host_system:oradb:1521:egurkha

      Wherever the port number is not applicable, use null. For instance, to acces the layer model of the Windows_server, win32:

      http://192.168.10.64:7077/final/monitor/egQuickLaunch.jsp?user=admin&pass=admin&access=component&name=Windows_server:win32:NULL

      (OR)

      http://192.168.10.64:7077/final/monitor/egQuickLaunch.jsp?user=admin&pass=admin&access=system&name=Windows_server:win32:NULL

    • To access the metrics reported by the Oracle SQL Network test mapped to the SQL Net layer of the Oracle database server, oradb:1521:egurkha:

      http://192.168.8.64:7077/final/monitor/egQuickLaunch.jsp?user=admin&pass=admin&access=component&name=Oracle_server: oradb:1521:egurkha&layer=SQLNET&test=OraSqlNetTest

      (OR)

      http://192.168.8.64:7077/final/monitor/egQuickLaunch.jsp?user=admin&pass=admin&access=system&name=Oracle_server: oradb:1521:egurkha&layer=SQLNET&test=OraSqlNetTest

    • To access the metrics reported by the Oracle Tablespaces test for the ORDERS tablespace (descriptor) of the Oracle database server, oradb:1521:egurkha:

      http://192.168.8.64:7077/final/monitor/egQuickLaunch.jsp?user=admin&pass=admin&access=component&name=Oracle_server: oradb:1521:egurkha&layer=TABLESPACES&test=OraSqlNetTest&descriptor=ORDERS

      (OR)

      http://192.168.8.64:7077/final/monitor/egQuickLaunch.jsp?user=admin&pass=admin&access=system&name=Oracle_server: oradb:1521:egurkha&layer=TABLESPACES&test=OraSqlNetTest&descriptor=ORDERS

    • To access the tests mapped to the Memory Structures layer of the Oracle database server, oradb:1521:egurkha:

      http://192.168.8.64:7077/final/monitor/egQuickLaunch.jsp?user=admin&pass=admin&access=component&name=Oracle_server: oradb:1521:egurkha&layer=MEMORY_STRUCTURES

      (OR)

      http://192.168.8.64:7077/final/monitor/egQuickLaunch.jsp?user=admin&pass=admin&access=system&name=Oracle_server: oradb:1521:egurkha&layer= MEMORY_STRUCTURES

Frequently Asked Questions

  • What will happen if I try to launch the COMPONENT SERVER page with the credentials of a user who does not have access to the COMPONENT SERVER page?

    When this URL is launched, the resulting page will indicate that the configured user does not have access to the page. Such a message will also appear while trying to launch a service list, zone list, or segment list page with the credentials of a user who does not have access to these pages.

  • What will happen if I try to launch the topology page of the segment, seg1, with the credentials of a user who does not have the rights to monitor seg1?

    When this URL is launched, the segment list page will appear, instead of the topology page of the segment seg1.

  • What will happen if I try to launch the topology page of the service, new_service, with the credentials of a user who does not have the rights to monitor new_service?

    When this URL is launched, the service list page will appear, instead of the topology page of the service new_service.

    Similarly, if you try to launch the layer model page of a specific component or the dashboard of a specific zone, but the user specified in the URL does not have access to the configured component/zone, then the component server page or the zone list page (as the case may be) will appear, upon launch.