com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_link3' is unknown.

Searching Data Within a Time Range

The following topics explain how to search for all the events in an event table that were generated during a specified time period, and how to persist data and generate events in a manner that allows such search operations to be carried out.

Defining and persisting attributes

The events are filtered by the time range based on their values for the _timestamp attribute. This attribute is added to each event table by default, and the default value for this attribute in each event is the system time at which the event was generated. If you want to override the system time, define an attribute named _timestamp for the required event stream as shown in the example below. This attribute should be defined as a payload attribute, and its data type should be long. This allows a custom timestamp to be specified for each event handled by the event stream.

Generating data

If you are not overriding the timestamp assigned by default, there are no specific approaches to follow when generating data in order to search by time range. 

If you are overriding the timestamp assigned by default, you need to specify values of the long type the _timestamp attribute you added to the event stream.

e.g., If you want to add the timestamp for an event as 16-07-1997 19:20:30, convert it to a long value (in this example, 869080830000) and enter as shown below.

Searching for Data

Click on the relevant tab to search for events by time range using the DAS Management Console or via REST API.

com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links2' is unknown.