fix: Updated documentation

Author: rupozzi

docs/source/AdministratorGuide/Configuration/ConfReference/Tips/ServicesPorts/index.rst

@@ -27,8 +27,6 @@ Ordered by System / Services
 +------+----------------------+---------------------+
 | 9158 | *Framework*          | BundleDelivery      |
 +------+----------------------+---------------------+
-| 9142 | *Framework*          | Monitoring          |
-+------+----------------------+---------------------+
 | 9154 | *Framework*          | Notification        |
 +------+----------------------+---------------------+
 | 9157 | *Framework*          | Plotting            |
@@ -74,8 +72,6 @@ Ordered by port number
 +------+----------------------+---------------------+
 | 9136 | *WorkloadManagement* | JobStateUpdate      |
 +------+----------------------+---------------------+
-| 9142 | *Framework*          | Monitoring          |
-+------+----------------------+---------------------+
 | 9143 | *RequestManagement*  | RequestManager      |
 +------+----------------------+---------------------+
 | 9145 | *WorkloadManagement* | WMSAdministrator    |

docs/source/AdministratorGuide/HowTo/SystemAdministratorInterface.rst

@@ -94,8 +94,7 @@ Show setup command allows administrators to know which components, Services and
      'Services': {'Accounting': ['ReportGenerator',
                                  'DataStore'],
                   'Configuration': ['Server'],
-                  'Framework': ['Monitoring',
-                                'BundleDelivery',
+                  'Framework': ['BundleDelivery',
                                 'SecurityLogging',
                                 'Notification',
                                 'UserProfileManager',

docs/source/AdministratorGuide/Systems/Framework/Monitoring/index.rst

@@ -4,15 +4,6 @@
 The Framework/monitoring service
 ================================
 
-The Framework/Monitoring service collects information from all the active DIRAC services and Agents.
-The information are collected in *rrd* files which are keeping the monitoring information.
-This information is available as time dependent plots via the ActivityMonitor web portal application.
-You can access these plots via the "System overview plots" tab in this application. In particular, it shows the load of the services
-in terms of CPU/Memory but also numbers of queries served, numbers of active threads, pending queries, etc.
-These plots are very useful for understanding of your services behavior, for example, of your FileCatalog service.
+The framework system for the monitoring of services and agents has been removed and will no longer be used.
 
-The bookkeeping of the rrd files is kept in an sqlite database usually kept in /opt/dirac/data/monitoring/monitoring.db file.
-There is no cleaning procedure foreseen for the rrd files.
-
-A Monitoring System based on ElasticSearch database as backend is possible,
-please read about it in :ref:`Monitoring <monitoring_system>`.
+It has been replaced by an ElasticSearch-based monitoring system. You can read about it in :ref:`Monitoring <monitoring_system>`

docs/source/DeveloperGuide/Systems/Monitoring/index.rst

@@ -43,7 +43,6 @@ It is based on layered architecture and is based on DIRAC architecture:
 
 
 * **Clients**
-   * MonitoringClient is used to interact withe the Monitoring service.
    * Types contains all Monitoring types.
 
 -------------------------------

src/DIRAC/Core/DISET/private/Service.py

@@ -47,8 +47,6 @@ def __init__(self, serviceData):
           'moduleObj': <module 'serviceNameHandler' from '/home/DIRAC/FrameworkSystem/Service/serviceNameHandler.pyo'>,
           'classObj': <class 'serviceNameHandler.serviceHandler'>}
 
-          Standalone is true if there is only one service started
-          If it's false, every service is linked to a different MonitoringClient
         """
         self._svcData = serviceData
         self._name = serviceData["modName"]