I have never heard of individual velocity measurements, they are wrong and should not be measured. I also think that burndown charts and velocity are for the team, not the stakeholders. This is because story point estimation is volatile and turning it into a feedback loop would turn this estimation into a meaningless thing.
Thus, there is room for transparency with the stakeholders in the sprint review and the setup, all else should be in the team's responsibility.
Scrum guides are usually very specific about the fact that the daily scrum is not for reporting.
Devops work should be priced in as a story in the sprint. If the Product Owner does not want to give such a story the proper priority, you should transparently explain how lack of such work will decrease sprint velocity in future sprints.
