RRepoGEO

REPOGEO REPORT · LITE

intelsdi-x/snap

Default branch master · commit 2b64b65f · scanned 5/13/2026, 11:46:51 AM

GitHub: 1,783 stars · 287 forks

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, monitoring, observability, data-collection, plugins, framework, go, system-data, agent
  • highreadme#2
    Move project title and core description above discontinuation notice in README

    Why:

    CURRENT
    The README currently starts with 'DISCONTINUATION OF PROJECT.' followed by the project title and description much later.
    COPY-PASTE FIX
    # **The Snap Telemetry Framework** [](https://travis-ci.org/intelsdi-x/snap) [](https://goreportcard.com/report/intelsdi-x/snap)  [](https://intelsdi-x.herokuapp.com/)

<p align="center">

</p>

**Snap** is an open telemetry framework designed to simplify the collection, processing and publishing of system data through a single API. The goals of this project are to:

* Empower systems to expose a consistent set of telemetry data
* Simplify telemetry ingestion across ubiquitous storage systems
* Allow flexible processing of telemetry data on agent (e.g. filtering and decoration)
* Provide powerful clustered control of telemetry workflows across

DISCONTINUATION OF PROJECT.

This project will no longer be maintained by Intel.

This project has been identified as having known security escapes.

Intel has ceased development and contributions including, but not limited to, maintenance, bug fixes, new releases, or updates, to this project.  

Intel no longer accepts patches to this project.

# DISCONTINUATION OF PROJECT 

**This project will no longer be maintained by Intel.  Intel will not provide or guarantee development of or support for this project, including but not limited to, maintenance, bug fixes, new releases or updates.  Patches to this project are no longer accepted by Intel. If you have an ongoing need to use this project, are interested in independently developing it, or would like to maintain patches for the community, please create your own fork of the project.**
  • mediumabout#3
    Refine the 'About' description for clarity and keywords

    Why:

    CURRENT
    The open telemetry framework
    COPY-PASTE FIX
    A plugin-driven open telemetry framework for dynamic collection, processing, and publishing of system data through flexible workflows and a single API.

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 Kafka
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. Apache Kafka · recommended 2×
  2. Prometheus · recommended 1×
  3. Grafana · recommended 1×
  4. OpenTelemetry · recommended 1×
  5. Elastic Stack · recommended 1×
  • CATEGORY QUERY
    What open source framework helps collect and process system telemetry data?
    you: not recommended
    AI recommended (in order):
    1. Prometheus
    2. Grafana
    3. OpenTelemetry
    4. Elastic Stack
    5. Elasticsearch
    6. Logstash
    7. Kibana
    8. Fluentd
    9. Fluent Bit
    10. Apache Kafka

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

    Show full AI answer
  • CATEGORY QUERY
    How to unify system data collection and publishing with a single API?
    you: not recommended
    AI recommended (in order):
    1. Apache Kafka
    2. Kafka Connect
    3. ksqlDB
    4. Apache Flink
    5. Confluent REST Proxy
    6. Confluent Platform
    7. Apache NiFi
    8. Google Cloud Pub/Sub
    9. Google Cloud Functions
    10. Cloud Run
    11. Cloud Endpoints
    12. Dataflow
    13. Cloud Logging
    14. BigQuery
    15. Firestore
    16. AWS Kinesis Data Streams
    17. Kinesis Data Firehose
    18. AWS Lambda
    19. Amazon API Gateway
    20. DynamoDB
    21. S3
    22. Azure Event Hubs
    23. Azure Functions
    24. Azure API Management
    25. MuleSoft Anypoint Platform

    AI recommended 25 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