> ## Content Index
> Fetch the complete content index at: https://blog.golem.network/llms.txt
> Use this file to discover other available public pages before exploring further.

# Golem GitHub Digest #11: Easy log collection
- URL: https://blog.golem.network/golem-github-digest-11/
- Published: 2021-01-13T15:43:37.000Z
- Updated: 2026-11-07T16:27:46.000Z
- Description: We’ve been thrilled by the community getting involved in the Golem Hackathon and have had so much amazing feedback and overall positivity, both from requestors/buidl`ers participating in the Golem Online Hackathon and providers joining the Provider Bounties.
- Author: Mattias Nystrom
- Tags: community, #Import 2024-04-10 14:10, #Import 2024-10-09 05:23

### What’s in store for this Digest?

In the previous Golem GitHub Digest ([#10](https://blog.golem.network/golem-github-digest-10/)) we covered the [Alpha 3](https://blog.golem.network/new-golem-alpha-iii-reveal/) release and [announcement of the hackathon and Golem Test Harness](https://blog.golem.network/gwebinars-golem-test-harness/) (Goth).

We’ve been thrilled by the community getting involved in the Golem Hackathon and have had so much amazing feedback and overall positivity, both from requestors/*buidl*\`ers participating in the [Golem Online Hackathon](https://blog.golem.network/golem-alpha3-provider-bounties/) and providers joining the [Provider Bounties](https://blog.golem.network/golem-alpha3-provider-bounties/).

### So, what’s in the Golem GitHub?

The team added a feature for [logging collection](https://github.com/golemfactory/yagna/pull/895?ref=blog.golem.network) to an output file by default, utilizing Flexi\_Logger. You’ll be able to save the logging information in a desired directory by running the command `yagna service run --log-dir YOUR_DIRECTORY`. To change the log dir, while using `golemsp run` it's necessary to use the `YAGNA_LOG_DIR` environment variable instead. Prior to this, users that wanted to collect logs of stdout/stderr had to do so manually using commands such as d `yagna service run -2>&1 | tee -a logfile.log`. Just as a note, you can still collect more detailed logs using this command: 

`RUST_LOG=debug,tokio_core=info,tokio_reactor=info,hyper=info golemsp run 2>&1 | tee -a logfile.log`

Although be warned that the output file will get large quite quickly so it’s not for the average user!

There was a significant collaboration between developers on the [Event API](https://github.com/golemfactory/ya-client/pull/89?ref=blog.golem.network) in the Yagna client across a few months that was ready to be merged into the master branch. If you're interested to go into a lower level overview of some of the Yagna Client API specs, you can do so [here](https://github.com/golemfactory/ya-client/tree/master/specs?ref=blog.golem.network)!

Other than that, improvement mentioned in the previous GitHub update containing some important bug fixes for long computations while using [YaJSapi](https://github.com/golemfactory/yajsapi?ref=blog.golem.network), handling HTTP 408 errors and decreasing API timeouts and sleep duration to fix ECONNRESET error, [has been merged](https://github.com/golemfactory/yajsapi/pull/90?ref=blog.golem.network). There are many more minor improvements that have been made across almost all repositories.

### Coming up

The team pushes to get the Yagna code and APIs to be ready for mainnet. While we can still expect a release to come out on testnet before that stage, it won’t be long before we hope to see a release that we deem mainnet ready! The judging of the Golem Online Hackathon is almost finished. After we announce the winners we’ll be updating [Awesome Golem](https://github.com/golemfactory/awesome-golem?ref=blog.golem.network) with all the interesting submissions/projects.

### Digest wrap-up!

That’s everything we have for you in GitHub Digest #11\. Don’t forget that the [Golem Community Incentives Program](https://blog.golem.network/community-incentives-program) is still running! We recently announced the [awardees of December](https://blog.golem.network/community-incentives-program-cip-december-update/), if you happen to be Clay Golem node name “Zootopia” then please get in contact with us so we can verify. To get involved in the CIP join our [Discord chat](https://chat.golem.network/?ref=blog.golem.network), get involved on [Reddit](http://reddit.com/r/GolemProject?ref=blog.golem.network), tag us in interesting conversations on [Twitter](https://twitter.com/?ref=blog.golem.network), or even throw some memes in [Telegram](https://t.me/GolemProject?ref=blog.golem.network). 

See you in the next GitHub Digest!