-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[EPIC] Trace Performance Improvements #5713
Labels
Comments
13 tasks
This was referenced Oct 21, 2024
This was referenced Nov 6, 2024
Merged
nityanandagohain
added a commit
to SigNoz/signoz-otel-collector
that referenced
this issue
Nov 10, 2024
The schema migration for trace v3. ( not integrated) Part of SigNoz/signoz#5713
nityanandagohain
added a commit
to SigNoz/signoz-otel-collector
that referenced
this issue
Nov 13, 2024
Follow up of #447 (please go through this first) Part of SigNoz/signoz#5713 * Here we are writing to signoz_index_v3 , trace_v3_resource, error span table and the tag attributes table. * The billing calculation is done using the JSON representation of spanV3. * It is not integrated i.e it won't run after getting merged * We are not storing the static fields like `statusCode` in tag attributes as the query service will take care of it ( more details in later pr's of query service. The reason I am calling this V3 is because of the table name signoz_index_v3
This was referenced Nov 14, 2024
nityanandagohain
added a commit
to SigNoz/signoz-otel-collector
that referenced
this issue
Nov 20, 2024
Add projection operations. FOR SigNoz/signoz#5713
This was referenced Nov 20, 2024
nityanandagohain
added a commit
to SigNoz/signoz-otel-collector
that referenced
this issue
Nov 20, 2024
Add support for settings in drop table FOR SigNoz/signoz#5713
This was referenced Nov 20, 2024
nityanandagohain
added a commit
to SigNoz/signoz-otel-collector
that referenced
this issue
Nov 22, 2024
Changes include * drop durationsort materialized view. ( please review #459 first) , no down operations for this as we don't want this MV anyway * added the flag `use_new_schema`, when enabled will only use the new exporters, and usage will be from the new schema. * Add resources to usage collection by uncommenting the json tag in the struct FOR SigNoz/signoz#5713 --------- Co-authored-by: Srikanth Chekuri <[email protected]>
srikanthccv
pushed a commit
to SigNoz/signoz-otel-collector
that referenced
this issue
Nov 22, 2024
Fixes SigNoz/signoz#6511 Fixes SigNoz/signoz#6512 Part of SigNoz/signoz#5713 * Updating the materialized views to use signoz_index_v3 * deleteing the old dependency graph tables
This was referenced Nov 25, 2024
Things remaining
https://github.com/SigNoz/engineering-pod/issues/2036 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
msgSystem
ormessaging.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 likemessaging.system
, should we use alias to still makemsgSystem
work to help backward compatibility?env
in sorting keysignoz_spans
table to view trace detail page. If searching by traceID is fast enough in thesignoz_index_v2
table we can remove thesignoz_spans
tablesignoz_spans
table for group bytraceID
features like trace funnels, time between producer and consumer span?The text was updated successfully, but these errors were encountered: