SigNoz/signoz · warning
partition not found in the request
Error message
partition not found in the request
What it means
Error returned by buildClickHouseQueryNetwork when the 'partition' key is absent from messagingQueue.Variables; both consumer_group and partition are mandatory for network-latency queries.
Source
Thrown at pkg/query-service/app/integrations/messagingQueues/kafka/translator.go:55
Version: "v4",
FormatForWeb: true,
}
return queryRangeParams, nil
}
func buildClickHouseQueryNetwork(messagingQueue *MessagingQueue, queueType string) (*v3.ClickHouseQuery, error) {
start := messagingQueue.Start
end := messagingQueue.End
consumerGroup, ok := messagingQueue.Variables["consumer_group"]
if !ok {
return nil, fmt.Errorf("consumer_group not found in the request")
}
partitionID, ok := messagingQueue.Variables["partition"]
if !ok {
return nil, fmt.Errorf("partition not found in the request")
}
query := generateNetworkLatencyThroughputSQL(start, end, consumerGroup, partitionID, queueType)
return &v3.ClickHouseQuery{
Query: query,
}, nil
}
func buildBuilderQueriesProducerBytes(
unixMilliStart, unixMilliEnd int64,
attributeCache *Clients,
) (map[string]*v3.BuilderQuery, error) {
bq := make(map[string]*v3.BuilderQuery)
queryName := "byte_rate"
chq := &v3.BuilderQuery{
QueryName: queryName,View on GitHub (pinned to 5069bf80b0)
Solutions
- Include partition in the variables map
- Provide a partition selector/default in the dashboard
- Validate variables before issuing the request
Example fix
// before
Variables: map[string]string{"consumer_group": "my-group"}
// after
Variables: map[string]string{"consumer_group": "my-group", "partition": "0"} Defensive patterns
Strategy: validation
Validate before calling
if (!('partition' in mq.Variables)) throw new Error('partition required'); Type guard
func hasRequiredVars(v map[string]string, keys ...string) bool { for _, k := range keys { if _, ok := v[k]; !ok { return false } }; return true } Prevention
- Include partition variable alongside consumer_group
- Validate variables client-side
When it happens
Trigger: Requesting Kafka network latency/throughput data without a partition variable in the request.
Common situations: Clients omit the partition template variable, or dashboards default it to empty when no partition is selected.
Related errors
- consumer_group not found in the request
- invalid type for Topic
- invalid type for Partition
- span evaluation feature is disabled and is experimental
- invalid type for consumer group
AI-assisted analysis of SigNoz/signoz@5069bf80b0 (2026-08-28).
Data as JSON: /api/errors/039b66314b72b436.
Report an issue: GitHub.