parseable icon indicating copy to clipboard operation
parseable copied to clipboard

Parseable is an observability platform built for the modern - cloud native, AI era.

Results 116 parseable issues
Sort by recently updated
recently updated
newest added

Can we add tests to better document the expectations we wish to be fulfilled by this code _Originally posted by @de-sh in https://github.com/parseablehq/parseable/pull/1196#pullrequestreview-2625652941_

good first issue
help needed

Unlike in the case of [correlations](https://github.com/parseablehq/parseable/pull/1115/files#diff-9365947de13fa1baeffe58418f99128e8a1e778cf89b2fb11524e69fb553c0b5L44-L46), both [dashboards](https://github.com/parseablehq/parseable/blob/main/src/users/dashboards.rs#L111) and [filters](https://github.com/parseablehq/parseable/blob/main/src/users/filters.rs#L73) continue to use `Vec`. This should change in order to help with improving the codebase as most usage involves lookup...

good first issue

current: timeout set to 30 secs change: remove timeout this is to ensure querier does not timeout while processing the request and prism does not throw exception to client when...

collect CPU usage, memory usage of the server collect disk usage of the volume - data, staging, hot-tier add these metrics to Prometheus Metrics export these metrics to cluster metrics...

we can create an issue and work on it in a separate PR, similar change needs to be done at the place when we detect schema and add fields to...

`/about` output: ```json { "version": "v1.7.1", "uiVersion": "v0.9.15", "commit": "8f1a1d5", "deploymentId": "01J7FFVWBWASYTBVD3A250V21P", "updateAvailable": true, "latestVersion": "v1.7.2", "llmActive": true, "llmProvider": "OpenAI", "oidcActive": true, "license": "AGPL-3.0-only", "mode": "Distributed (Query)", "staging": "", "hotTier":...

console

We have hundreds of columns in Parseable and depend on filters and the table view a lot. We select only a handful of columns to be shown in our table...

Adds query params `stream`, `user_id`, and `type` to the endpoint Fixes #XXXX. ### Description This PR has: - [ ] been tested to ensure log ingestion and log query works....

The codebase currently uses both anyhow and thiserror for error handling. While anyhow is convenient for applications, thiserror provides better type safety, explicit error variants, and improved maintainability. consider: -...

We need to require custom partitioning to be strict, disallowing keys/values that contain special characters. This requires that the custom partitioning should adhere to not have name/values that aren't alphanumeric....