[
https://issues.apache.org/jira/browse/AIRAVATA-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15532680#comment-15532680
]
ASF subversion and git services commented on AIRAVATA-2065:
-----------------------------------------------------------
Commit 342400cf310a8cd9d3350751f31e6895e4ecf603 in airavata's branch
refs/heads/lahiru/AIRAVATA-2065 from Lahiru Ginnaliya Gamathige
[ https://git-wip-us.apache.org/repos/asf?p=airavata.git;h=342400c ]
[AIRAVATA-2065] Introduce more robust logging mechanism for Airavata
Summary:
1. Add configurable KafkaAppender (default turned off) which will push
the airavata logs to kafka topic.
2. Use configured kafka topic prefix and construct the topic name based on
the airavata role running.
3. Bring back logback as the logging library.
4. Use git describe in the server version string and introduce new serverId
with more metadata.
5. Added new class to handle specifically AWS deployment (use aws-metadata
service).
6. Add MDC context to orchestrator and gfac thread executions.
Test Plan: Deployed a Airavata setup in AWS with ES cluster and tested the logs.
Reviewers: supun, ajinkya, suresh
Differential Revision: https://airavata.exana.io/D2
> Introduce more robust logging mechanism for Airavata
> ----------------------------------------------------
>
> Key: AIRAVATA-2065
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2065
> Project: Airavata
> Issue Type: Story
> Reporter: Lahiru Gunathilake
> Assignee: Lahiru Gunathilake
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
