Designs for alerts table

[linear]

Attributes:

• Name
• State
• Last state update
• Source
• Channels/emails
• Algo type
• Alert on or off

[linear]

HIG-4623 Designs for alerts table

[greptile-apps]

To implement the designs for an alerts table with the specified attributes, follow these steps:

1. Backend Model Update: Ensure the alert model in /backend/alerts/alerts.go includes fields for Name, State, Last state update, Source, Channels/emails, and Algo type. If any fields are missing, update the model accordingly.

2. GraphQL Schema: Update the GraphQL schema in /backend/private-graph/graph/model/models_gen.go to include the new or updated fields. This ensures that the frontend can query the updated alert data.

3. Frontend Display: Modify the Alerts page component in /frontend/src/pages/Alerts/Alerts.tsx to include a table that displays the specified attributes. Use utility functions from /frontend/src/pages/Alerts/utils if necessary to format data for display.

4. Data Fetching: Ensure the GraphQL queries in the frontend correctly fetch the new or updated fields from the backend.

5. Styling: Update CSS in /frontend/src/pages/Alerts/Alerts.module.css to match the design requirements for the alerts table.

These steps provide a high-level overview. Implementation details will depend on the current codebase structure and the specific requirements for each attribute.

References

/backend/alerts
/backend/private-graph/graph/model
/frontend/src/pages/Alerts

Ask Greptile