nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

redirecting JIRA logs to STDOUT

Yuval Zaltz

We plan to run JIRA over kubernetes - typically containers in kubernetes write to STDOUT from there the data is captured and sent to log solution like elastic search.
especially as container may crush and data can be lost.

JIRA and JVM container save STDOUT and STDERR to log files

So is it passable to redirect logs to STDOUT?

Accepted answers

Yuval Zaltz

Found a workaround solution using kubernetes "sidecar" - see here https://kubernetes.io/docs/concepts/cluster-administration/logging/#using-a-sidecar-container-with-the-logging-agent

basically it's a daemon container on the same pod that prints out a specific log file tail

All comments

Earl McCutcheon

Hello @Yuval Zaltz ,

We have the following Knowledge base article detailing the steps on how to change the default logging locations, check it out and let me know how it goes:

How to change the location of stdout and stderr logs

Regards,
Earl

Yuval Zaltz

Thanks - My instance is on Kubernetes and using Atlassian Docker (Ubuntu based i believe).

So this does not apply

Yuval Zaltz

Found a workaround solution using kubernetes "sidecar" - see here https://kubernetes.io/docs/concepts/cluster-administration/logging/#using-a-sidecar-container-with-the-logging-agent

basically it's a daemon container on the same pod that prints out a specific log file tail

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server