dsmiley commented on PR #4646: URL: https://github.com/apache/solr/pull/4646#issuecomment-5026931193
Sharing a prompt & response with AI with the wider audience here: **Context:** Historically, metrics and tracing were backed by different mechanisms. Now it's basically all OpenTelemetry. Our documentation and configuration seems too bifurcated nowadays. Of course we still need to discuss metrics separately from tracing, but there's a need IMO for a documentation page just for OTEL, and perhaps configuration too. WDYT? (not acting on this now, just capturing the thought) --- Agreed — this PR ends up duplicating the same gRPC-JARs caveat in both `distributed-tracing.adoc` and `metrics-reporting.adoc`, which is a symptom of the split. My take: don't fully merge them (tracing and metrics still have genuinely different audiences and mental models), but a single `opentelemetry.adoc` landing page covering the shared stuff once — module enablement, the JAR/dependency story, gRPC-vs-HTTP tradeoffs — with tracing and metrics as subsections or linked child pages, would kill the duplication without pretending they're the same feature. The deeper wrinkle worth flagging: it's not just docs that are split, the *configuration mechanisms* are too — tracing goes through real OTEL SDK autoconfigure (`OTEL_EXPORTER_OTLP_*` env vars), while metrics uses bespoke Solr system properties (`solr.metrics.otlpExporter*`) that don't follow OTEL conventions at all. A unified doc page would make that inconsistency more visible, which might be a feature (motivates fixing it) or a distraction (raises scope) depending on appetite. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
