You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some things to sort out for local docker compose start up and Helm deployments.
1. Promtail container startup error, local
After running docker compose -f docker-compose.logs.yml -f docker-compose.yml up scripts-promtail-1 fails to start with:
2025-01-20 15:40:13 level=error ts=2025-01-20T23:40:13.765806511Z caller=main.go:170
msg="error creating promtail" error="failed to make journal target manager: creating journal reader: failed to open journal in directory \"/var/log/journal\":
no such file or directory"
2. Helm chart setup for infrastructure
Need to set up necessary Loki streaming infra and config in a way that it can deploy and update to our environments.
Ideally would be stood up for pull request environments as well but might not be worth it if complicated.
3. Parameterize log filter
In log-stream.ts it references:
Loki logging can be optionally enabled, see details here
https://github.com/bcgov/traction/tree/main/scripts#optional-local-log-streaming-setup
Some things to sort out for local docker compose start up and Helm deployments.
1. Promtail container startup error, local
After running
docker compose -f docker-compose.logs.yml -f docker-compose.yml up
scripts-promtail-1
fails to start with:2. Helm chart setup for infrastructure
Need to set up necessary Loki streaming infra and config in a way that it can deploy and update to our environments.
Ideally would be stood up for pull request environments as well but might not be worth it if complicated.
3. Parameterize log filter
In
log-stream.ts
it references:Think that hard coded container name is specific to local docker standup.
4. Error handling
If anything goes wrong starting the log stream there's no feedback to the frontend, or anything logged in the Node app.
The text was updated successfully, but these errors were encountered: