Zenoss website screenshot

Zenoss

Zenoss is an AIOps and full-stack IT infrastructure monitoring platform, acquired by Virtana in May 2025 and now sold as Virtana Service Observability. It ingests metrics, events and entity models from hybrid estates — VMware, Nutanix, Kubernetes, AWS, Azure, GCP, network and storage — through on-premises Collection Zones, streaming agents and OpenTelemetry/OTLP, then applies dependency mapping, event correlation and anomaly detection to turn raw signal into service impact. The developer surface is a versioned /v1 REST API covering data ingest, event query and management, entity/model context, maintenance windows, the metric dictionary, notification Actions, credentials and user management, plus first-party proto3/gRPC contracts for the data receiver and data registry. API clients authenticate with a long-lived key in the zenoss-api-key header, issued per API Client from the console, and each tenant is assigned one of four regional endpoints.

Zenoss publishes 3 APIs on the APIs.io network. Tagged areas include AIOps, Monitoring, Observability, Infrastructure, and Event Management.

The Zenoss catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Zenoss’ developer surface includes documentation, API reference, getting-started guide, engineering blog, support, changelog, authentication, and 28 more developer resources.

50.6/100 developing ▬ flat Agent 26/100 agent aware saas Full breakdown ↓
scored 2026-09-14 · rubric v0.22.0
3 APIs
AIOpsMonitoringObservabilityInfrastructureEvent ManagementHybrid CloudOpenTelemetrygRPCMetrics

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-14 · rubric v0.22.0
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/zenoss: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 3

Individual APIs this provider publishes, each with its own machine-readable definition.

Virtana Service Observability API

Versioned /v1 REST API for the Zenoss (Virtana Service Observability) platform. Covers the data receiver (metrics, events, entity models), event query and event management, mode...

Zenoss Cloud gRPC Services

First-party proto3 service contracts published at github.com/zenoss/zenoss-protobufs and released as a Go module (v1.5.5, 2026-07-27). DataReceiverService carries unary PutEvent...

Zenoss API for Collection Zone and Resource Manager

The long-standing Zenoss JSON router API, still documented and supported for Zenoss Cloud Collection Zones and on-premises Zenoss Resource Manager / Service Dynamics. Every call...

Pricing Plans 1

Published pricing tiers and plan structures.

Zenoss Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Zenoss Rate Limits

0 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Zenoss Webhooks

ASYNCAPI

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Zenoss Authentication

3 schemes

SECURITY

Zenoss Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Zenoss Trust Center

SOC 2 Type II, CSA STAR Registry

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Scroll for all 7

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 4

Authentication, authorization, and security posture

Operate 6

Status, limits, changes, and where to get help

Commercial 5

Pricing, plans, and the legal terms of use

Company 4

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: zenoss
name: Zenoss
description: Zenoss is an AIOps and full-stack IT infrastructure monitoring platform, acquired by Virtana in May 2025 and
  now sold as Virtana Service Observability. It ingests metrics, events and entity models from hybrid estates — VMware, Nutanix,
  Kubernetes, AWS, Azure, GCP, network and storage — through on-premises Collection Zones, streaming agents and OpenTelemetry/OTLP,
  then applies dependency mapping, event correlation and anomaly detection to turn raw signal into service impact. The developer
  surface is a versioned /v1 REST API covering data ingest, event query and management, entity/model context, maintenance
  windows, the metric dictionary, notification Actions, credentials and user management, plus first-party proto3/gRPC contracts
  for the data receiver and data registry. API clients authenticate with a long-lived key in the zenoss-api-key header, issued
  per API Client from the console, and each tenant is assigned one of four regional endpoints.
type: Index
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - documentation
  - grpc
  generated: '2026-08-29'
  method: derived
accessModel:
  pricing: contact-sales
  onboarding: sales-led
  trial: false
  try_now: false
  public: false
  label: Contact sales
  confidence: high
  source:
  - plans
  - url: https://www.zenoss.com
    status: 301
    note: declared website redirects to https://www.virtana.com/service-observability/ — a different registrable domain (zenoss.com
      -> virtana.com), possible rename or acquisition (probed 2026-09-03, roadmap#169)
  generated: '2026-08-29'
  method: searched
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/zenoss.png
tags:
- AIOps
- Monitoring
- Observability
- Infrastructure
- Event Management
- Hybrid Cloud
- OpenTelemetry
- gRPC
- Metrics
url: https://raw.githubusercontent.com/api-evangelist/zenoss/refs/heads/main/apis.yml
created: '2026-03-27'
modified: '2026-08-29'
specificationVersion: '0.23'
apis:
- aid: zenoss:zenoss
  name: Virtana Service Observability API
  description: Versioned /v1 REST API for the Zenoss (Virtana Service Observability) platform. Covers the data receiver (metrics,
    events, entity models), event query and event management, model context (entity search, custom properties, maintenance
    windows), the metric/entity-field/event-field dictionary, notification Actions (triggers, rules, destinations), credentials,
    and user and group management. JSON over HTTPS, authenticated with a long-lived key in the zenoss-api-key header. Non-CRUD
    operations use Google AIP custom-method colon suffixes (:search, :count, :batchGet, :deleteBulk). Each tenant is assigned
    one of four regional endpoints — api.virtana.ai (Iowa), api2 (Las Vegas), api3 (Sydney), api4 (Frankfurt).
  humanURL: https://docs.zenoss.io/api/zenoss-api.html
  baseURL: https://api.virtana.ai
  tags:
  - AIOps
  - Monitoring
  - Observability
  - Event Management
  - Metrics
  properties:
  - type: Documentation
    url: https://docs.zenoss.io/
  - type: APIReference
    url: https://docs.zenoss.io/api/zenoss-api.html
  - type: GettingStarted
    url: https://docs.zenoss.io/start/get-started.html
  - type: Authentication
    url: authentication/zenoss-authentication.yml
  - type: Conventions
    url: conventions/zenoss-conventions.yml
  - type: ErrorCatalog
    url: errors/zenoss-problem-types.yml
  - type: DataModel
    url: data-model/zenoss-data-model.yml
  - type: Webhooks
    url: asyncapi/zenoss-webhooks.yml
- aid: zenoss:zenoss-grpc
  name: Zenoss Cloud gRPC Services
  description: First-party proto3 service contracts published at github.com/zenoss/zenoss-protobufs and released as a Go module
    (v1.5.5, 2026-07-27). DataReceiverService carries unary PutEvents, PutMetrics and PutModels plus client-streaming PutEvent,
    PutMetric and PutModel; DataRegistryService registers metric and definition metadata; CredentialManagement reads stored
    credentials; CollectionConfigService streams collection configuration to probes. RPCs carry google.api.http annotations
    binding them to the same /v1 REST paths, so the protobufs are the machine-readable contract behind the ingest surface.
  humanURL: https://docs.zenoss.io/api/receiver/data-receiver.html
  baseURL: https://api.virtana.ai
  tags:
  - gRPC
  - Metrics
  - Event Management
  - OpenTelemetry
  properties:
  - type: Protobuf
    url: grpc/zenoss-data-receiver.proto
  - type: Protobuf
    url: grpc/zenoss-data-registry.proto
  - type: Protobuf
    url: grpc/zenoss-credentials.proto
  - type: Protobuf
    url: grpc/zenoss-collection-cfg.proto
  - type: SourceCode
    url: https://github.com/zenoss/zenoss-protobufs
  - type: Documentation
    url: https://docs.zenoss.io/api/receiver/data-receiver.html
- aid: zenoss:zenoss-router-api
  name: Zenoss API for Collection Zone and Resource Manager
  description: 'The long-standing Zenoss JSON router API, still documented and supported for Zenoss Cloud Collection Zones
    and on-premises Zenoss Resource Manager / Service Dynamics. Every call is an HTTP POST of a JSON envelope — {"action":
    "<Router>", "method": "<method>", "data": [...], "tid": <n>} — to a router path under /zport/dmd (for example device_router,
    events_router, triggers_router). 61 routers are documented, covering devices, events, event classes, triggers, templates,
    reports, jobs, users, LDAP, SAML IdP, licensing, ZenPacks, impact and vendor-specific surfaces (AWS, Azure, vSphere, Hyper-V,
    OpenStack, Cisco UCS, EMC Isilon, SMI-S). Collection Zones authenticate with a z-api-key header; Resource Manager uses
    HTTP Basic. Zenoss states that some of this functionality will be replaced by the newer /v1 API services over time.'
  humanURL: https://docs.zenoss.com/api/background.html
  baseURL: https://{collection-zone-host}/cz0/zport/dmd
  tags:
  - Monitoring
  - Event Management
  - Infrastructure
  properties:
  - type: Documentation
    url: https://docs.zenoss.com/api/background.html
  - type: APIReference
    url: https://docs.zenoss.com/api/reference/devicerouter.html
  - type: GettingStarted
    url: https://docs.zenoss.com/api/how-to/use-curl.html
  - type: Authentication
    url: authentication/zenoss-authentication.yml
  - type: Conventions
    url: conventions/zenoss-conventions.yml
common:
- type: License
  name: Apache-2.0
  url: https://github.com/zenoss/zenoss-protobufs/blob/master/LICENSE
- type: Website
  url: https://www.zenoss.com
- type: Documentation
  url: https://docs.zenoss.io/
- type: APIReference
  url: https://docs.zenoss.io/api/zenoss-api.html
- type: GettingStarted
  url: https://docs.zenoss.io/start/get-started.html
- type: GitHubOrganization
  url: https://github.com/zenoss
- type: LinkedIn
  url: https://www.linkedin.com/company/zenoss-inc-
- type: Blog
  url: https://www.virtana.com/blog/
- type: BlogRSS
  url: https://www.virtana.com/feed/
- type: Support
  url: https://www.virtana.com/support/
- type: Login
  url: https://app.cloud.virtana.com/ui/new-signin
- type: TermsOfService
  url: https://www.virtana.com/legal-notices/
- type: PrivacyPolicy
  url: https://www.virtana.com/privacy/
- type: StatusPage
  url: https://status.zenoss.io/
- type: Deprecation
  url: https://docs.zenoss.io/admin/updates/deprecation.html
- type: ChangeLog
  url: https://docs.zenoss.io/admin/updates/cloud-updates.html
- type: ChangeLog
  url: changelog/zenoss-changelog.yml
- type: Lifecycle
  url: lifecycle/zenoss-lifecycle.yml
- type: Vocabulary
  url: https://docs.zenoss.io/glossary/glossary.html
- type: TrustCenter
  url: https://www.virtana.com/trust/
- type: Compliance
  url: security/zenoss-trust-center.yml
- type: Conformance
  url: conformance/zenoss-conformance.yml
- type: Packages
  url: packages/zenoss-packages.yml
- type: SDKs
  url: packages/zenoss-packages.yml
- type: Authentication
  url: authentication/zenoss-authentication.yml
- type: Conventions
  url: conventions/zenoss-conventions.yml
- type: ErrorCatalog
  url: errors/zenoss-problem-types.yml
- type: DataModel
  url: data-model/zenoss-data-model.yml
- type: Webhooks
  url: asyncapi/zenoss-webhooks.yml
- type: Plans
  url: plans/zenoss-plans-pricing.yml
- type: RateLimits
  url: rate-limits/zenoss-rate-limits.yml
- type: FinOps
  url: finops/zenoss-finops.yml
- type: DomainSecurity
  url: security/zenoss-domain-security.yml
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/zenoss-llms.txt
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
x-enrichment:
  date: '2026-08-29'
  status: enriched
  artifacts_added: 22
  pass: local-v1

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/zenoss"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/zenoss/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/zenoss/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.