feat: Add ability to disable data sources #1567

alok87 · 2026-01-07T16:52:08Z

Summary

This PR implements the ability to enable/disable data sources from the UI. Disabled sources remain visible in the Sources management page but are automatically hidden from all dropdowns and selection menus throughout the application.

Changes

Backend

Added disabled field to the Source model (MongoDB schema)
- Type: Boolean
- Default: false
- Sources are enabled by default

Frontend - Schema & Types

Updated SourceBaseSchema in common-utils to include optional disabled field
Type validation ensures backward compatibility with existing sources

Frontend - UI Components

Sources Management Page

Added toggle switch to enable/disable each source
Switch displays current state: "Enabled" or "Disabled"
Sources can be toggled on/off with a single click
All sources (enabled and disabled) remain visible in this management view

Source Filtering

Updated all source selection dropdowns to filter out disabled sources:

Search Page: Default source selection now excludes disabled sources
Sessions Page: Auto-selection only considers enabled session sources
Services Dashboard: Trace source dropdown filters out disabled sources
Kubernetes Dashboard: Log and metric source selection excludes disabled sources
All dropdowns: Generic source selector component filters disabled sources

User Experience

When a source is disabled:

✅ Still visible in Team Settings → Sources (management page)
✅ Can be re-enabled via toggle switch
❌ Not shown in any source selection dropdowns
❌ Not auto-selected as default source
❌ Not available for new searches, dashboards, or queries

When a source is enabled:

✅ Visible everywhere (management page + all dropdowns)
✅ Available for selection in all features
✅ Can be auto-selected as default
✅ Normal behavior throughout the app

Use Cases

This feature enables teams to:

Temporarily hide data sources without deleting them
Keep development/staging sources configured but hidden in production
Manage seasonal data sources that are only needed periodically
Reduce clutter in source selection dropdowns
Maintain source configurations while preventing accidental use

Testing

Manually tested:

✅ Toggle switch works correctly in Sources list
✅ Disabled sources hidden from Search page dropdown
✅ Disabled sources hidden from Sessions page
✅ Disabled sources hidden from Services dashboard
✅ Disabled sources hidden from Kubernetes dashboard
✅ Default source selection skips disabled sources
✅ Re-enabling a source makes it immediately available
✅ Existing sources without the field work correctly (default enabled)

Backward Compatibility

✅ Existing sources without disabled field are treated as enabled
✅ No database migration required
✅ No breaking changes to API
✅ Field is optional in schema validation

Changelog

Updated changelogs for all affected packages:

@hyperdx/app - UI components and filtering logic
@hyperdx/api - Backend model changes
@hyperdx/common-utils - Schema updates

changeset-bot · 2026-01-07T16:52:12Z

🦋 Changeset detected

Latest commit: 15ed071

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages

Name	Type
@hyperdx/common-utils	Patch
@hyperdx/api	Patch
@hyperdx/app	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

vercel · 2026-01-07T16:52:49Z

@alok87 is attempting to deploy a commit to the HyperDX Team on Vercel.

A member of the Team first needs to authorize it.

brandon-pereira · 2026-01-07T22:15:24Z

packages/api/CHANGELOG.md


 ### Patch Changes

+- feat: Add ability to disable data sources (fixes #1545) - Added 'disabled' field to Source model for toggling source visibility


Note: we should run yarn changeset and revert changes to CHANGELOG.md as this file is generated at release time

brandon-pereira · 2026-01-07T22:21:56Z

packages/app/src/components/Sources/SourcesList.tsx

-                    </Group>
-                  </Group>
-                </Text>
+              <div style={{ flex: 1 }}>


@elizabetdev can you provide UX feedback here? My gut tells me this feature won't be one of the main things people are doing it, so we should move it inside the form itself (see screenshots):

Example of where to put disabled potentially

Closed UI (toggle could be removed and add "Disabled" badge to details row?)

@alok87 functionality wise, things look good. pending @elizabetdev's feedback we could simplify some form code, lets see what she says :)

Done. Also made the disabled one less highlighted.

@alok87 The enabled/disabled toggle placement looks good to me 👍 Since it’s a high-level state, I agree it shouldn’t be buried under “Optional Fields.”

For the disabled state in the list view, the reduced opacity works well to show the status. One small thing to watch out for is the expand or collapse arrow (chevron). It would be good to keep that at full opacity.

If the arrow dims along with the text, the row can feel unclickable or read-only. Keeping the arrow bright helps signal that the row is still interactive and can be opened to update settings or re-enable it.

- Add 'disabled' field to source schema (common-utils, api, app) - Move enable/disable toggle to expanded form header (top right) - Dim disabled sources in list view (50% opacity when closed) - Show full opacity when form is open for editing - Filter out disabled sources in search page, dashboards, sessions - Add changeset for release management - Smooth transition effects for visual feedback Based on PR feedback, form simplification will be addressed separately.

vercel · 2026-01-08T12:09:23Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
hyperdx-v2-oss-app	Ready	Preview, Comment	Jan 8, 2026 0:12am

brandon-pereira · 2026-01-08T15:33:07Z

packages/app/src/components/Sources/SourceForm.tsx

  const { data: connections } = useConnections();
+  const updateSourceMutation = useUpdateSource();
+
+  const handleDisabledToggle = useCallback(


Thoughts on removing this code and just allowing the form to manage updating this value on save?

brandon-pereira reviewed Jan 7, 2026

View reviewed changes

alok87 force-pushed the fix-1545-disable-datasource branch 3 times, most recently from 8c0e4d4 to a2e1e18 Compare January 8, 2026 03:42

alok87 force-pushed the fix-1545-disable-datasource branch from a2e1e18 to 15ed071 Compare January 8, 2026 03:52

brandon-pereira reviewed Jan 8, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feat: Add ability to disable data sources #1567

feat: Add ability to disable data sources #1567

Uh oh!

alok87 commented Jan 7, 2026 •

edited

Loading

Uh oh!

changeset-bot bot commented Jan 7, 2026 •

edited

Loading

Uh oh!

vercel bot commented Jan 7, 2026

Uh oh!

brandon-pereira Jan 7, 2026 •

edited

Loading

Uh oh!

brandon-pereira Jan 7, 2026

Uh oh!

brandon-pereira Jan 7, 2026

Uh oh!

alok87 Jan 8, 2026

Uh oh!

elizabetdev Jan 8, 2026

Uh oh!

vercel bot commented Jan 8, 2026 •

edited

Loading

Uh oh!

brandon-pereira Jan 8, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants


		### Patch Changes

		- feat: Add ability to disable data sources (fixes #1545) - Added 'disabled' field to Source model for toggling source visibility

feat: Add ability to disable data sources #1567

Are you sure you want to change the base?

feat: Add ability to disable data sources #1567

Uh oh!

Conversation

alok87 commented Jan 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Changes

Backend

Frontend - Schema & Types

Frontend - UI Components

Sources Management Page

Source Filtering

User Experience

Use Cases

Testing

Backward Compatibility

Changelog

Uh oh!

changeset-bot bot commented Jan 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🦋 Changeset detected

Uh oh!

vercel bot commented Jan 7, 2026

Uh oh!

brandon-pereira Jan 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

brandon-pereira Jan 7, 2026

Choose a reason for hiding this comment

Uh oh!

brandon-pereira Jan 7, 2026

Choose a reason for hiding this comment

Uh oh!

alok87 Jan 8, 2026

Choose a reason for hiding this comment

Uh oh!

elizabetdev Jan 8, 2026

Choose a reason for hiding this comment

Uh oh!

vercel bot commented Jan 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

brandon-pereira Jan 8, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

alok87 commented Jan 7, 2026 •

edited

Loading

changeset-bot bot commented Jan 7, 2026 •

edited

Loading

brandon-pereira Jan 7, 2026 •

edited

Loading

vercel bot commented Jan 8, 2026 •

edited

Loading