kyma-project
Add short tutorial on how to use unified logging library
Description
Add a short tutorial (for example kyma/common/logging/README.md) on how to use the logging library. Main features should be described and examples of the usage should be provided. We may also want to link the Application Connectivity Validator as it's the first exemplary migrated component (after the merge of this PR)
The tutorial should not be merged before this PR as it is the library implementation
Area
- Common library
- Logging
Reasons
The logging library is implemented in a way that every component should be able to use it. Therefore everyone should be able to easily get to know it
Assignees
@kyma-project/technical-writers @dbadura (library owner) @franpog859 (library owner)
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.
![kyma-stale-bot[bot] avatar](https://avatars.githubusercontent.com/u/39153523?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed due to the lack of recent activity.
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue or PR has been automatically marked as stale due to the lack of recent activity. Thank you for your contributions.
This bot triages issues and PRs according to the following rules:
- After 60d of inactivity,
lifecycle/staleis applied - After 7d of inactivity since
lifecycle/stalewas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Close this issue or PR with
/close
If you think that I work incorrectly, kindly raise an issue with the problem.
/lifecycle stale
I'm closing this issue as I haven't seen any interest in having such a document. Please, reopen it if needed