RRepoGEO

REPOGEO REPORT · LITE

intelsdi-x/snap

Default branch master · commit 2b64b65f · scanned 6/23/2026, 10:53:19 PM

GitHub: 1,781 stars · 288 forks

Scan history for this repo

Score trend below includes all ready runs (older left, newer right; scroll horizontally if needed). The table is collapsed by default—expand for newest-first rows, 10 per page.

Score trend (left → right: older → newer)

2 ready scans. Expand the table below for newest-first rows (10 per page, paginated).

AI VISIBILITY SCORE
35 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
1 pass · 1 warn · 0 fail
Objective metadata checks
AI knows your name
3 / 3
Direct prompts that named your repo
HOW TO READ THIS REPORT

Action plan is what to do next — copy-pasteable changes prioritized by impact. Category visibility is the real GEO test: when a user asks an AI a brand-free question that should surface intelsdi-x/snap, does the AI actually recommend you — or your competitors? Objective checks verify the metadata signals AI engines weight first. Self-mention check detects whether AI even knows you exist by name.

Action plan — copy-paste fixes

3 prioritized changes generated by gemini-2.5-flash. Mark items done after you ship the fix.

OVERALL DIRECTION
  • hightopics#1
    Add relevant topics to the repository

    Why:

    COPY-PASTE FIX
    telemetry, metrics, observability, framework, data-collection, data-processing, plugins, go, golang
  • mediumabout#2
    Update the repository's About description

    Why:

    CURRENT
    The open telemetry framework
    COPY-PASTE FIX
    A discontinued open telemetry framework for collecting, processing, and publishing system data.
  • lowreadme#3
    Add a brief comparison section to the README

    Why:

    COPY-PASTE FIX
    Add a section to the README titled 'Original Positioning and Alternatives' that briefly explains how Snap, as a plugin-based telemetry framework, differed from broader data streaming tools (e.g., Apache NiFi, Fluentd) or complete monitoring solutions (e.g., Prometheus) in its design goals.

Category GEO backends resolved for this scan: google/gemini-2.5-flash, deepseek/deepseek-v4-flash

Category visibility — the real GEO test

Brand-free queries asked to google/gemini-2.5-flash. Did AI recommend you, or someone else?

Same questions for every model — switch tabs to compare answers and rankings.

Recall
0 / 2
0% of queries surface intelsdi-x/snap
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Apache Flink
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. Apache Flink · recommended 1×
  2. Apache Kafka Streams · recommended 1×
  3. Apache Spark Streaming · recommended 1×
  4. Apache NiFi · recommended 1×
  5. Fluentd · recommended 1×
  • CATEGORY QUERY
    Seeking an open framework to unify system data collection and processing.
    you: not recommended
    AI recommended (in order):
    1. Apache Flink
    2. Apache Kafka Streams
    3. Apache Spark Streaming
    4. Apache NiFi
    5. Fluentd
    6. Logstash
    7. Telegraf

    AI recommended 7 alternatives but never named intelsdi-x/snap. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What are robust tools for collecting, processing, and publishing diverse system metrics?
    you: not recommended
    AI recommended (in order):
    1. Prometheus (prometheus/prometheus)
    2. Datadog
    3. Grafana (grafana/grafana)
    4. Loki (grafana/loki)
    5. InfluxDB (influxdata/influxdb)
    6. Telegraf (influxdata/telegraf)
    7. New Relic
    8. Splunk Observability Cloud
    9. Beats (elastic/beats)
    10. Elasticsearch (elastic/elasticsearch)
    11. Kibana (elastic/kibana)
    12. Logstash (elastic/logstash)

    AI recommended 12 alternatives but never named intelsdi-x/snap. This is the gap to close.

    Show full AI answer

Objective checks

Rule-based audits of metadata signals AI engines weight most.

  • Metadata completeness
    warn

    Suggestion:

  • README presence
    pass

Self-mention check

Does AI even know your repo exists when asked about it directly?

  • Compared to common alternatives in this category, what is the core differentiator of intelsdi-x/snap?
    pass
    AI named intelsdi-x/snap explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • If a team adopts intelsdi-x/snap in production, what risks or prerequisites should they evaluate first?
    pass
    AI named intelsdi-x/snap explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • In one sentence, what problem does the repo intelsdi-x/snap solve, and who is the primary audience?
    pass
    AI named intelsdi-x/snap explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

Embed your GEO score

Drop this badge into the README of intelsdi-x/snap. It auto-updates whenever the report is rescanned and links back to the latest report — easy public proof that you care about AI discoverability.

RepoGEO badge previewLive preview
MARKDOWN (README)
[![RepoGEO](https://repogeo.com/badge/intelsdi-x/snap.svg)](https://repogeo.com/en/r/intelsdi-x/snap)
HTML
<a href="https://repogeo.com/en/r/intelsdi-x/snap"><img src="https://repogeo.com/badge/intelsdi-x/snap.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

intelsdi-x/snap — Lite scans stay free; this card itemizes Pro deep limits vs Lite.

  • Deep reports10 / month
  • Brand-free category queries5 vs 2 in Lite
  • Prioritized action items8 vs 3 in Lite