Skip to content

Conversation

@santoshp210-akamai
Copy link
Contributor

@santoshp210-akamai santoshp210-akamai commented Jan 19, 2026

Description 📝

Covers the Associated Alerts section of the Notification Channel Show Details Page

Changes 🔄

List any change(s) relevant to the reviewer.

  • Add a new type, API request, hook to fetch the all the alerts associated with a channel
  • Add a Table component with Error, Loading states for the Associated Alerts
  • Relevant mocks and UTs

Scope 🚢

Upon production release, changes in this PR will be visible to:

  • All customers
  • Some customers (e.g. in Beta or Limited Availability)
  • No customers / Not applicable

Target release date 🗓️

28th Jan

Preview 📷

Include a screenshot <img src="" /> or video <video src="" /> of the change.

🔒 Use the Mask Sensitive Data setting for security.

💡 For changes requiring multiple steps to validate, prefer a video for clarity.

FIGMA

image

localhost

image

No alert case

image

How to test 🧪

Prerequisites

(How to setup test environment)

  • In Mock environment (Legacy MSW Handlers)
  • Enable the the notificationChannels in CloudPulse Alerting (aclpAlerting) to enable the mock feature flags
  • Under Monitor, click on Alerts. Click on the NotificationChannel Tab
  • In the list of Notification Channel, click on the Hyperlink-ed label , or go to the action item menu and choose show details

Reproduction steps

(How to reproduce the issue, if applicable)

  • ...
  • ...

Verification steps

(How to verify changes)

  • The Associated Alerts Table component renders the API data properly
  • Zero alerts case
  • Clicking on the Alert name redirects to that alert's show-details
Author Checklists

As an Author, to speed up the review process, I considered 🤔

👀 Doing a self review
❔ Our contribution guidelines
🤏 Splitting feature into small PRs
➕ Adding a changeset
🧪 Providing/improving test coverage
🔐 Removing all sensitive information from the code and PR description
🚩 Using a feature flag to protect the release
👣 Providing comprehensive reproduction steps
📑 Providing or updating our documentation
🕛 Scheduling a pair reviewing session
📱 Providing mobile support
♿ Providing accessibility support


  • I have read and considered all applicable items listed above.

As an Author, before moving this PR from Draft to Open, I confirmed ✅

  • All tests and CI checks are passing
  • TypeScript compilation succeeded without errors
  • Code passes all linting rules

data-qa-alert-link
to={`/alerts/definitions/detail/${service_type}/${id}`}
>
{label}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hope we are fine displaying the label with whatever case we are receiving and no need to convert to some custom cases?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, Alert labels should not be transformed or converted in any other way.

"@linode/api-v4": Upcoming Features
---

New type, request to fetch alerts associated to a notification channel ([#13294](https://github.com/linode/manager/pull/13294))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
New type, request to fetch alerts associated to a notification channel ([#13294](https://github.com/linode/manager/pull/13294))
New type `NotificationChannelAlerts`, request `getAlertsByNotificationChannelId` to fetch alerts associated to a notification channel ([#13294](https://github.com/linode/manager/pull/13294))

Copy link
Contributor

@venkymano-akamai venkymano-akamai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved pending changeset change

@github-project-automation github-project-automation bot moved this from Review to Approved in Cloud Manager Jan 20, 2026
@linode-gh-bot
Copy link
Collaborator

Cloud Manager UI test results

🔺 2 failing tests on test run #6 ↗︎

❌ Failing✅ Passing↪️ Skipped🕐 Duration
2 Failing863 Passing11 Skipped39m 23s

Details

Failing Tests
SpecTest
clone-linode.spec.tsCloud Manager Cypress Tests→clone linode » can clone a Linode from Linode details page
search-images.spec.tsCloud Manager Cypress Tests→Search Images » creates two images and make sure they show up in the table and are searchable

Troubleshooting

Use this command to re-run the failing tests:

pnpm cy:run -s "cypress/e2e/core/linodes/clone-linode.spec.ts,cypress/e2e/core/images/search-images.spec.ts"

@santoshp210-akamai
Copy link
Contributor Author

Failing tests are not related to the PR changes. Merging the PR.

@santoshp210-akamai santoshp210-akamai merged commit 9219e31 into linode:develop Jan 21, 2026
34 of 35 checks passed
@github-project-automation github-project-automation bot moved this from Approved to Merged in Cloud Manager Jan 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Merged

Development

Successfully merging this pull request may close these issues.

4 participants