Skip to content

upcoming: [DI-29907] - Logs service Alerts Integration#13445

Open
santoshp210-akamai wants to merge 4 commits intolinode:developfrom
santoshp210-akamai:feature/alerts-logs-integration
Open

upcoming: [DI-29907] - Logs service Alerts Integration#13445
santoshp210-akamai wants to merge 4 commits intolinode:developfrom
santoshp210-akamai:feature/alerts-logs-integration

Conversation

@santoshp210-akamai
Copy link
Contributor

@santoshp210-akamai santoshp210-akamai commented Feb 27, 2026

Description 📝

ACLP Logs service integration for Alerts

Changes 🔄

List any change(s) relevant to the reviewer.

  • Add the logs fetch all query to the resources.ts
  • Add Logs to the capability, type mappings
  • Add status_code dimension filter placeholder, helper and error texts
  • Add status_code dimension filter value schema

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 🗓️

Please specify a release date (and environment, if applicable) to guarantee timely review of this PR. If exact date is not known, please approximate and update it as needed.

Preview 📷

Create flow

alert-logs-integration.mp4

Show-details flow

image

How to test 🧪

Prerequisites

(How to setup test environment)

  • In Mock environment, please enable the logs service type for alerts with beta in the ACLP Services feature flag
image
  • Under Monitor, click on Alerts.
  • Create Flow: Click on Create Alert and choose Logs to verify
  • Show Details Flow: In the Alert Definitions, search for an Alert Logs-alert , click on the Alert label link or the Action menu and choose Show Details
  • Edit Flow: In the Alert Definitions, search for an Alert Logs-alert , click on the Action menu and choose Edit

Verification steps

(How to verify changes)

  • Able to create an Alert with logs service
  • Able to properly see the details rendered in the Show-details
  • Able to edit the logs Alert
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

Boolean(
serviceType && (serviceType === 'firewall' || supportedRegionIds?.length)
serviceType &&
(serviceType === 'firewall' ||
Copy link
Contributor

Choose a reason for hiding this comment

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

@santoshp210-akamai . some linting issue that may be fixed??

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.

LGTM, check some eslint warnings

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Review

Development

Successfully merging this pull request may close these issues.

2 participants