SigNoz/signoz · error

error in builder queries

Error message

error in builder queries

What it means

Aggregate error returned by runBuilderQueries when one or more individual builder queries failed (details are in the per-query errs map / errQueriesByName). The generic message signals partial or total failure of a query-range execution.

Source

Thrown at pkg/query-service/app/querier/querier.go:193

	results := make([]*v3.Result, 0)
	errQueriesByName := make(map[string]error)
	var errs []error

	for result := range ch {
		if result.Err != nil {
			errs = append(errs, result.Err)
			errQueriesByName[result.Name] = result.Err
			continue
		}
		results = append(results, &v3.Result{
			QueryName: result.Name,
			Series:    result.Series,
		})
	}

	var err error
	if len(errs) > 0 {
		err = fmt.Errorf("error in builder queries")
	}

	return results, errQueriesByName, err
}

func (q *querier) runPromQueries(ctx context.Context, orgID valuer.UUID, params *v3.QueryRangeParamsV3) ([]*v3.Result, map[string]error, error) {
	channelResults := make(chan channelResult, len(params.CompositeQuery.PromQueries))
	var wg sync.WaitGroup
	cacheKeys := q.keyGenerator.GenerateKeys(params)

	for queryName, promQuery := range params.CompositeQuery.PromQueries {
		if promQuery.Disabled {
			continue
		}
		wg.Add(1)
		go func(queryName string, promQuery *v3.PromQuery) {
			defer wg.Done()
			cacheKey, ok := cacheKeys[queryName]

View on GitHub (pinned to 5069bf80b0)

Solutions

  1. Inspect the errQueriesByName map in the response to find the failing query and its real error
  2. Fix the specific query (attribute name, filter, aggregate function)
  3. If the cause is a ClickHouse error, check ClickHouse health/logs next
Defensive patterns

Strategy: fallback

Validate before calling

// pre-flight each builder query's filters/aggregates against known schema before executing
for name, q := range params.CompositeQuery.BuilderQueries { validateFiltersAndAggregates(name, q) }

Try / catch

Check errQueriesByName per query; render successful results and mark failed series as errors in the panel rather than failing the whole request.

Prevention

When it happens

Trigger: Any builder query inside a composite POST /api/v3/query_range failing — e.g. invalid filter, ClickHouse error, or unsupported aggregate — causes the top-level response to carry this error alongside per-query errors.

Common situations: One panel query referencing a non-existent attribute; ClickHouse connectivity/permission issues; version drift where a function or attribute changed.

Related errors

AI-assisted analysis of SigNoz/signoz@5069bf80b0 (2026-08-28). Data as JSON: /api/errors/1da99c1a3677d383. Report an issue: GitHub.