Packit-service: Better logs

[lachmanfrantisek]

Since we are publishing the debug logs in the packit-service (e.g. https://stg.packit.dev/copr-build/19/logs), we need to think about them more now.

• format of the log output
• content of the logs (consistency, what/when to log, what is debug/info/warning/...)

Related to https://github.com/packit-service/packit/issues/719

[lachmanfrantisek]

Can we somehow turn off these type of messages in worker? It's very messy because of them.

[2020-03-11 12:52:09,770: DEBUG/MainProcess] pidbox received method enable_events() [reply_to:None ticket:None]

[2020-03-11 12:52:40,459: DEBUG/MainProcess] pidbox received method ping() [reply_to:{'exchange': 'reply.celery.pidbox', 'routing_key': '6cb53494-3364-3f98-a2dc-eeb5bf039860'} ticket:3436c9ac-44ef-4c94-b44b-9a8094e7838a]

[jpopelka]

Hmm, they should have already been turned off.

Something's wrong with
https://github.com/packit-service/packit-service/blob/master/files/run_worker.sh#L10

[lachmanfrantisek]

Hmm, they should have already been turned off.

OK, it's from stage... Do we need them on stage?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
Thank you for your contributions.
We are doing this to be sure that the issue is still relevant. Anyone can comment to remove the stale state. (The issues marked with pinned, security, bug or EPIC label
are not considered stale.)

[lachmanfrantisek]

@lbarcziova Can we consider this as fixed or is your PR just a part of it?

[lbarcziova]

@lachmanfrantisek my PR was mainly focusing on the format, so it is just the first point.

[stale[bot]]

This issue has been marked as stale because it hasn't seen any
activity for the last 60 days.

Stale issues are closed after 14 days, unless the label is removed
by a maintainer or someone comments on it.

This is done in order to ensure that open issues are still relevant.

Thank you for your contribution! :unicorn: :rocket: :robot:

(Note: issues labeled with pinned, security, bug or EPIC are
never marked as stale.)

[stale[bot]]

This issue has been marked as stale because it hasn't seen any
activity for the last 60 days.

Stale issues are closed after 14 days, unless the label is removed
by a maintainer or someone comments on it.

This is done in order to ensure that open issues are still relevant.

Thank you for your contribution! :unicorn: :rocket: :robot:

(Note: issues labeled with pinned, security, bug or EPIC are
never marked as stale.)

[stale[bot]]

This issue has been marked as stale because it hasn't seen any
activity for the last 60 days.

Stale issues are closed after 14 days, unless the label is removed
by a maintainer or someone comments on it.

This is done in order to ensure that open issues are still relevant.

Thank you for your contribution! :unicorn: :rocket: :robot:

(Note: issues labeled with pinned or EPIC are
never marked as stale.)

[lachmanfrantisek]

Anything more specific we can do here?

Do you think it's still valid?

[TomasTomecek]

I'd say the best solution here is to start utilizing the dashboard (and ideally get rid of the build result page); I propose to close it