OU-432: Merge Perses dashboards with current dashboards list

[zhuje]

Description

On the dashboard page, list Perses dashboards in the dropdown.
This PR only lists the dashboards in the dropdown; the dashboard is not rendered when you click on the dropdown item.

Figure 1. Perses dashboards are listed in the dashboard page dropdown (e.g., "testproject / dashboard1" and "testproject / dashboard2"). The dashboards are displayed as <"project name"> / <"dashboard name">. The tag, by default, is "perses."

Related Issue

https://issues.redhat.com/browse/OU-432

Testing

This PR was only tested locally during development. To setup the test:

1. Launch a perses container docker run --name perses -d -p 127.0.0.1:8080:8080 persesdev/perses. See https://github.com/perses/perses?tab=readme-ov-file#docker-images for information.
2. Navigate to http://localhost:8080, which will take you to the local Perses instance. Create a project and a dashboard for it.
3. Start the monitoring-plugin (make start-frontend and in a separate terminal make start-console). make start-console is proxying localhost:8080 (our local perses instance).
4. There is a bug in the OCP console that prevents the Dashboard page from fetching the OCP dashboards specs -- to circumvent (with a hack-y solution) I've created a mock API response that serves the specs in this branch which you can merge in to the PR : https://github.com/zhuje/monitoring-plugin/tree/mock_monitoring_dashboard_config.
5. Navigate to http://localhost:9000 (our local OCP instance). Go to Observe > Dashboards > Dropdown, the dashboards you created in the local perses instance should now be listed in the dropdown.

https://github.com/user-attachments/assets/7f6258e8-62de-46dc-8bd1-c7c598d628ea
Figure 2. Video demo of testing (~1:45 minutes). Shows perses dashboards are listed in the Dashboard page dropdown.

[jgbernalp]

As discussed in the tech sync, I don't think we need the proxy here as this will be handled by the proxy created in the ConsolePlugin CR

[openshift-ci-robot]

@zhuje: This pull request references OU-432 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.19.0" version, but no target version was set.

In response to this:

Description

On the dashboard page, list Perses dashboards in the dropdown.
This PR only lists the dashboards in the dropdown; the dashboard is not rendered when you click on the dropdown item.

Figure 1. Perses dashboards are listed in the dashboard page dropdown (e.g., "testproject / dashboard1" and "testproject / dashboard2"). The dashboards are displayed as <"project name"> / <"dashboard name">. The tag, by default, is "perses."

Related Issue

https://issues.redhat.com/browse/OU-432

Testing

This PR was only tested locally during development. To setup the test:

1. Launch a perses container docker run --name perses -d -p 127.0.0.1:8080:8080 persesdev/perses. See https://github.com/perses/perses?tab=readme-ov-file#docker-images for information.
2. Navigate to http://localhost:8080, which will take you to the local Perses instance. Create a project and a dashboard for it.
3. Start the monitoring-plugin (make start-frontend and in a separate terminal make start-console). make start-console is proxying localhost:8080 (our local perses instance).
4. There is a bug in the OCP console that prevents the Dashboard page from fetching the OCP dashboards specs -- to circumvent (with a hack-y solution) I've created a mock API response that serves the specs in this branch which you can merge in to the PR : https://github.com/zhuje/monitoring-plugin/tree/mock_monitoring_dashboard_config.
5. Navigate to http://localhost:9000 (our local OCP instance). Go to Observe > Dashboards > Dropdown, the dashboards you created in the local perses instance should now be listed in the dropdown.

https://github.com/user-attachments/assets/7f6258e8-62de-46dc-8bd1-c7c598d628ea
Figure 2. Demo of testing. Shows perses dashboards are listed in the Dashboard page dropdown.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@zhuje: This pull request references OU-432 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.19.0" version, but no target version was set.

In response to this:

Description

On the dashboard page, list Perses dashboards in the dropdown.
This PR only lists the dashboards in the dropdown; the dashboard is not rendered when you click on the dropdown item.

Figure 1. Perses dashboards are listed in the dashboard page dropdown (e.g., "testproject / dashboard1" and "testproject / dashboard2"). The dashboards are displayed as <"project name"> / <"dashboard name">. The tag, by default, is "perses."

Related Issue

https://issues.redhat.com/browse/OU-432

Testing

This PR was only tested locally during development. To setup the test:

1. Launch a perses container docker run --name perses -d -p 127.0.0.1:8080:8080 persesdev/perses. See https://github.com/perses/perses?tab=readme-ov-file#docker-images for information.
2. Navigate to http://localhost:8080, which will take you to the local Perses instance. Create a project and a dashboard for it.
3. Start the monitoring-plugin (make start-frontend and in a separate terminal make start-console). make start-console is proxying localhost:8080 (our local perses instance).
4. There is a bug in the OCP console that prevents the Dashboard page from fetching the OCP dashboards specs -- to circumvent (with a hack-y solution) I've created a mock API response that serves the specs in this branch which you can merge in to the PR : https://github.com/zhuje/monitoring-plugin/tree/mock_monitoring_dashboard_config.
5. Navigate to http://localhost:9000 (our local OCP instance). Go to Observe > Dashboards > Dropdown, the dashboards you created in the local perses instance should now be listed in the dropdown.

https://github.com/user-attachments/assets/7f6258e8-62de-46dc-8bd1-c7c598d628ea
Figure 2. Video demo of testing (~1:45 minutes). Shows perses dashboards are listed in the Dashboard page dropdown.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[jgbernalp]

cc @fkargbo

[fkargbo]

Looks good to me!

[jgbernalp]

It would be better to leave the perses-client to abstract the perses API as functions. See:
https://github.com/openshift/logging-view-plugin/blob/main/web/src/loki-client.ts

And then build in another file a usePerses hook that consumes this client. This hook should expose functions and probably a state so the consumers can decide when to query or reuse a persistent state.

[zhuje]

I updated the files in the latest push.

1. Added cancellable-fetch.ts ported from logging-view-plugin
2. perses-client.ts modified to follow loki-client.ts from logging-view-plugin
3. usePerses.ts created to follow useLogs.ts from logging-view-plugin
4. ...dashboards/index.ts modified to utilize usePerses() hook

[PeterYurkovich]

/lgtm

[jgbernalp]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jgbernalp, PeterYurkovich, zhuje

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [PeterYurkovich,jgbernalp,zhuje]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@zhuje: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: monitoring-plugin
This PR has been included in build monitoring-plugin-container-v4.19.0-202412092010.p0.g5651a2f.assembly.stream.el9.
All builds following this will include this PR.