Deepak Prabhakara
Deepak Prabhakara
Apologies for the delay in getting to this, @SharmaPrakhar25 please pick this up. Many thanks.
@Musyonchez No worries, we understand.
@Tchekda You can only add custom fields as part of `fields` (which are indexed) or `metadata` (which is not indexed). And then in GraphQL you can use `fields.` or `metadata.`...
Thanks for reporting this, definitely sounds like an issue. @ukrocks007 will investigate.
In the meantime could you please try ``` fields { key value } ``` I think `fields` and `metadata` is all or nothing, you won't be able to selectively bring...
@Tchekda Cool. Only the outer `fields` attribute is indexed though. You will be able to search on those in the search query string by using `fields.div`.
@bega-cinaq In the graphql request you can specify a `cursor`, the cursor is also returned back for each query. Pagination can be implemented using this - https://boxyhq.com/docs/retraced/apis/graphql#eventedge.
@bega-cinaq You can, the Retraced npm package is just a wrapper around the APIs - https://github.com/retracedhq/retraced-js/blob/main/src/graphql.ts#L76.
Since it is cursor based search, for prevPage(s) you will have to keep the previous cursor(s) in memory - https://github.com/retracedhq/logs-viewer/blob/af925483f9e9df465e4d0377fef717063e45f0ca/src/components/containers/EventsBrowser.tsx#L217
@bega-cinaq Aah I see, we'll check to see if it's possible to use the npm package for it. Otherwise it does make sense to add support for it.