Skip to content

Data Access

The optional Data Access feature of Zenoss Cloud allows you to use your favorite SQL tools to display and analyze the monitoring data that Zenoss Cloud receives from your infrastructure and applications.

When you enable Zenoss Cloud Data Access, Zenoss grants you access to datasets in a dedicated Google Cloud project that contains views of your data. Then, you use the views or your own views or queries to display and analyze your data. You can use any Google BigQuery interface or any SQL tool that is compatible with BigQuery. For example:

In addition, you can export your data with tools like Matillion, or create customized integrations with data from other sources.

The following diagram illustrates the relationships among the components of Data Access.

Near real-time access

Zenoss Cloud processes incoming data in parallel pipelines. One pipeline populates the data store used by Smart View and dashboards, and another populates the data store used by Data Access. The pipelines complete their work at about the same time. Your data is available in near real-time, every time you run a query—there's no delay for ETL processing because there is no ETL processing!

Enabling Data Access

To enable the Data Access feature, you need a Google Cloud account. Zenoss Operations creates a Zenoss-owned, Google Cloud project dedicated to you, in the same Google Cloud region as your Zenoss Cloud instance. The project includes BigQuery datasets that contain views of your data. Then, Zenoss Support grants read permission to the datasets to one or more of your Google Cloud account resources.

Warning

Google charges you for querying the Data Access data store.

Once enabled, Zenoss starts retaining your data for the period specified in your Zenoss Cloud contract. Currently, the retention period options are 3 months and 15 months. Of course, you can easily export your data to your own data store and retain it there as long as you wish.

Selecting Google Cloud account resources

You can request read permission to the datasets in your dedicated Google Cloud project for one or more of the Google Cloud account resources described in the following table.

Resource Grants access to Notes
Google account email An individual Google account Could be the best option when only one or two people are running reports
Google Group All members of a Google group Simplifies administration when a rotating group of people need access
Google Apps Domain All users and groups in a Google domain Simplifies administration when a rotating group of people need access
Service account An individual service account Automated integrations through external tools may require service accounts