StackStorm / StackStorm/st2

Can't see my pack actions logs in any pod

Open
#5,504 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

stale
Dominant language
Python
Stars
6.5k
Forks
787
PR merge metrics
No merged PRs in 30d

Description

I was trying to look if I can find my custom action logs in one of K8s pods.
But couldn't find them.
My logs looks as in the docs:
https://docs.stackstorm.com/actions.html#logging

Assuming they should have been in: st2actionrunner pod

I use the logger that in:
https://github.com/StackStorm/st2/blob/master/st2common/st2common/runners/base_action.py#L54
Although I see that actionrunner logger location is in:
https://github.com/StackStorm/st2/blob/master/st2actions/st2actions/container/base.py#L44

Anyway to connect my actions logger so I can see my logs in st2actionrunner pod or in some other location\file?
(Or maybe in some other way/location)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the logging section in docs.stackstorm.com/actions.html, then compare the logger in st2common/runners/base_action.py with the actionrunner logger in st2actions/container/base.py. Trace where custom action output is emitted and collected in Kubernetes, using the referenced locations as entry points. Done means the correct log location or connection method is identified and documented, with the behavior verified in an actionrunner pod.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes, python
Domain
devops, observability
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.