FE & BE: Incidents for other monitor types

[ajhollid]

Current behavior: The "Incidents" table only displays incidents for regular Uptime monitors. If a monitor of another type is selected no incidents are shown.

Expected behavior: The "Incidents" table should show incidents for all types of monitors. If a monitor of another type is selected incidents for that monitor should be shown.

[jasneetsingh6114]

Hello, I’d like to work on this issue. Could you please assign it to me?

[ajhollid]

Hi @jasneetsingh6114,

This issue requires a well thought out approach, if you'd like to work on it please post a brief proposal and we'll see if it fits the project goals.

Thanks!

[Owaiseimdad]

@ajhollid , could you please share a screenshot of the current behavior? I'm having trouble understanding the issue.

[ajhollid]

@Owaiseimdad there are four types of monitors, uptime, hardware, PageSpeed, and distributed.

The page currently only shows incidents for Uptime type monitors.

You can test this by creating different monitor and types.

[Owaiseimdad]

Thanks for the brief here @ajhollid.
I get that there are four types of monitoring here, uptime, infrastructure, page-speed and distributed (you need to enable it)

Now, its shows only monitor and and from looking at the code and UI it looks like they had only uptime in mind and we definitely need to add more.

[jasneetsingh6114]

I'd love to work on this issue! My approach includes updating the incidents page (src/Pages/Incidents/index.jsx) to ensure it displays incidents for all four monitor types (Uptime, Hardware, PageSpeed, and Distributed). I'll review API calls in NetworkService.js to fetch incidents for all monitor types, check filtering logic in monitorUtils.js, update the table component if needed, and verify state management in store.js. I’ll also test by creating different monitor types to ensure full coverage. Let me know if this approach aligns with the project goals!

[Br0wnHammer]

Hi @gorkem-bwl,
Could you please assign this issue to me? I've discussed an approach with Alex, and it seems to be on the right track.

[Owaiseimdad]

@Br0wnHammer I do see an api which is getting called and has all the data we might need.
The path contains /api/v1/monitors/team and response data has all the type.
Let me know if this helps.

[Br0wnHammer]

@Owaiseimdad Thanks for the info! I'll test out the /api/v1/monitors/team endpoint as well to see how it fits into our requirements. Let's see how it goes!

[Br0wnHammer]

Hey @gorkem-bwl, we can close out this issue.