Provide generic documentation on how to publish logs in to centralized external system such as Elastic search.
Open
Nobody has claimed this yet.
API-M-3.2.0
API-M-4.0.0
Type/Bug
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
Description:
Publishing logs in to centralized external system such as Elastic search can be done in an approach as follows.
- Configure fluentd sidecar with WSO2 main container
- Configure fluentd to publish logs to Elastic Search for each WSO2 log file
Need to document a generic approach for such requirements.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. Start by locating the documentation area covering WSO2 logging or deployment, then use the proposed Fluentd sidecar flow and Elasticsearch destination as the scope. Done means a generic guide explains configuring Fluentd with the WSO2 container and publishing each WSO2 log file to Elasticsearch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch
- Domain
- documentation, observability
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100