[jira] [Commented] (AIRAVATA-3958) A Central Admin Dashboard to Inspect Health + Logs of Airavata Services

["Rahul Kumar (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AIRAVATA-3958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17934246#comment-17934246 ] 

Rahul Kumar commented on AIRAVATA-3958:
---------------------------------------

Hi, I am Rahul Kumar. I am a regular contributor at [https://github.com/javapathfinder/jpf-core] (The Java Path Finder). I have a strong knowledge of Java. I am interested in contributing to this issue. I was exploring the documentation for AIRAVATA. But there was no much information fom development context. It might be that I haven't found correct one. 

 

Kindly guide me! From where should I start to understand the AIRAVATA.

> A Central Admin Dashboard to Inspect Health + Logs of Airavata Services
> -----------------------------------------------------------------------
>
>                 Key: AIRAVATA-3958
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-3958
>             Project: Airavata
>          Issue Type: New Feature
>            Reporter: Yasith Jayawardana
>            Priority: Major
>              Labels: gsoc, gsoc2025, mentor
>
> Develop a devops dashboard to monitor Apache Airavata services, enabling real-time tracking of service health, uptime, and logs independent of the science gateway(s).
> This centralized tool will help administrators efficiently monitor service performance and troubleshoot issues. The dashboard will feature a user-friendly monitoring UI that displays real-time status updates and logs for each service.
> Proposed Solution:
> * A logging subproces alongside each service, pushing logs to an external service.
> * A devops dashboard that aggregates the logs and provides a unified view into the system.
> * API calls from devops dashboard to each service, for proactive health-checking.
> * Ability to monitor multiple gateways from the same dashboard.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)