Skip to main content

Metric Categories

Apinizer Gateway metrics are divided into four main categories:

API Traffic Metrics

Provides detailed information about API requests, success/error rates, response times, and sizes.

External Connection Metrics

Provides information about requests made to external services, success/error rates, and response times.

Cache Metrics

Provides information about cache operations, success/error rates, and response times.

JVM Metrics

Provides information about memory usage, GC, thread status, and processor usage.

Metric Formats

Each metric is collected in two formats:

General Metric

Total values without labels. For example, total number of all API requests.

Tagged Metric

Metrics enriched with labels for detailed analysis. For example, requests by API ID.

Prometheus Metric Types

Gateway metrics are collected using four basic metric types of Prometheus. These types are designed to best represent different data types and behaviors.
Each metric type serves different purposes depending on how you collect and analyze the data.

Counter

Counter (Counter)

It is a value that only increases. It starts from zero when the application runs and increases, and is reset only when the application is restarted. Counter type metrics are ideal for tracking continuously increasing values such as total request count, error count, or number of completed operations.
Available Operations:
  • sum: The total value itself
  • rate: Calculates the rate of increase over time (such as how much it increases per second)
  • increase: Calculates the total increase in a specific time range

Gauge

Gauge (Gauge)

Represents an instant value. This value can increase, decrease, or remain constant. Gauge type metrics are used to monitor an instant state or level such as current memory usage, instant CPU usage, or number of active threads.
Available Operations:
  • sum: Sum of Gauge values grouped by labels
  • mean: Average of Gauge values grouped by labels
  • min/max: Minimum or maximum of values grouped by labels

Timer

Timer (Timer)

Measures how long an operation takes (usually in milliseconds or seconds). Although technically not a special type in Prometheus, it is a metric created by libraries such as Micrometer with a combination of DistributionSummary and Counter. These metrics provide information such as average duration, maximum duration, and percentile slices.
Available Operations:
  • sum: Gives the total duration
  • count: Gives how many times the operation was performed in total
  • mean: Calculates the average duration of the operation
  • max: Gives the longest duration observed
  • histogram_quantile: Calculates percentile slices

DistributionSummary

DistributionSummary (Distribution Summary)

Used to monitor the distribution of a value. It works similarly to Timer, but instead of measuring time, it measures arbitrary numerical values such as request size, file size. This metric also provides statistical information such as average, maximum, and percentile slices.
Available Operations:
  • sum: Gives the total value
  • count: Gives the number of observed values
  • mean: Calculates the average of values
  • max: Gives the largest value observed
  • histogram_quantile: Calculates percentile slices

API Traffic Metrics

These metrics are used to monitor API requests passing through Apinizer and measure their performance. While total requests, success, error, and cache hit rates are tracked numerically, request processing time and data sizes are measured for performance analysis.
Some metrics are provided with api_id and api_name labels for API-based detailed examination.

General Metrics

Tagged Metrics (api_id, api_name)

External Connection Metrics

These metrics are used to monitor external requests made through Apinizer. Performance of external services is analyzed by measuring total requests, error count, and response time.
Some metrics are provided with the url label for URL-based detailed examination.

General Metrics

Tagged Metrics (url)

Cache Metrics

These metrics are used to monitor the interaction of the worker (gateway) pod with cache. How the worker pod performs cache operations and its performance is analyzed by measuring total requests, error count, and response time.

JVM Metrics

These metrics are used to monitor JVM performance and resource usage in the worker (gateway) pod. They help analyze the system’s efficient operation by providing detailed information about memory, GC (Garbage Collection) activity, and thread status.