Default Parameters for ZeppNotebookTest

Apache Zeppelin is an open web-based notebook that enables interactive data analytics and collaborative documents with SQL, Scala, Python, R and more. It brings data ingestion, data exploration, visualization, sharing and collaboration features to Hadoop and Spark. Apache Zeppelin interpreter concept allows any language/data-processing-backend to be plugged into Zeppelin. Zeppelin currently supports many interpreters such as Apache Spark, Python, JDBC, Markdown and Shell. Also, Apache Zeppelin provides built-in Apache Spark integration.

A Zeppelin notebook is a browser-based GUI for interactive data exploration, modeling, and visualization. As a notebook author or collaborator, you write code in a browser window. When you run the code from the browser, Zeppelin sends the code to backend processors such as Spark. The processor or service returns results; you can then use Zeppelin to review and visualize results in the browser. Apache Zeppelin has a pluggable notebook storage mechanism controlled by zeppelin.notebook.storage configuration option with multiple implementations.

Notes are fundamental elements of a Zeppelin notebook and each instance of Zeppelin has only one notebook which contains many notes. The user can create, import or delete notes which will be stored by default in the Zeppelin home notebook folder. Zeppelin is considered to be a Big Data tool which support multi-user capability. Thus, it is difficult to keep track on the number of notebooks created or deleted from Zeppelin. For this eG enterprise offers ZeppNotebookTest. This test reports the number of notebooks currently stored in the Zeppelin notebook folder and detailed diagnosis of this measure provides the name and ID of all the notebooks present in Zeppelin. This metric helps administrators to figure out the details of notebooks that are currently present in Zeppelin.

This page depicts the default parameters that need to be configured for the ZeppNotebookTest.

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• To collect metrics from an Apache zeppelin server, the eG agent monitoring the server should be configured to use JMX to connect to the JVM used by the server and pull out the metrics of interest. If JMX requires authentication only (but no security), then ensure that the USER NAME and PASSWORD parameters are configured with the credentials of a user with read-write access to JMX. To know how to create this user, refer to Monitoring Apache Zeppelin. Confirm the password by retyping it in the CONFIRM PASSWORD text box.

• By default, the SSL flag is set to No indicating that the SSL (Secured Socket Layer) is not used to connect to the target Apache Zeppelin. If not so, set the SSL flag to Yes.

• Specify the duration (in seconds) for which this test should wait for a response from the Apache Zeppelin server in the TIMEOUT text box. If there is no response from the server beyond the configured duration, the test will timeout. By default, this is set to 5 seconds.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz*” and $port will be changed to “80” when configuring a test.