jaegertracing/jaeger · error

'%s' is no longer supported: %s; please remove the setting (

Error message

'%s' is no longer supported: %s; please remove the setting (see https://github.com/jaegertracing/jaeger/pull/9076)

What it means

Newer Elasticsearch clients in Jaeger no longer read certain legacy config keys. When validation finds one of these unwired keys, rejectUnwiredKey produces this error naming the key, the reason it was dropped, and a link to PR #9076 explaining the migration. The fix is always to remove the setting.

Source

Thrown at internal/storage/elasticsearch/config/config.go:581

	}
}

// validateLogLevel rejects an unrecognized log_level. An empty value is allowed
// and means no client logging is attached.
func validateLogLevel(level string) error {
	switch level {
	case "", "debug", "info", "error":
		return nil
	default:
		return fmt.Errorf("unrecognized log_level %q: valid values are debug, info, error", level)
	}
}

// rejectUnwiredKey builds the validation error for a config key that the current
// Elasticsearch client no longer reads, pointing operators at the PR that explains
// the change. The migration is always the same: remove the key.
func rejectUnwiredKey(key, reason string) error {
	return fmt.Errorf(
		"'%s' is no longer supported: %s; please remove the setting "+
			"(see https://github.com/jaegertracing/jaeger/pull/9076)",
		key, reason,
	)
}

View on GitHub (pinned to 806f444784)

Solutions

1. Remove the named setting from your config
2. Read PR https://github.com/jaegertracing/jaeger/pull/9076 for what replaced the key
3. If a replacement exists in the new config schema, set that instead

Example fix

// before
sniff: true
max_doc_count: 100000
// after
# both keys removed; behavior now controlled internally by the client

// keep a denylist of removed keys and check your config before upgrade
removedKeys := []string{"sniff", "max_doc_count"} // per PR #9076
for _, k := range removedKeys {
    if _, ok := rawConfig[k]; ok {
        return fmt.Errorf("key %q removed, see jaeger PR 9076", k)
    }
}

When it happens

Trigger: Calling Validate on a config that still contains a legacy key the current ES client no longer consumes (the key/reason pair is supplied by the caller of rejectUnwiredKey).

Common situations: Upgrading Jaeger from an older version where the key was honored; migrating old elasticsearch.yml/CLI flags forward without cleaning them up.

Related errors

• deprecated ES rotation flags (%s) are no longer supported; m
• unrecognized write_mode %q: valid values are %q and %q
• unrecognized log_level %q: valid values are debug, info, err
• cannot use both 'rotation' config and legacy flags (%s) simu
• indices.%s: cannot use both 'rotation' config and legacy 'da

AI-assisted analysis of jaegertracing/jaeger@806f444784 (2026-09-01). Data as JSON: /api/errors/cbe0fe5c8b8a4503. Report an issue: GitHub.