[
https://issues.apache.org/jira/browse/AIRAVATA-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15519092#comment-15519092
]
ASF subversion and git services commented on AIRAVATA-2065:
-----------------------------------------------------------
Commit f7f1f9c093ed66de182c72d9618ac9561a28e5fe 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=f7f1f9c ]
[AIRAVATA-2065] Introduce more robust logging mechanism for Airavata
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.
> 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)
