Merge branch 'main' into improve-metrics

Author: nikhilsinhaparseable

.github/workflows/build.yaml

@@ -96,7 +96,6 @@ jobs:
         if: runner.os == 'macOS'
         run: |
           brew install \
-            cmake \
             llvm \
             pkg-config \
             zstd \

Cargo.lock

@@ -1,6 +1,6 @@
 [package]
 name = "parseable"
-version = "2.4.1"
+version = "2.4.2"
 authors = ["Parseable Team <hi@parseable.com>"]
 edition = "2024"
 rust-version = "1.88.0"
@@ -158,8 +158,8 @@ arrow = "54.0.0"
 temp-dir = "0.1.14"
 
 [package.metadata.parseable_ui]
-assets-url = "https://parseable-prism-build.s3.us-east-2.amazonaws.com/v2.4.1/build.zip"
-assets-sha1 = "19eec4d38b978270eca1026325350e38c235ac31"
+assets-url = "https://parseable-prism-build.s3.us-east-2.amazonaws.com/v2.4.2/build.zip"
+assets-sha1 = "218c43d9bb75e8f9a15df544763a874e65fa0f40"
 
 [features]
 debug = []

Cargo.toml

@@ -13,23 +13,27 @@
 [![Docs](https://img.shields.io/badge/stable%20docs-parseable.com%2Fdocs-brightgreen?style=flat&color=%2373DC8C&label=Docs)](https://logg.ing/docs)
 [![Build](https://img.shields.io/github/checks-status/parseablehq/parseable/main?style=flat&color=%2373DC8C&label=Checks)](https://github.com/parseablehq/parseable/actions)
 
-[Key Concepts](https://www.parseable.com/docs/key-concepts) | [Features](https://www.parseable.com/docs/features/alerts) | [Documentation](https://www.parseable.com/docs) | [Demo](https://demo.parseable.com/login?q=eyJ1c2VybmFtZSI6ImFkbWluIiwicGFzc3dvcmQiOiJhZG1pbiJ9) | [FAQ](https://www.parseable.com/docs/key-concepts/data-model#faq)
+[Key Concepts](https://www.parseable.com/docs/key-concepts) | [Features](https://www.parseable.com/docs/features/alerts) | [Documentation](https://www.parseable.com/docs) | [Demo](https://demo.parseable.com/login) | [FAQ](https://www.parseable.com/docs/key-concepts/data-model#faq)
 
 </div>
 
-ParseableDB is a disk **_less_**, cloud native database for logs, observability, security, and compliance. ParseableDB is built with focus on simplicity & resource efficiency. It is useful for use cases where **complete data ownership, data security and privacy are paramount**.
+Parseable is a full stack observability platform built to ingest, analyze and extract insights from all types of telemetry (MELT) data. You can run Parseable on your local machine, in the cloud, or as a managed service. To experience Parseable UI, checkout [demo.parseable.com ↗︎](https://demo.parseable.com/login).
 
-To experience Prism(Parseable UI), checkout [demo.parseable.com ↗︎](https://demo.parseable.com/login?q=eyJ1c2VybmFtZSI6ImFkbWluIiwicGFzc3dvcmQiOiJhZG1pbiJ9).
+<div align="center">
+  <a href="http://www.youtube.com/watch?feature=player_embedded&v=gYn3pFAfrVA" target="_blank">
+  <img src="http://img.youtube.com/vi/gYn3pFAfrVA/mqdefault.jpg" alt="Watch the video" width="300" height="240" />
+  </a>
+</div>
 
 ## Quickstart :zap:
 
-### Run ParseableDB
+### Run Parseable
 
 <details>
 <summary><a href="https://www.parseable.com/docs/quickstart/docker">Docker Image</a></summary>
 <p>
 
-Get started with ParseableDB Docker with a single command:
+Get started with Parseable Docker image with a single command:
 
 ```bash
 docker run -p 8000:8000 \
@@ -44,7 +48,7 @@ docker run -p 8000:8000 \
 <summary><a href="https://www.parseable.com/docs/quickstart/binary">Executable Binary</a></summary>
 <p>
 
-Download and run the ParseableDB binary on your laptop:
+Download and run the Parseable binary on your laptop:
 
 - Linux or MacOS
 
@@ -63,7 +67,7 @@ powershell -c "irm https://logg.ing/install-windows | iex"
 
 ### Ingestion and query
 
-Once you have ParseableDB running, ingest data with the below command. This will send logs to the `demo` stream. You can see the logs in the dashboard.
+Once you have Parseable running, ingest data with the below command. This will send logs to the `demo` stream. You can see the logs in the dashboard.
 
 ```bash
 curl --location --request POST 'http://localhost:8000/api/v1/ingest' \
@@ -85,10 +89,10 @@ Access the UI at [http://localhost:8000 ↗︎](http://localhost:8000). You can
 
 For quickstart, refer the [quickstart section ↗︎](#quickstart-zap).
 
-This section elaborates available options to run ParseableDB in production or development environments.
+This section elaborates available options to run Parseable in production or development environments.
 
-- Distributed ParseableDB on Kubernetes: [Helm Installation](https://www.parseable.com/docs/installation/distributed/k8s-helm).
-- Distributed ParseableDB on AWS EC2 / VMs / Linux: [Binary Installation](https://www.parseable.com/docs/installation/distributed/linux).
+- Distributed Parseable on Kubernetes: [Helm Installation](https://www.parseable.com/docs/installation/distributed/k8s-helm).
+- Distributed Parseable on AWS EC2 / VMs / Linux: [Binary Installation](https://www.parseable.com/docs/installation/distributed/linux).
 
 ## Features :rocket:
 
@@ -99,20 +103,6 @@ This section elaborates available options to run ParseableDB in production or de
 - [OAuth2 support ↗︎](https://www.parseable.com/docs/features/oepnid)
 - [OpenTelemetry support ↗︎](https://www.parseable.com/docs/OpenTelemetry/logs)
 
-## How do people use Parseable :bulb:
-
-- **Log Analytics** - Not all logs are created equal. For example application logs are seldom useful after a few days pass, but if same application also logs all the user interactions, that data is very valuable for product managers, and can be stored for a longer period. Several businesses store such high value logs and slice / dice them as needed.
-
-- **Audit & Compliance** - Organizations that need to store logs in a secure, compliant manner. Parseable's direct to S3 bucket storage mode ensures that logs are stored in a secure, cost effective manner, and can be accessed only by authorized users, while all the data is queryable in real-time.
-
-- **Observability & Monitoring** - A very large chunk of observability data is logs. Organizations that need to monitor their systems, applications, and infrastructure in real-time use Parseable as the primary log storage system so they get timely alerts, and can analyze logs in real-time.
-
-## Motivation :dart:
-
-Traditionally, logging has been seen as a text search problem. Log volumes were not high, and data ingestion or storage were not really issues. This led us to today, where all the logging platforms are primarily text search engines.
-
-But with log data growing exponentially, today's log data challenges involve whole lot more – Data ingestion, storage, and observation, all at scale. We are building Parseable to address these challenges.
-
 ## Verify images :writing_hand:
 
 Parseable builds are attested for build provenance and integrity using the [attest-build-provenance](https://github.com/actions/attest-build-provenance) action. The attestations can be verified by having the latest version of [GitHub CLI](https://github.com/cli/cli/releases/latest) installed in your system. Then, execute the following command:

README.md

@@ -46,12 +46,6 @@ parseable:
         requests:
           cpu: 250m
           memory: 1Gi
-  ## Enable audit logging on parseable nodes
-  auditLogging:
-    enabled: false
-    p_server: "http://parseable-ingestor-service.parseable.svc.cluster.local"
-    p_username: "admin"
-    p_password: "admin"
 
   ## Add environment variables to the Parseable Deployment
   env:

helm/values.yaml

@@ -316,6 +316,7 @@ impl AlertRequest {
             notification_config: self.notification_config,
             created: Utc::now(),
             tags: self.tags,
+            last_triggered_at: None,
         };
         Ok(config)
     }
@@ -342,6 +343,7 @@ pub struct AlertConfig {
     pub notification_config: NotificationConfig,
     pub created: DateTime<Utc>,
     pub tags: Option<Vec<String>>,
+    pub last_triggered_at: Option<DateTime<Utc>>,
 }
 
 #[derive(Debug, serde::Serialize, serde::Deserialize, Clone)]
@@ -367,6 +369,7 @@ pub struct AlertConfigResponse {
     pub notification_config: NotificationConfig,
     pub created: DateTime<Utc>,
     pub tags: Option<Vec<String>>,
+    pub last_triggered_at: Option<DateTime<Utc>>,
 }
 
 impl AlertConfig {
@@ -405,6 +408,7 @@ impl AlertConfig {
             notification_config: self.notification_config,
             created: self.created,
             tags: self.tags,
+            last_triggered_at: self.last_triggered_at,
         }
     }
 }

src/alerts/alert_structs.rs

@@ -62,6 +62,7 @@ pub struct ThresholdAlert {
     pub created: DateTime<Utc>,
     pub tags: Option<Vec<String>>,
     pub datasets: Vec<String>,
+    pub last_triggered_at: Option<DateTime<Utc>>,
 }
 
 #[async_trait]
@@ -192,6 +193,11 @@ impl AlertTrait for ThresholdAlert {
             // update state in memory
             self.state = new_state;
 
+            // if new state is `Triggered`, change triggered at
+            if new_state.eq(&AlertState::Triggered) {
+                self.last_triggered_at = Some(Utc::now());
+            }
+
             // update on disk
             store.put_alert(self.id, &self.to_alert_config()).await?;
             // The task should have already been removed from the list of running tasks
@@ -220,6 +226,11 @@ impl AlertTrait for ThresholdAlert {
         // update state in memory
         self.state = new_state;
 
+        // if new state is `Triggered`, change triggered at
+        if new_state.eq(&AlertState::Triggered) {
+            self.last_triggered_at = Some(Utc::now());
+        }
+
         // update on disk
         store.put_alert(self.id, &self.to_alert_config()).await?;
 
@@ -367,6 +378,7 @@ impl From<AlertConfig> for ThresholdAlert {
             created: value.created,
             tags: value.tags,
             datasets: value.datasets,
+            last_triggered_at: value.last_triggered_at,
         }
     }
 }
@@ -389,6 +401,7 @@ impl From<ThresholdAlert> for AlertConfig {
             created: val.created,
             tags: val.tags,
             datasets: val.datasets,
+            last_triggered_at: val.last_triggered_at,
         }
     }
 }

src/alerts/alert_types.rs

@@ -134,6 +134,7 @@ impl AlertConfig {
             notification_config: NotificationConfig::default(),
             created: Utc::now(),
             tags: None,
+            last_triggered_at: None,
         };
 
         // Save the migrated alert back to storage
@@ -675,6 +676,13 @@ impl AlertConfig {
             ),
         );
 
+        if let Some(ts) = self.last_triggered_at {
+            map.insert(
+                "lastTriggeredAt".to_string(),
+                serde_json::Value::String(ts.to_string()),
+            );
+        }
+
         map
     }
 }