ZO-3967: Consolidate importer metrics with label content=news, video, podcast, tts
#618
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Was erledigt dieser PR?
Wir wollen getrennte Alarme schreiben können dafür, wieviele Podcasts und wieviele TTS typischerweise laufend veröffentlicht werden, damit wir mitbekommen, falls eins davon stark sinkt. Dazu wird die Metrik
recent_audios
umgewandelt inrecent_content{content="podcast|tts|etc"}
(und nebenbei gleich noch der richtige Zeitstempellast_published
stattlast_modified
verwewendet).postdeploy
Wenn das nach Production deployed ist, muss man https://github.com/ZeitOnline/vm-prometheus-deployment/blob/main/deployments/kustomize/rules/vivi.rules.yaml anpassen:
Und wenn wir dann verlässliche Zahlen aus Production haben, wieviele Podcasts bzw TTS jeweils so durchlaufen, können wir dafür dann auch Alarm-Regeln schreiben.