diff --git a/content/en/dd_e2e/cdocs/components/stepper_customizable.md b/content/en/dd_e2e/cdocs/components/stepper_customizable.md new file mode 100644 index 00000000000..fde847bd033 --- /dev/null +++ b/content/en/dd_e2e/cdocs/components/stepper_customizable.md @@ -0,0 +1,184 @@ +--- +title: Stepper test (customizable page) +draft: true +private: true +--- +

Programming Language

Database

Programming Language

+

Database

+

Overview

This is a test page used to verify stepper scroll behavior on a customizable page. Because the page defines content_filters, it renders the sticky Cdocs filter bar below the header. When you navigate between steps, the new step title must scroll clear of both the header and the sticky filter bar.

The first step is intentionally long so that advancing to the next step forces a scroll, letting you confirm the title lands below the sticky region.

Stepper component

Install the database

Run the following command to install FakeDB:

curl -fsSL https://fakedb.example.com/install.sh | bash
+

After the installation completes, verify that FakeDB is running:

fakedb --version
+

System requirements

Before you install FakeDB, make sure your system meets the following requirements:

  • Operating system: Linux (kernel 4.15+), macOS 12+, or Windows 10+
  • CPU: x86_64 or ARM64
  • Memory: At least 2 GB of available RAM
  • Disk space: At least 500 MB of free disk space for the binary and initial data directory
  • Network: Outbound access to fakedb.example.com on port 443 during installation

What the installer does

The one-line installer performs the following steps:

  1. Downloads the latest stable FakeDB binary for your platform
  2. Verifies the download signature using GPG
  3. Copies the binary to /usr/local/bin/fakedb
  4. Creates the default data directory at ~/.fakedb/data
  5. Writes a default configuration file to ~/.fakedb/fakedb.conf
  6. Registers FakeDB as a systemd service (Linux) or launchd agent (macOS)

Manual installation

If you prefer to install FakeDB without running the one-line installer, download the binary directly:

curl -fsSL https://releases.fakedb.example.com/v2.4.1/fakedb-linux-amd64.tar.gz -o fakedb.tar.gz
+tar -xzf fakedb.tar.gz
+sudo mv fakedb /usr/local/bin/fakedb
+sudo chmod +x /usr/local/bin/fakedb
+

Verify the installation:

fakedb --version
+# Expected output: fakedb version 2.4.1 (build 20240315)
+

Troubleshooting installation issues

Permission denied when running the installer

If you see a Permission denied error, run the installer with sudo:

sudo bash -c "$(curl -fsSL https://fakedb.example.com/install.sh)"
+

GPG verification failed

If GPG verification fails, your keyring may be outdated. Update it:

gpg --keyserver hkps://keys.openpgp.org --recv-keys FAKEDB_KEY_ID
+

Port already in use

If port 5432 is already in use by another process, identify the process:

sudo lsof -i :5432
+

You can then either stop the conflicting process or configure FakeDB to use a different port in the next step.

Configure the database

Create a configuration file for FakeDB:

fakedb:
+  host: localhost
+  port: 5432
+  database: mydb
+

Connect to the database

Start the FakeDB service and open a connection:

fakedb start
+fakedb connect --host localhost --port 5432 --database mydb
+

You're all set. Happy databasing!

+
\ No newline at end of file diff --git a/content/en/real_user_monitoring/ownership_of_views.md b/content/en/real_user_monitoring/ownership_of_views.md index 9d77e76c6c1..d8b80cdc058 100644 --- a/content/en/real_user_monitoring/ownership_of_views.md +++ b/content/en/real_user_monitoring/ownership_of_views.md @@ -18,6 +18,20 @@ Ownership of views lets you see only the RUM metrics and events for the parts of By default, the toggle is enabled, which filters metrics and event data to show only the one coming from views your team owns. If you belong to multiple teams, you can enable or disable specific team filters. The teams that own a view are also listed in the top-right corner of all event side panels. +## Ownership rules + +There are two types of rules to configure ownership of views: + +1. Exact rules, which map one-to-one with a view name +2. Prefix rules, which capture all views that contain the prefix in their name + +{{< img src="/real_user_monitoring/ownership_of_views/ownership-rule-type.png" alt="Side panel displaying the two different types of rules to define ownership of views." >}} + +Every must also have at least one team and one scope defined. Two scope types are supported: +- For the current RUM application across all services +- For a specific service across all applications + + ## Setup
To use this feature, your organization must have teams enabled and configured.
@@ -25,8 +39,9 @@ By default, the toggle is enabled, which filters metrics and event data to show To configure team ownership for your application's views: 1. In Datadog, navigate to the [{{< ui >}}Digital Experience{{< /ui >}} > {{< ui >}}Manage Applications{{< /ui >}}][1] page and select your application. -2. In the left navigation menu, select {{< ui >}}Team Ownership{{< /ui >}}. -3. For each selected view, click {{< ui >}}Edit Teams{{< /ui >}} and select one or more teams. This attributes each view in your application to those teams. +2. In the left navigation menu, select {{< ui >}}Ownership{{< /ui >}}. +3. For each view, click {{< ui >}}Missing Ownership{{< /ui >}} and create a rule for the view. +4. Click on the {{< ui >}}All Rules{{< /ui >}} tab to review all created rules and their associated views. After you associate a view with a team, Datadog automatically attributes new event data to that team. diff --git a/static/images/real_user_monitoring/ownership_of_views/ownership-application-management-2.png b/static/images/real_user_monitoring/ownership_of_views/ownership-application-management-2.png index aad398c9d00..0e57db73fd4 100644 Binary files a/static/images/real_user_monitoring/ownership_of_views/ownership-application-management-2.png and b/static/images/real_user_monitoring/ownership_of_views/ownership-application-management-2.png differ diff --git a/static/images/real_user_monitoring/ownership_of_views/ownership-rule-type.png b/static/images/real_user_monitoring/ownership_of_views/ownership-rule-type.png new file mode 100644 index 00000000000..8eb61cb5958 Binary files /dev/null and b/static/images/real_user_monitoring/ownership_of_views/ownership-rule-type.png differ