docs(concepts): add on-prem mentions (#3949)

* docs(recipes): monitors fix typos * docs(concepts): add mention and link to on-prem
kubeshop · Aug 1, 2024 · 53c52d7 · 53c52d7
1 parent 11179b3
commit 53c52d7
Show file tree

Hide file tree

Showing 4 changed files with 27 additions and 7 deletions.
diff --git a/docs/docs/concepts/open-source-vs-commercial-features.mdx b/docs/docs/concepts/open-source-vs-commercial-features.mdx
@@ -18,7 +18,7 @@ Tracetest has two distinct feature sets:
 - [Commercial Tracetest](https://app.tracetest.io/) (Cloud + On-Prem): The commercial versions of Tracetest include both a cloud-based managed version and an on-prem enterprise version. They contain more advanced features on top of Tracetest Core for larger organizations with platform and observability teams.
 
 
-| Feature                                                                                               | Open Source                     | Commercial |
+| Feature                                                                                               | Open Source             | Commercial |
 |-------------------------------------------------------------------------------------------------------|-------------------------|------------|
 |                                                                                                       |                         |            |
 | **Core Trace-based Testing Features**                                                                 |                         |            |
@@ -32,6 +32,7 @@ Tracetest has two distinct feature sets:
 | Artillery support                                                                                     | No                      | Yes        |
 | Cypress support                                                                                       | No                      | Yes        |
 | Playwright support                                                                                    | No                      | Yes        |
+| Playwright engine trigger                                                                             | No                      | Yes        |
 | Vercel integration                                                                                    | No                      | Yes        |
 | Cloudflare integration                                                                                | No                      | Yes        |
 | AWS Lambda integration                                                                                | No                      | Yes        |
@@ -42,6 +43,7 @@ Tracetest has two distinct feature sets:
 | Runs view with filtering                                                                              | No                      | Yes        |
 | Run groups                                                                                            | No                      | Yes        |
 | Run tests or test suites in parallel                                                                  | No                      | Yes        |
+| Synthetic monitoring                                                                                  | No                      | Yes        |
 | Secrets management                                                                                    | No                      | Yes        |
 | Support for multiple polling profiles (fast vs long running tests)                                    | No                      | Yes        |
 | TypeScript / JavaScript integration                                                                   | No                      | Yes        |

diff --git a/.../docs/examples-tutorials/recipes/synthetic-monitoring-trace-based-api-tests.mdx b/.../docs/examples-tutorials/recipes/synthetic-monitoring-trace-based-api-tests.mdx
@@ -61,8 +61,8 @@ Follow these instructions to run the quick start:
 4. Fill out the [token](https://docs.tracetest.io/concepts/environment-tokens) and [API key](https://docs.tracetest.io/concepts/agent) details by editing your `.env` file. You can find these values in the Settings area for your environment.
 5. Run `docker compose up -d`.
 6. Configure your CLI with `tracetest configure -t <YOUR_API_TOKEN>`.
-7. Fill out the [token](https://docs.tracetest.io/concepts/environment-tokens) in the `tracetest-synthetic-monitor.yaml` file and apply the Tracetest Monitor with `tracetest apply monitor -f tracetest-synthetic-monitor.yaml`.
-8. Run tests from the CLI with `tracetest run test -f ./tracetest-test-api.yaml` or from the Tracetest Web UI by accessing the app with the URL `http://app:8080/books`.
+7. Apply the Tracetest Monitor with `tracetest apply monitor -f tracetest-synthetic-monitor.yaml`. This will start running the `./tracetest-test-api.yaml` test every minute.
+8. Run tests manually from the CLI with `tracetest run test -f ./tracetest-test-api.yaml` or from the Tracetest Web UI by accessing the app with the URL `http://app:8080/books`.
 
 Follow along with the sections below for a detailed breakdown of what the example you just ran did and how it works.
 
@@ -103,6 +103,16 @@ It fails because `books.length` is equal to `3`.
 
 ## Run Synthetic Monitoring
 
+You can apply the Tracetest Monitor with the CLI.
+
+```bash
+tracetest apply monitor -f tracetest-synthetic-monitor.yaml
+```
+
+This will start running the `./tracetest-test-api.yaml` test every minute.
+
+With the Web UI follow these steps to create a monitor.
+
 1. Select `Monitors` in the [Tracetest](https://app.tracetest.io/) sidebar.
 2. Create a Monitor. Select a schedule and toggle the enable monitor switch.
     ![create a monitor](https://res.cloudinary.com/djwdcmwdz/image/upload/v1721921382/docs/app.tracetest.io_organizations_ttorg_e66318ba6544b856_environments_ttenv_8fca16a31b8b6e24_monitors_page_1_guf2id.png)

diff --git a/docs/docs/getting-started/overview.mdx b/docs/docs/getting-started/overview.mdx
@@ -23,7 +23,7 @@ import {TracetestGettingStartedGuideCardsRow, TracetestCoreGettingStartedGuideCa
 Tracetest is a cloud-native application, designed to run in the cloud. Get started in three ways.
 
 - **[Cloud-based Managed Tracetest](https://app.tracetest.io/) (Free to get started!)**: Use managed infrastructure with collaboration for teams, and additional features on top of Tracetest Core.
-- **Enterprise Self-hosted Tracetest (Coming soon...)**: Same experience as with Cloud-based Managed Tracetest but self-hosted in your own infrastructure. **[Book a call](https://dub.sh/tracetest-demo) to get into early access.**
+- **Enterprise Self-hosted Tracetest**: Same experience as with Cloud-based Managed Tracetest but self-hosted in your own infrastructure. **[Request a demo](https://dub.sh/tracetest-demo) or [contact us](https://tracetest.io/contact) to get a quote!**
 - **[Hobby Self-hosted Open-source Tracetest Core](/core/getting-started/overview)**: Deploy a hobby instance in your own infrastructure with Docker or Kubernetes. Not suitable for production workloads.
 
 ## Cloud-based Managed Tracetest
@@ -36,7 +36,13 @@ Get started with the installation guide below, tailored for microservice and dis
 <TracetestGettingStartedGuideCardsRow />
 ```
 
-### Features Available in Cloud-based Managed Tracetest
+## Enterprise Self-hosted Tracetest
+
+If your organization requires you to keep data on-prem, you can use Enterprise Self-hosted Tracetest and deploy it in your own infrastructure. It contains the same features as Cloud-based Managed Tracetest.
+
+We recommend you try [Cloud-based Managed Tracetest](https://app.tracetest.io/) as a trial, and reach out to us to [request a demo](https://dub.sh/tracetest-demo) for Enterprise Self-hosted Tracetest.
+
+### Features Available in Cloud-based Managed Tracetest and Enterprise Self-hosted Tracetest
 
 #### All Tracetest Core features, plus...
 
@@ -46,7 +52,9 @@ Get started with the installation guide below, tailored for microservice and dis
 - Grouped test runs: Organize multiple tests into a single "test run group". These tests can then be executed simultaneously in parallel. The system will wait for all tests in the group to complete before delivering a consolidated "pass/fail" outcome. This functionality is particularly beneficial for halting CI/CD processes if any test in the group fails.
 - Test coverage overview: "Run" tab to monitor actively running tests with extensive meta tagging and filtering.
 - Public + private access, with Tracetest Agent or Tracetest Cloud Agent.
-- Secrets management (coming soon...)
+- Secrets management: Obfuscate values in variable sets.
+- Synthetic monitoring: Run your existing trace-based tests and test suites on a schedule and get alerted with your favorite alerting tools when they fail.
+- Playwright engine trigger: Run your existing Playwright tests as part of the Tracetest platform and enhance them with trace-based testing.
 
 ## Hobby Self-hosted Open-source Tracetest Core
 

diff --git a/examples/quick-start-nodejs-synthetic-monitoring/tracetest-synthetic-monitor.yaml b/examples/quick-start-nodejs-synthetic-monitoring/tracetest-synthetic-monitor.yaml
@@ -7,7 +7,7 @@ spec:
   tests:
   - phAZcrT4B
   schedule:
-    cron: "*/5 * * * *"
+    cron: "*/1 * * * *"
     timeZone: Etc/UTC
   alerts:
   - id: slack-webhook-message