Get last processed tick for event logs

[qubicmio]

What? Why? Who?

Clients should get the information what tick the queried event logs are valid for so that they know, how recent the data is.

Acceptance Criteria

• Return the last processed event log tick number in the search response.
• Return last processed event log in the getLastProcessedTick endpoint.

Scope

• Event log queries

Open question

• Should we error, if the queried tick is larger than the last processed event log tick?

Technical Sketch (How?)

Needs changes in the ingestion pipeline and status service. We get the data from the status service.

Prerequisites

• Needs publishing of last processed event log tick in the ingestion pipeline (probably at the consumer, for example with a last log flag).
• Needs changes to the status service or a similar solution for event logs.

[sallymoc]

@qubicmio seems this is a duplication for the ticket I've also created few hours ago #123

[qubicmio]

Yes, it's a duplicate. Can we keep this one?

Prerequisite is qubic/go-log-data-publisher#25 and there are some open questions.

[sallymoc]

@qubicmio No problem, I can close mine. But please consider the following I've added to the other ticket:

1. Add a field to the GetEvents response — include the last processed events tick so the consumer knows up to which tick the data is complete.
2. Optionally/less priority, expose this information also via GetLastProcessedTick (adding an events-specific field) or a dedicated endpoint like GetEventsLastProcessedTick. This is nice-to-have and not strictly required if option 1 is implemented.
3. When using getEvents with tick filter, equivalent to what we receive in other archiver endpoints when trying to fetch data from a future tick. getTransactionsForTick and getTickData endpoints currently return:
   Status code 400
   {"code":3,"message":"invalid tick number: rpc error: code = FailedPrecondition desc = requested tick number 45581780 is greater than last processed tick 45581194","details":[]}

[qubicmio]

1+2 okay
3 not sure how we will do this.