Ext Ops Panel
Open dashboard
Comparison

clickstack-otel-collector vs New Relic

clickstack-otel-collector is a plugin bundle for AI coding tools published by ClickHouse Inc. Marketplaces we read that list it: 1 (Community GitHub marketplaces). New Relic is a plugin bundle for AI coding tools published by newrelic. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-21. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceclickstack-otel-collectorNew Relic
Community marketplace clickhouse/agent-skills Listed
Version: 0.6.0
Forks (GitHub): 38
Stars (GitHub): 554
Not marked · First seen
Not listed
Claude Code: claude-plugins-official Not listed Listed
Version: 1.0.0
Forks (GitHub): 1
Stars (GitHub): 2
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 1.0.0
Forks (GitHub): 1
Stars (GitHub): 2
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

clickstack-otel-collector vs New Relic
Factclickstack-otel-collectorNew Relic
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)554 (better)2 (worse)
Forks (GitHub) (differs)38 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.newrelic.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not published4
LicenceApache-2.0Apache-2.0
Repository (differs)github.com/clickhouse/agent-skillsgithub.com/newrelic/claude-code-plugin
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 4 days ago, requires a key

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

clickstack-otel-collector

In its own words, on Community GitHub marketplaces:

Step-by-step workflow for wiring an OpenTelemetry collector into a Managed ClickStack service on ClickHouse Cloud — deploying a new local collector or configuring an existing one, creating a dedicated ingest user, sending synthetic telemetry, and verifying it in ClickStack

New Relic

In its own words, on Claude Code: claude-plugins-official:

New Relic observability intelligence for Claude Code. Investigate APM performance, analyze cloud costs, debug Kubernetes, write NRQL queries, and respond to alerts — all from your terminal using New Relic telemetry data.

How to run each

clickstack-otel-collector As a Claude Code plugin

Claude Code
/plugin marketplace add clickhouse/agent-skills
/plugin install clickstack-otel-collector@clickhouse-agent-skills

New Relic As a Claude Code plugin

Claude Code
/plugin install newrelic@claude-plugins-official

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only New Relic has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: clickstack-otel-collector · What it can do: New Relic · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built