You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@airavata.apache.org by "Suresh Marru (JIRA)" <ji...@apache.org> on 2019/04/03 00:38:00 UTC

[jira] [Commented] (AIRAVATA-2999) [GSoC] Administration Dashboard for Airavata Services

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

Suresh Marru commented on AIRAVATA-2999:
----------------------------------------

There are more monitoring instrumentation components which can be integrated, Kamom [https://github.com/kamon-io/Kamon], Zipkin [https://github.com/openzipkin/zipkin] and Datadog - [https://github.com/DataDog/dd-trace-java]

Airavata previously had integrations with some of these - https://issues.apache.org/jira/browse/AIRAVATA-2107 

> [GSoC] Administration Dashboard for Airavata Services
> -----------------------------------------------------
>
>                 Key: AIRAVATA-2999
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2999
>             Project: Airavata
>          Issue Type: New Feature
>            Reporter: Dimuthu Upeksha
>            Priority: Major
>              Labels: gsoc2019
>
> Typical Apache Airavata deployment consists of multiple microservices (API Server, Participant, Controller, Pre Workflow Manager, Post Workflow Manager, Job Monitors and etc) and several other services (Database, Kafka, RabbitMQ, Keycloak, Zookeeper, Apache Helix). As it is a deployment with multiple components, when it comes to an issue,  it is time consuming to find which component is having the problem. So we need an Administration Dashboard which can visualize the system health and provide some handle to administrators to control those services like stopping or restarting each component through the dashboard.
> Additionally, this dashboard should be able to authenticate users through Keycloak which is the identity provider for Airavata and  only system administrators should be given access to those operations.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)