Performance and Health Tests
With HOPEX you can daily generate a repository health report. This report enables to detect:
• performance or usage anomalies that users can face daily.
• any significant change.
For this purpose, performance and health tests are run daily. Events are generated when anomalies are detected
See HOPEX Administration > Technical Articles > Supervision Events Description > Repository Health.Test Description
Infrastructure performance test description
HOPEX standard use scenarios are carried out every afternoon ("RepositoryHeath Daily Afternoon Trigger” job, 04:00 pm GMT):
• Reading of 1000 existing large objects (BLOB).
• Exploring an existing graph (1000 objects and 500 MetaAssociations).
• ERQL query on an existing graph (1000 objects and 500 MetaAssociations).
• Reading of 1000 large texts (BLOB).
• Creation of a graph including 1000 objects and 500 MetaAssociations.
• Deletion of a graph including 1000 objects and 500 MetaAssociations.
• ERQL query on a recently created graph (1000 objects and 500 MetaAssociations).
In a cluster-type configuration, performances are measured on all of the machines.Each scenario generates a result, which is stored in the repository. These results are analyzed daily in the evening ("RepositoryHeath Daily Evening Post Trigger” job, 11:05 pm GMT)
An history of 30 results are needed before generating an alert.
Repository health test description
It is essential to analyze certain usages to identify anything that might compromise data integrity, whether in the daily work or following a HOPEX update.
For all of the repositories of all of the environments, the following checks are performed every evening ("RepositoryHeath Daily Evening Trigger” job, 11:00 pm):
• Administration
• Compatibility checks between the SQL structure of the data and the server version.
• table fragmentation
• index fragmentation
• SQL maintenance plan execution
• Customization
• HOPEX data modification
• HOPEX data volume
• Usage
• workspace volume
In a cluster-type configuration, usage tests are performed randomly on a single machine only.Viewing the HOPEX Health Reports
Accessing HOPEX daily health reports
The Administration desktop gives access to HOPEX daily health reports. Each report includes the anomalies detected on all the machines, in all the repositories.
Reports are listed chronologically (the oldest first) in the following format:
HopexHealthFullReportYYYY-MM-DD_hh-mm-ss.html
with: YYYY: year, MM: month, DD: day, hh: hours, mm: minutes, and ss : seconds.
The report icon is represented by:
• 
if the health report does not include anomalies
if the health report does not include anomalies• 
if the health report includes anomalies
if the health report includes anomaliesTo view HOPEX daily health reports:
To access the content of the Repository Management pane, you must be an advanced user. In Options > Workspace > Desktop, the Display advanced UI option must be selected.1. Connect to the Administration desktop.
2. In the Repository Management > HOPEX Health reports, click the report you are interested in (the last report is at the bottom of the list).
The report is displayed in a new browser tab.
3. Click (+)/(-) beside the name of the machine, environment, repository, or aler to display/hide its details.
HOPEX Health report description
The HOPEX health report includes a short description of the anomalies detected at performance or usage level. It shows alerts detected at:
• infrastructure level (Infrastructure Alerts)
• data level (Data Alerts) for each repository of each environment
Example : detection of three alerts ("Query Execution Alert", "Macro Execution Alert" and "Data Volume Alert") at data level, on "Soho” repository.
