SigNoz is an open-source observability platform native to OpenTelemetry with logs, traces and metrics in a single application. An open-source alternative to DataDog, NewRelic, etc. 🔥 🖥. 👉 Open source Application Performance Monitoring (APM) & Observability tool
[ ] How to support searching by columns like msgSystem or messaging.system together? Today users get confused whether to use either of these in filtering and groupby. Also, if we decide to use custom column names to support semantic convention of attributes like messaging.system, should we use alias to still make msgSystem work to help backward compatibility?
[ ] Flatten Resource attributes? Also, remove from map to save storage
[ ] Search by messaging, http, db and other group attributes. Flatten these or introduce grouping?
[ ] SigNoz/engineering-pod#1886
[ ] #6160
[ ] How to make search by resource attributes faster?
[ ] Add env in sorting key
[ ] We only need signoz_spans table to view trace detail page. If searching by traceID is fast enough in the signoz_index_v2 table we can remove the signoz_spans table
[ ] Will we still need signoz_spans table for group by traceID features like trace funnels, time between producer and consumer span?
[ ] Which schema will be best for support trace analytics like tree, map etc?
nityanandagohain
commented
3 days ago
msgSystemormessaging.systemtogether? Today users get confused whether to use either of these in filtering and groupby. Also, if we decide to use custom column names to support semantic convention of attributes likemessaging.system, should we use alias to still makemsgSystemwork to help backward compatibility?envin sorting keysignoz_spanstable to view trace detail page. If searching by traceID is fast enough in thesignoz_index_v2table we can remove thesignoz_spanstablesignoz_spanstable for group bytraceIDfeatures like trace funnels, time between producer and consumer span?