Ref# https://docs.datalust.co/docs/whats-new

Ref# https://docs.datalust.co/docs/whats-new

Ref# https://docs.datalust.co/docs/whats-new

Ref# https://docs.datalust.co/docs/whats-new

Ref# https://docs.datalust.co/docs/whats-new

Ref# https://docs.datalust.co/docs/whats-new

Ref# https://docs.datalust.co/docs/whats-new

Whats New in 2024.3?$$$$$$User-defined; high-cardinality indexes make Seq 2024.3 the most efficient and responsive Seq yet. High-cardinality indexes target fields like request ids; client IP addresses; URIs; and email addresses; where the large number of possible values makes using signals — Seqs other index type — impractical.$$$$$$Seq 2024.3 adds a new Indexes page under the Data menu. This page gives server administrators a complete view of all active indexes and a way to suppress or delete them.

Whats New in 2024.3?$$$$$$User-defined; high-cardinality indexes make Seq 2024.3 the most efficient and responsive Seq yet. High-cardinality indexes target fields like request ids; client IP addresses; URIs; and email addresses; where the large number of possible values makes using signals — Seqs other index type — impractical.$$$$$$Seq 2024.3 adds a new Indexes page under the Data menu. This page gives server administrators a complete view of all active indexes and a way to suppress or delete them.

Refer the below link:$$$https://docs.datalust.co/docs/whats-new$$$$$$Whats New in 2024.3?$$$User-defined; high-cardinality indexes make Seq 2024.3 the most efficient and responsive Seq yet. High-cardinality indexes target fields like request ids; client IP addresses; URIs; and email addresses; where the large number of possible values makes using signals — Seqs other index type — impractical.$$$$$$High-cardinality indexes can be defined from the new Index this menu item when interacting with properties on the events page.$$$High-cardinality indexes can be defined from the new Index this menu item when interacting with properties on the events page.$$$$$$Seq 2024.3 adds a new Indexes page under the Data menu. This page gives server administrators a complete view of all active indexes and a way to suppress or delete them.$$$$$$The new indexes page showing the total index storage size of 88kb and total indexing time in the last day as 9 seconds.$$$The new indexes page showing the total index storage size of 88kb and total indexing time in the last day as 9 seconds.

Refer the below link:$$$https://docs.datalust.co/docs/whats-new$$$$$$User-defined; high-cardinality indexes make Seq 2024.3 the most efficient and responsive Seq yet. High-cardinality indexes target fields like request ids; client IP addresses; URIs; and email addresses; where the large number of possible values makes using signals — Seqs other index type — impractical.$$$$$$High-cardinality indexes can be defined from the new Index this menu item when interacting with properties on the events page.$$$High-cardinality indexes can be defined from the new Index this menu item when interacting with properties on the events page.$$$$$$Seq 2024.3 adds a new Indexes page under the Data menu. This page gives server administrators a complete view of all active indexes and a way to suppress or delete them.

Refer the below link:$$$https://docs.datalust.co/docs/whats-new$$$$$$Whats New in 2024.3?$$$User-defined; high-cardinality indexes make Seq 2024.3 the most efficient and responsive Seq yet. High-cardinality indexes target fields like request ids; client IP addresses; URIs; and email addresses; where the large number of possible values makes using signals — Seqs other index type — impractical.$$$$$$$$$Seq 2024.3 adds a new Indexes page under the Data menu. This page gives server administrators a complete view of all active indexes and a way to suppress or delete them.

Refer the below link:$$$https://docs.datalust.co/docs/whats-new$$$$$$Whats New in 2024.3?$$$User-defined; high-cardinality indexes make Seq 2024.3 the most efficient and responsive Seq yet. High-cardinality indexes target fields like request ids; client IP addresses; URIs; and email addresses; where the large number of possible values makes using signals — Seqs other index type — impractical.$$$$$$$$$Seq 2024.3 adds a new Indexes page under the Data menu. This page gives server administrators a complete view of all active indexes and a way to suppress or delete them.

Refer the below link:$$$https://docs.datalust.co/docs/whats-new$$$$$$Seq 2024.2 features a range of usability improvements in the events page.$$$Highlights include:$$$$$$Show markers in the trace view for events that were logged within that span. Only events that are also visible in the event log below will be shown; better linking what you see in the log with what you see on the trace.$$$Render span names as a message template instead of plain text; just like messages in the event log.$$$Support for logging span kinds with traces; allowing the trace view can visually distinguish client-side spans from server-side ones.$$$Show a colored bar to the left of service names in the trace view so its easier to see their relative depth in the trace.$$$More streamlined interaction on the range picker when working with custom time ranges. If you input a custom date range; subsequent interactions with the picker will open the calendar control instead of forcing you to select it from the dropdown; saving a click per interaction.$$$Support expanding and collapsing complex event properties inline. For nesty log models like OpenTelemetry; the new default of flattening event properties into a single level works well; but for other models its less ideal. You can now flatten or unflatten nested properties directly in an events property list.$$$This release also improves performance for some common kinds of queries:$$$$$$Create an internal index on @EventType; speeding up any queries that filter events based on their type.$$$Make @Id queries perform a lookup instead of a scan; speeding up queries that are finding a specific event.$$$$$$See the full release milestone on GitHub - https://github.com/datalust/seq-tickets/milestone/158?closed=1

Refer the below link:$$$https://docs.datalust.co/docs/whats-new$$$$$$Seq 2024.2 features a range of usability improvements in the events page.$$$Highlights include:$$$$$$Show markers in the trace view for events that were logged within that span. Only events that are also visible in the event log below will be shown; better linking what you see in the log with what you see on the trace.$$$Render span names as a message template instead of plain text; just like messages in the event log.$$$Support for logging span kinds with traces; allowing the trace view can visually distinguish client-side spans from server-side ones.$$$Show a colored bar to the left of service names in the trace view so its easier to see their relative depth in the trace.$$$More streamlined interaction on the range picker when working with custom time ranges. If you input a custom date range; subsequent interactions with the picker will open the calendar control instead of forcing you to select it from the dropdown; saving a click per interaction.$$$Support expanding and collapsing complex event properties inline. For nesty log models like OpenTelemetry; the new default of flattening event properties into a single level works well; but for other models its less ideal. You can now flatten or unflatten nested properties directly in an events property list.$$$This release also improves performance for some common kinds of queries:$$$$$$Create an internal index on @EventType; speeding up any queries that filter events based on their type.$$$Make @Id queries perform a lookup instead of a scan; speeding up queries that are finding a specific event.

Refer the below link:$$$https://docs.datalust.co/docs/whats-new#whats-new-in-20241