Measure how your DOCX editor feels.

See how fast typing reaches the screen and how long documents take to open, for every editor version you release. Built-in diagnostics exclude document content.

Set up telemetryReview the privacy model
DOCX Editor · last 24 hoursLIVE
Editor sessions
212
Documents opened
181
Opens succeeding
99.8%
Typical open time
671 ms
Presses over 200 ms
0.91%
Input delay
median95th percentile
00:0012:00now
Sessions per day
Montoday
Open time by document size
Median
1-9 pages0.6 s
10-99 pages-
100+ pages-
Excluded from built-in diagnosticsdocument textfile namesauthor names

Monitor the editing experience, privacy first.

Destinations
OpenTelemetry, Sentry, Prometheus, logs
Document content
Excluded from built-in diagnostics
Dashboards
Grafana, ready to import
/ Capabilities

Know how editing feels, without reading the document.

Input delay

Measure the time from a key press to the next frame on screen, by document size and editor version. One summary per minute keeps the volume low.

Measure performance→

Open and layout time

See how long documents take to open and lay out, by file size and page count. Compare each release with the one before it.

Import the dashboards→

Privacy first

Built-in diagnostics use closed lists of codes, buckets, and timings, and the package validates them again before export. Your consent function runs before each event.

Read the privacy model→
/ Implementation

Add telemetry to your editor.

Create one client, register its module, and choose where the data goes. The package sends nothing until you configure an exporter.

  1. 01

    Create the client

    Choose the areas to record and connect your consent manager. Create the client once, outside your components.

    Set up an editor
  2. 02

    Choose a destination

    Send metrics to OpenTelemetry or Prometheus, issues to Sentry, or log records to Better Stack, Axiom, or Datadog.

    Send to a log service
  3. 03

    Import the dashboards

    Import the Grafana dashboards for editor experience and collaboration servers. Set targets from a few weeks of your own traffic.

    Import the dashboards
/ Industry applications

Examples by industry.

You define access, validation, retention, and approval rules. DOCX Editor applies supported document operations.

Product teams

Track the editing experience

Follow input delay and open time as your users and their documents grow. Find the document sizes that need attention first.

    Platform teams

    Compare releases

    Compare input delay and open time by editor version and app version, and confirm that an upgrade made editing faster.

      Regulated workloads

      Review a small, closed set of fields

      Built-in diagnostics exclude document text, file names, and author names. Use the privacy review checklist for the attributes and SDK settings you add.

        / Questions

        Common questions

        Does telemetry send document content?+

        Built-in diagnostics do not. They contain codes, booleans, bucketed sizes and counts, and timings, and the package validates them again before export. You control the attributes you add and the data your monitoring SDKs collect. Read the privacy model.

        Does the package send data by itself?+

        No. It sends data only to the exporters you configure. Without an exporter, nothing leaves the page.

        How do I respect a user's consent choice?+

        Pass a consent function. When it returns false, the client drops new events. browserPrivacySignals() reads Global Privacy Control and Do Not Track. Control consent.

        Which monitoring tools are supported?+

        Any OpenTelemetry backend, Prometheus, Sentry, and HTTP log services such as Better Stack. A callback exporter sends events to any other tool.

        Can I monitor collaboration servers?+

        Yes. Server metrics cover rooms, people, memory, and load and store times. Set up collaboration servers.

        Which license does telemetry use?+

        @docx-editor.dev/telemetry uses the EigenPal Pro License. You can evaluate it for free. Production use requires a Pro agreement. See pricing.

        Add DOCX editing to your application.

        Start with the open-source editor. Add commercial review and automation features when your workflow needs them.

        See pricingStart building

        More document solutions

        Markdown Converter

        Convert Word (.docx) files to paginated Markdown for agents and retrieval-augmented generation (RAG). Keep page references with body text and read headers and footers separately.

        Explore Markdown Converter→

        PDF converter

        Convert DOCX files to PDF on your Node.js server. Use the same fonts and layout settings as the editor to keep page breaks consistent.

        Explore PDF converter→

        Custom UI

        Build a DOCX editor interface in React or Vue with your own components and CSS. Replace toolbars, comment threads, and tracked-change controls. Public hooks and chrome slots connect your UI to the editor's state and commands.

        Explore Custom UI→

        DOCX agents

        Build AI agents that read, draft, comment, and redline DOCX files through typed document operations. You control the model, tools, permissions, and review steps.

        Explore DOCX agents→

        Collaborative editor

        Let several people edit one DOCX file together. Show live carets and selections, keep each person's undo history separate, and merge offline edits after reconnection.

        Explore Collaborative editor→

        Word-faithful document preview

        Add a React or Vue DOCX viewer with paginated layout and document fonts. Render tables, images, headers, and footers. Add Pro to review comments and tracked changes.

        Explore Word-faithful document preview→