...
The framework runs checks, such as:
Runs sanity build process (validation and build process both).
Executes sanity queries to validate if the queries (for both MDX and SQL) are successfully served from the query engine.
Execute sanity queries (for both MDX and SQL ) to validate the result cache.
Notify the complete status of all the checks, and so on.
You can specify the name and type of the cube semantic model to be builtprocessed, the cube semantic model on which the queries should be executed, the number of queries to be executed, the type of queries to be executed, the type of cache to be validated, and so on.
...
Parameter | Description |
status | Enable or disable cluster validation on restart |
timeToWaitInMinutes | Provide the time interval for which the system should wait until Query Engines are successfully initialized after the BI Server bootup |
emailId | Email ID of the user who will be notified. |
notifyOn | Set the value as success or failure. A notification will be sent to the email ID mentioned above. |
detailsToCapture | Specify the details of events that you want to capture. |
requiredDetails | Specify the details of logs to be captured in the following:
|
QueryExecution status | Enable or disable the execution of queries during sanity testing. By default, the system will not execute queries on the configured cubesemantic model. |
cubeName | Name of the cube semantic model on which the queries are to be executed. |
cubeID | For query execution enabled, cubeID is a mandatory field. |
Filters | Provide filters to specify which queries to execute on the cubesemantic model. If no filters are provided then the system will execute all the saved queries of the specified cubesemantic model. |