-
Notifications
You must be signed in to change notification settings - Fork 158
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
docs: Document using actionset labels to extend logs (#2981)
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
- Loading branch information
1 parent
8b5c9b0
commit 62de235
Showing
5 changed files
with
53 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -7,5 +7,6 @@ Tasks | |
|
||
tasks/argo.rst | ||
tasks/logs_level.rst | ||
tasks/logs_labels.rst | ||
tasks/logs.rst | ||
tasks/scaleworkload.rst |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
Configuring logs for specific ActionSets | ||
---------------------------------------- | ||
|
||
Kanister uses structured logging to ensure that its logs can be easily | ||
categorized, indexed and searched by downstream log aggregation software. | ||
|
||
Extra fields can be added to the logs related to a specific ActionSet by adding | ||
a label in the ActionSet with ``kanister.io`` prefix. | ||
|
||
For example: | ||
|
||
.. code-block:: yaml | ||
:linenos: | ||
apiVersion: cr.kanister.io/v1alpha1 | ||
kind: ActionSet | ||
metadata: | ||
namespace: kanister | ||
name: myActionSet | ||
labels: | ||
kanister.io/myFieldName: myFieldValue | ||
All logs concerning this ActionSet execution will have | ||
``myFieldName`` field with ``myFieldValue`` value. | ||
|
||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
# Configuring logs for specific ActionSets | ||
|
||
Kanister uses structured logging to ensure that its logs can be easily | ||
categorized, indexed and searched by downstream log aggregation software. | ||
|
||
Extra fields can be added to the logs related to a specific ActionSet by adding | ||
a label in the ActionSet with `kanister.io` prefix. | ||
|
||
For example: | ||
|
||
``` yaml | ||
apiVersion: cr.kanister.io/v1alpha1 | ||
kind: ActionSet | ||
metadata: | ||
namespace: kanister | ||
name: myActionSet | ||
labels: | ||
kanister.io/myFieldName: myFieldValue | ||
|
||
``` | ||
|
||
All logs concerning this ActionSet execution will have | ||
`myFieldName` field with `myFieldValue` value. |