Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Add cluster info api end point #699

Conversation

Eshanatnight
Copy link
Contributor

This PR contains the ingester side changes

Fixes #698.

Description

Add Endpoint on Query Server /api/v1/cluster/info to fetch the information and status of the ingest server


This PR has:

  • been tested to ensure log ingestion and log query works.
  • added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
  • added documentation for new or modified features or behaviors.

on hitting {url}/api/v1/cluster/info
it would return a json response with the information on the cluster

Return JSON looks like
```
[
    {
        domain_name: "<domain_name>:<port>",
        reachable: bool,
        error: string error message,
        status: string
    },
    .
    .
    .
}
@Eshanatnight Eshanatnight force-pushed the impl-cluster-api-endpoints branch from d06370c to 3f057b8 Compare March 11, 2024 07:18
@Eshanatnight Eshanatnight changed the title feat: distributed Implementation of the Parseable Server (#656) feat: Add cluster info api end point Mar 11, 2024
1. Add Action ListCluster
2. Authorize /cluster/info for ListCluster
When in S3 Mode, get_objects was fetching all the files that
contained the pattern "ingester".
@nikhilsinhaparseable nikhilsinhaparseable merged commit a39b9f7 into parseablehq:distributed Mar 13, 2024
6 checks passed
@Eshanatnight Eshanatnight deleted the impl-cluster-api-endpoints branch March 13, 2024 11:39
Eshanatnight added a commit to Eshanatnight/parseable that referenced this pull request Apr 1, 2024
* feat: add endpoint on Query Server to fetch the cluster info

on hitting {url}/api/v1/cluster/info
it would return a json response with the information on the cluster

Return JSON looks like
```
[
    {
        domain_name: "<domain_name>:<port>",
        reachable: bool,
        error: string error message,
        status: string
    },
    .
    .
    .

]

* feat: add auth for /cluster/info endpoint

1. Add Action ListCluster
2. Authorize /cluster/info for ListCluster

* fix: get_objects fetch the proper files

When in S3 Mode, get_objects was fetching all the files 
that contained the pattern "ingester".
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants