#13030 - Fedora docs - daily email - infra/tickets

jibecfed commented

2026-01-11 10:10:58 +00:00

Hi team,

I receive everyday an email from Fedora documentation automation:

To: jibecfed@fedoraproject.org
From: noreply@fedoraproject.org
Subject: [docstranslation] error log
Message-Id: 20260110221236.4E6607765C@bastion01.rdu3.fedoraproject.org

Content looks like this: https://paste.yunohost.org/raw/enepapebor

can we have this is a shared log somewhere and document where to find this log in the following repositories?
https://pagure.io/fedora-docs/translations-scripts/
https://gitlab.com/fedora/docs/docs-website/docs-fp-o

ideally, having errors sent to #l10n:fedoraproject.org could be useful

Example of "errors":
fatal: repository 'https://pagure.io/fedora-docs-l10n/community-participate/' not found
it means a localization repository needs to be created for the community to be able to translate

Hi team, I receive everyday an email from Fedora documentation automation: To: jibecfed@fedoraproject.org From: noreply@fedoraproject.org Subject: [docstranslation] error log Message-Id: <20260110221236.4E6607765C@bastion01.rdu3.fedoraproject.org> Content looks like this: https://paste.yunohost.org/raw/enepapebor can we have this is a shared log somewhere and document where to find this log in the following repositories? https://pagure.io/fedora-docs/translations-scripts/ https://gitlab.com/fedora/docs/docs-website/docs-fp-o ideally, having errors sent to #l10n:fedoraproject.org could be useful Example of "errors": fatal: repository 'https://pagure.io/fedora-docs-l10n/community-participate/' not found it means a localization repository needs to be created for the community to be able to translate

zlopez commented

2026-01-12 09:38:03 +00:00

Owner

Metadata Update from @zlopez:

Issue priority set to: Waiting on Assignee (was: Needs Review)
Issue tagged with: low-trouble, medium-gain, ops

**Metadata Update from @zlopez**: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-trouble, medium-gain, ops

zlopez commented

2026-01-12 09:39:01 +00:00

Owner

Would it be a viable option to send the e-mail to some mailing list of your choice?

jflory7 commented

2026-01-12 15:14:41 +00:00

Member

Is there any way we could use something like Zabbix to get alerting for these errors? One challenge is that the pool of people who are both capable of working on this and informed enough to work on these challenges is very low. We should consider more ways to get added visibility into the localization stack in Fedora Infrastructure.

jflory7 commented

2026-01-12 15:15:20 +00:00

Member

Also, if Zabbix could help with making a Matrix bot that alerts in a specific Matrix room when there are issues, e.g. #localization:fedoraproject.org, that would be very helpful too.

Also, if Zabbix could help with making a Matrix bot that alerts in a specific Matrix room when there are issues, e.g. `#localization:fedoraproject.org`, that would be very helpful too.

zlopez commented

2026-01-13 12:08:42 +00:00

Owner

zabbix is open to check for everyone, but these are logs from cron jobs and we don't want to have them saved them in zabbix.

jibecfed commented

2026-01-19 20:07:14 +00:00

Author

ok then, what would be the required steps to have those logs on zabbix?
if cron jobs are not suitable, what would be?

ok then, what would be the required steps to have those logs on zabbix? if cron jobs are not suitable, what would be?

kevin commented

2026-01-20 00:50:05 +00:00

Owner

Well, I am not sure. zabbix is a monitoring system, so it runs a check and acts on the output of that check.

I suppose if the logs were stored somewhere it could run a check over them and alert if errors were found.

@gwmngilfen any ideas here?

Well, I am not sure. zabbix is a monitoring system, so it runs a check and acts on the output of that check. I suppose if the logs were stored somewhere it could run a check over them and alert if errors were found. @gwmngilfen any ideas here?

gwmngilfen commented

2026-01-20 11:13:00 +00:00

Member

So, yes, Zabbix could help here.

The cron jobs could be updated to send a result to Zabbix (pass/fail, or even more complex data) using the Zabbix agent or zabbix_sender
We can set Zabbix up to act on that, and send alerts to a Matrix room
- The setup for that is a little fiddly, but it can be Ansibilised once we're happy with it.
- The main challenge would be not reporting that event in #noc, if we're happy to have it reporting in both then this gets a lot simpler
However, looking at the length of that output, I don't think we want to be storing it in the Zabbix DB, so you'd want the check to make it clear who/what needs to act on it.

I can help with the Zabbix-side stuff for sure - but the first step would be modifying the cron jobs to output something useful to Zabbix. Then we either:

Put that output in a file and tell the Zabbix agent to read it, or
Add the Zabbix call to the end of the cronjob - but that would mean ensuring that it does run, with error handling, etc

I lean to the first option - lets have the cron dump output to /var/log or similar, and and then we write a new script that checks both the output and the timestamp - if the file is too old, or has bad content, we send a warning.

How does that feel?

So, yes, Zabbix *could* help here. - The cron jobs could be updated to send a result to Zabbix (pass/fail, or even more complex data) using the Zabbix agent or `zabbix_sender` - We can set Zabbix up to act on that, and send alerts to a Matrix room - The setup for that is a little fiddly, but it can be Ansibilised once we're happy with it. - The main challenge would be *not* reporting that event in #noc, if we're happy to have it reporting in both then this gets a lot simpler - However, looking at the length of that output, I don't think we want to be storing it in the Zabbix DB, so you'd want the check to make it clear who/what needs to act on it. I can help with the Zabbix-side stuff for sure - but the first step would be modifying the cron jobs to output something useful to Zabbix. Then we either: - Put that output in a file and tell the Zabbix agent to read it, or - Add the Zabbix call to the end of the cronjob - but that would mean ensuring that it *does* run, with error handling, etc I lean to the first option - lets have the cron dump output to /var/log or similar, and and then we write a new script that checks both the output and the timestamp - if the file is too old, or has bad content, we send a warning. How does that feel?

jibecfed commented

2026-02-27 18:49:49 +00:00

Author

Hi @gwmngilfen , who are you asking the question to?
We are now having a few contributors involved ad localization team admin, having the log available somewhere would be most welcome
The Matrix notification would be a nice to have feature, but first priority would be to stop having only me receiving the log.
If I may help here, please tell me (I'll be honest with my technical ability to do it)
thanks a lot for your help

Hi @gwmngilfen , who are you asking the question to? We are now having a few contributors involved ad localization team admin, having the log available somewhere would be most welcome The Matrix notification would be a nice to have feature, but first priority would be to stop having only me receiving the log. If I may help here, please tell me (I'll be honest with my technical ability to do it) thanks a lot for your help

jibecfed referenced this issue

2026-02-27 22:04:14 +00:00

sundries change to use forgejo instead of Pagure #13171

gwmngilfen commented

2026-03-02 11:20:38 +00:00

Member

Good question about who I'm questioning :)

I think I'm mostly asking @kevin & @zlopez - although your input is welcome too. And it's possible that I don't understand the full details of the concerns. What I'm hearing is:

There's a cronjob that runs, but we don't want to store/share the raw log of that - why not? is it sensitive, or just large?
That log goes to you @jibecfed right now, but you'd rather something went to the wider community - in the Matrix room was suggested, but are there other options?

I can think of possible actions, but it depends on the answers to these questions.

Good question about who I'm questioning :) I think I'm mostly asking @kevin & @zlopez - although your input is welcome too. And it's possible that I don't understand the full details of the concerns. What I'm hearing is: - There's a cronjob that runs, but we don't want to store/share the raw log of that - why not? is it sensitive, or just large? - That log goes to you @jibecfed right now, but you'd rather something went to the wider community - in the Matrix room was suggested, but are there other options? I can think of possible actions, but it depends on the answers to these questions.

zlopez commented

2026-03-02 14:00:54 +00:00

Owner

@jibecfed What about sending the log to fedorapeople.org instead of your own mail and you can give the link to it to anyone? For example I'm sharing weekly standup summaries for CLE Team that way (see https://zlopez.fedorapeople.org/).

gwmngilfen commented

2026-05-28 15:53:12 +00:00

Member

Coming back to this, the email is currently disabled: infra/ansible#3262

So I guess the question is - do you want it back at all @jibecfed? and if so, do any of the options above make sense?

Coming back to this, the email is currently disabled: https://forge.fedoraproject.org/infra/ansible/pulls/3262 So I guess the question is - do you want it back at all @jibecfed? and if so, do any of the options above make sense?

jibecfed commented

2026-07-01 06:16:59 +00:00

Author

hi there, for info: @darknao enabled the cron a few days (weeks?) ago and the publication restarted, and the email logs too...

sending it to the matrix room is not fine for me since it is a log and not an alert, it will spam us

we need to be able to access the last X execution to find when an issue appeared (would a month be doable?)

using fedorapeople or other is fine, as long as the Fedora Localization Admins (@rffontelle, @peartown and myself) and a few infra people (likely darknao?) have access to the logs

hi there, for info: @darknao enabled the cron a few days (weeks?) ago and the publication restarted, and the email logs too... sending it to the matrix room is not fine for me since it is a log and not an alert, it will spam us we need to be able to access the last X execution to find when an issue appeared (would a month be doable?) using fedorapeople or other is fine, as long as the Fedora Localization Admins (@rffontelle, @peartown and myself) and a few infra people (likely darknao?) have access to the logs

kevin commented

2026-07-01 21:56:38 +00:00

Owner

For release engineering things like this we have a mailing list... releng-cron. All the output goes there and you can subscribe if you want it, or just look at the archives when you are debugging a failure.

would something like that work for this?

For release engineering things like this we have a mailing list... releng-cron. All the output goes there and you can subscribe if you want it, or just look at the archives when you are debugging a failure. would something like that work for this?

Rows
Columns

Fedora docs - daily email #13030