Zenoss Core 5 Beta/Download
The Alpha program uses a virtual appliance for ease of evaluation. A VMWare and Oracle VirtualBox appliance have been provided.
To run Zenoss Core 5 Alpha, first download the appliance of your choice from SourceForge: <link>
Start Appliance using either VMWare Player or Oracle VirtualBox, and note down the banner URL reference, which should include an IP address and port in the pre-login banner. If it doesn't appear, log in as root/zenoss and run ifconfig eth0 to display the IP address of the appliance.
As you can see upon boot, we are currently using Fedora 19 as a development platform and will be targeting (at a minimum) RHEL and CentOS for the release version of Core 5.
Open Web Browser
Now, open up your Web browser and navigate to http://[ApplianceIP]:8080. In the example above, the address would be http://192.168.3.136:8080.
The following Zenoss setup screen will appear in your browser:
Click on "Get Started!". We are now ready to enter the configuration settings for this install of Zenoss.
You will be greeted by an initial settings screen that looks like this:
Fill out these fields as follows:
- Device Type
- Linux Server (SSH)
Use the following SSH Credentials:
Now, click on the "Save" button and skip the rest of the setup.
Zenoss is now ready to use! :)
Now, let's model the appliance within Zenoss, so that we don't need to wait for modeling to happen on its own. Enter in localhost in the search bar at the top hand corner of the UI:
Click on the localhost link presented by the search bar, and model the device manually by clicking on the plus sign at the bottom of the UI and selecting "Model Device":
The following screen will appear and there should be no errors returned once the model job has completed. If there are errors, review error messages and correct the stated issue(s) and/or seek help in the forums or on IRC:
The following components should now appear on the left hand pane of the device:
Note: If you click on any of the components or graphs, you may see the following error message in the UI:
The error message is OK, it just means the metric tag has not been created yet. The new back-end takes a JIT approach and will create new tags as they are added to the system vs. pre-populating the Hbase back-end with a bunch of KPI tags that may never be populated. If you wait a few minutes (polling cycle dependent - default is 5 minutes) you should start to see time series data being rendered in the new graphs, similar to the example below in a few minutes:
Exploring the New Back-end =
Here are some things you can explore related to the new performance data back-end that you may want to explore and test out.
Data be exported to CSV through each graph widget via the cog icon embedded in the title bar:
The underlying JSON data structure can also be viewed by clicking on "Definition":
If you look carefully, you can see where the metric and tag data is stated. This information can be used directly for querying and graphing time series data directly in the TSD interface section below.
Time Series Data Interface
For those who are curious as to how we are leveraging TSD under the covers, you can take a look at the TSD UI via http://[ApplianceIP]:4242/ or telnet directly into TSD via telnet [ApplianceIP] 4242.
The TSD UI has built-in auto-complete, so you can quickly find interesting metrics to graph against. Try a combination of uppercase and lowercase letters when searching for metrics.
For tags, you can use wildcard expressions, thus any metric with one or more tags can be rendered on the same graph.
You can even plot different metrics on the same graph across multiple targets. In the future by clicking on the "+" tab. API documentation will be provided so you can build your own graphs and also be able to import/export data as needed.
Note: The current version of OpenTSDB has no authentication functionality, thus it will most likely only be able for debugging/development in the final release and the UI/API will . A REST API will be available which will require authentication before any query is executed.
If the web UI appears inaccessible after starting the appliance and navigating to the stated IP:port combination, verify the network configuration of your VM appliance.
If in doubt, set the network configuration to bridged mode (assuming you are on the same network as a DHCP server) and restart the appliance, or restart the network service within the appliance itself, run ifconfig and then try again.
If you see any errors in the console around not unable to connect to 127.0.0.1:9001, please follow these steps. First, SSH into the appliance (user: root, password: zenoss). Then:
# rm $ZENHOME/var/supervisord.pid # zenoss restart
Run netstat -ant | grep 8080 and see if there anything is listening on 8080, if there is you are gold. If there isn't then restart the appliance and try again.
If you are still having issues with the UI coming up or seeing connection refused error messages in the graphs, try the following steps. First, SSH into appliance (user: root, password: zenoss). Then:
# rm $ZENHOME/var/supervisord.pid # zenoss shutdown # service hbase restart # service opentsdb restart # su - zenoss # zenoss start # zsupervisor # stop all # start all # exit
Now, run netstat -ant | grep 8080 and see if there anything is listening on 8080, if there is you are gold. Else, try rebooting the appliance.
We gladly accept bugs as a token of appreciation from our community. The filing process is the same as it is for available Core releases. The main difference is the affected version is code named ‘europa’.
If you don’t have a JIRA account already, please go ahead and create one, by navigating to jira.zenoss.com. Sign-up link: https://jira.zenoss.com/secure/Signup!default.jspa
Once you have created an account, the process is pretty straight-forward for filing a bug.
- Click on the Create Issue button on the top of the UI
- Fill out the following fields and attach any relevant screenshots/log files as required
- . Please use the defect priority guide below when filing bugs:
Defect/Bug Priorities Priority Description 1 System crash, loss of data, loss of monitoring. This bug will take top priority with development and stop the release of the software until fixed. 2 A Feature is not functioning and no workaround exists. Next highest priority for development; will not hold up release. 3 A Feature is not functioning a workaround exists. 4 Lowest severity, minor issues, cosmetic issues.