Life With Zenoss Cloud Gives You Intelligent Insights
EXPLORE THE PLATFORM
Life With Zenoss Cloud Gives You ControlPrevent IT Outages and Predict Issues
Life With Zenoss Cloud Gives You Massive Scale
Zenoss Partner Portal
Become a Partner
Learn. Discuss. Participate.Join thousands of Zenoss users and experts to learn, discuss and participate in the Zenoss Community.
Customer Support Portal
Zenoss Learning Center
Analyst ReportForrester: Top 5 Focus Areas to Succeed With DevOps
Customers for LifeAt Zenoss, our customers are at the core of everything we do.
Request A Demo
The Google Cloud Platform ZenPack adds support for monitoring resources deployed in Google Cloud.
Currently the following services are supported.
The following features are available to help you monitor resources deployed in Google Cloud Platform.
The following component types will be automatically discovered through Google Cloud Platform APIs. The components, their properties, and their relationships will be periodically remodeled to provide automatically up-to-date monitoring.
Each Google Cloud Platform project to be monitored must be added to Zenoss. The resulting Zenoss "device" equates to this project, and all of the resources within that project become components of the project in Zenoss.
All Compute Engine (GCE) components will have the following standard properties.
All Kubernetes Engine (GKE) components will have the following standard properties.
Regions will only be discovered if the project contains instances in the region.
Zones will only be discovered if the project contains instances in the zone.
Images will only be discovered if they're the source image for at least one disk within the project.
Instance templates will only be discovered if they were the template for an instance within the project, or if they're the template for a managed instance group in the project.
All project-level and region-level quotas with a limit set will be modeled.
Instance groups will only be discovered if they contain at least one instance. This includes multi-zone (region) instance groups, single-zone instance groups, and managed and unmanaged instance groups.
Machine types will only be discovered if used by an instance within the project. Note that it is possible for a machine type of the same name to vary in capabilities from region to region. So you will see multiple machine types of the same name that only vary by their zone.
Disk types will only be discovered if used by a disk within the project. Note that it is possible for a disk type of the same name to vary in capabilities from region to region. So you will see multiple disk types of the same name that only vary by their zone.
Disks will only be discovered if they're attached to at least once instance within the project.
All instances within the project will be discovered.
All instance network interfaces within the project will be discovered.
All Kubernetes clusters within the project will be discovered.
All Kubernetes node pools within the project will be discovered.
Many of the discovered resources have a status available via the Google Cloud Platform APIs. All of these are monitored by default by this ZenPack.
In addition to the per-resource-type status values listed below, each of these resource types can also have one of the following non-API status values.
Performance (metric) monitoring is done via the Stackdriver Monitoring API. The following metrics are monitored by default.
Dynamic View support is enabled for projects, and all resources that have an impactful relationship to other resources. See the Service Impact and Root Cause Analysis section for more detail on what the specific impact relationships are.
The project-level Dynamic View shows a high-level logical overview of the discovered project's resources instead of the typical (what impacts the project) view because nothing would typically impact the project as a whole.
When combined with the Zenoss Service Dynamics product, this ZenPack adds built-in service impact and root cause analysis capabilities for services running on Google Cloud. The service impact relationships described below are automatically added. These will be included in any services that contain one or more of the explicitly mentioned components.
Adding a Google Cloud Platform Project to Zenoss requires a service account with the Project View role. This role allows Zenoss to view all resource information within the project, but not make any changes.
Use the following steps to setup a service account.
Use the following steps to add a Google Cloud Platform project to Zenoss.
Alternatively you can use zenbatchload to add projects from the command line. To do this, you must create a file with contents similar to the following. Replace all values in angle brackets with your values minus the brackets. Multiple projects can be added under the same /Devices/GoogleCloudPlatform section.
You can then load the endpoint(s) with the following command.
This ZenPack has the following known limitations.
Adding using the Add Multiple Devices or Add Multiple Devices requires that an IP address or resolvable name be entered for the device. Google Cloud Platform projects don't have an IP or resolvable name, so something arbitrary such as cloud.google.com must be used. It is recommended that the Add Google Cloud Project menu item be used to add projects instead because it doesn't require a resolvable name be entered.
Continuous modeling is not currently supported by this ZenPack. This means that the model seen in Zenoss may be up to 12 hours old because it is only updated every 12 hours by default.
This ZenPack installs the following items into the Zenoss system.
View the discussion thread.
This ZenPack is developed and supported by Zenoss Inc. Commercial ZenPacks are available to Zenoss commercial customers only. Contact Zenoss to request more information regarding this or any other ZenPacks. Click here to view all available Zenoss Commercial ZenPacks.