Use these examples to analyze common cost patterns in Meter Explorer and save recurring views for later reuse.
Querying Meter Data
Meter Explorer uses the same powerful query interface as other SigNoz components, making it easy to analyze your cost data with familiar patterns and syntax.
Time Range Considerations
Important: Meter data is aggregated over hourly intervals. Queries with time ranges under 1 hour will not return any data. For real-time analysis, use time ranges of 1 hour or greater.
Query Patterns
The querying patterns for meter data are identical to standard metric querying patterns. You can use the same operators, functions, and syntax that you're familiar with from other SigNoz metrics.
For detailed information about metric querying, refer to our Metrics Management Guide.
Example Queries
1. Log Size Analysis by Service
To find the total size of log records ingested by a specific service over the last day:
signoz.meter.log.size{service.name="demo-app"}
This query will show you the total log size for the demo-app service, helping you understand which services are generating the most log data.
2. Span Count by Environment
To analyze span ingestion across different environments:
signoz.meter.span.count{deployment.environment="otel-demo"}
This helps you understand the volume of trace data being generated in your environment.
3. Multi-Service Cost Comparison
To compare log ingestion across multiple services:
signoz.meter.log.size{group-by:service.name}
4. Host-Level Analysis
To identify which hosts are generating the most telemetry data:
signoz.meter.log.size{host.name = "x"}
This aggregation helps you identify hosts that might be generating excessive log data.
5. Ingestion ID-Based Analysis
To analyze telemetry data based on specific ingestion IDs:
signoz.meter.log.size{signoz.workspace.key.id = "01963e56-0bbb-7df5-b26c-2c4aa48b291a"}
Next steps
- Learn how to save and reuse queries in Meter Explorer.
- Set up Meter Alerts to get notified when usage crosses your thresholds.
