Skip to content
This repository was archived by the owner on Nov 9, 2025. It is now read-only.
This repository was archived by the owner on Nov 9, 2025. It is now read-only.

[FEAT]: Replace API-based Analyzer with Prometheus Metrics Endpoints #19

@juikalan21

Description

@juikalan21

Current issues with the analyzer:

  1. API design problem - This is considered suboptimal for metrics collection. APIs can introduce unnecessary complexity and overhead

Solution:

  1. Implementing Prometheus - Prometheus scrapes metrics directly which is more efficient than pushing via API. Also better for monitoring use cases.
Image

Key Benefits of this Change:

  1. Simplification:
  • Remove API complexity
  • Direct metrics exposure
  • Standard monitoring approach
  1. Scalability:
  • Easy to add new collectors
  • Better performance
  • Lower resource usage
  1. ** Standardization:**
  • Common metrics format
  • Built-in monitoring tools support
  • Better integration options
  1. Reliability:
  • Fewer moving parts
  • Built-in retry mechanisms
  • Better failure handling

Overall, using standard Prometheus patterns for metrics exposure will implement a more scalable and maintainable architecture.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions