Skip to content

Limits for Logs

Last updated on

To ensure consistent performance and reliability for all users, STACKIT Logs enforces specific limits on data ingestion, metadata, and querying.

These limits define how much data you can send to STACKIT Logs instance and the constraints on the individual log lines.

These limits define the number of labels you can attach to log lines and the constraints on them. Labels are the keys and values used to index your logs. Efficient use of labels is critical for query performance.

STACKIT Logs is based on Loki which is designed to be “metadata light.” Unlike traditional databases, STACKIT Logs does not index the full text of logs, but only the labels. An excessive number of labels (high cardinality) significantly slows down the index and increases memory usage.

See the documentation for more details about labels.

With structured metadata, you can attach additional context to log lines without the performance penalty of traditional labels.

Structured metadata is ideal for high-cardinality data (like request_id or user_id) that you want to attach to a log line for filtering, but which shouldn’t be part of the main index labels.

See the documentation for more details about structured metadata.

These limits apply when you are retrieving log data through the STACKIT Logs API e.g. inside the Grafana dashboard.