-
Notifications
You must be signed in to change notification settings - Fork 14
API: Expose index stats #30
Comments
Is this functionality really needed? We will have page with latest blocks for all systems, we will have page with index size, count and etc cluster info. |
Yes. This is really needed. The story is that person wants to find his transaction that was just posted on the chain. He opens search, enters transaction and gets nothing. Status shows green. The person leaves. If indexator does not function, the error message could be exposed in http://search.cyber.fund/cybernode status page together with yellow status for Search API component. This creates a feedback loop with a user and tells him what's going on. User can report specific error to us and track the progress. Makes it cybernetic. ) |
How do you see API that returns cluster info page? The critical part is only the service health check with error message in UI, so maybe leave cluster info and status checks separated. |
@YodaMike please comment on API for state of indexation story
|
|
@SiarheiSadau we should discuss, where and what info we will show to the users and then define goals for this task |
Feel free to discuss it right here. What is wrong with the scheme suggested
in initial issue comment?
…On Mar 23, 2018 7:48 PM, "Hleb Albau" ***@***.***> wrote:
@SiarheiSadau <https://github.com/siarheisadau> we should discuss, where
and what info we will show to the users and then define goals for this task
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#30 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIX9MyCgHWVTpWlZ2NOH-ROIXInm6ySMks5thO8YgaJpZM4RHBny>
.
|
@abitrolly It's not wrong, we should just explicit declare what to expose according to cyber-browser requirements. I just want more info here. |
Rename task
All other staff related to search healthy will be done in separate issue. All required info can be obtained by processing result of elastic search default stats endpoint. |
http://browser.cybersearch.io/ https://github.com/cybercongress/cyber-browser/blob/master/docs/Software_Requirements.md#1-main-page Search in [134 M] transactions in [2] blockchain systems with [135] parsed tokens. Database size : [369 GBs] |
Endpoint for statistics: http://api.cybersearch.io/search/stats |
We need to see through
cyber-ui
when indexator is not functional. For example, when it can not access underlying Parity server.Possible implementation is that the error should propagate to http://search.cyber.fund/cybernode status page and change the
cyber-search
status to yellow with exact message "ETH node (Parity) is not accessible for indexing".The text was updated successfully, but these errors were encountered: