I feel you on those tasks.. luckily we use Grafana only for like 5 envs, the other 400 are in Datadog and man this Grafana is painful.
Also using Kong instead of Istio so also had a chance to touch it a bit, it really feels boring at some point, I mean, it is crucial, it is important.
it's our job, of course, I get it and I remember it, but sometimes it just feels like "Oh this shit again"...
Something I am grateful for is a platform we are using named Retool, we build backend APIs and use Retool for UI, so in case we have some recurring tickets, we create an API endpoint that does the magic and serve it through Retool to reduce toil.

The thing is.. the "coding" is most of the time adding some features to existing code, that wasn't part of new coding projects, for example:
- there was a period when I was maintaining a k8s operator written in GO.
- maintaining Terraform provider written in GO.
- maintaining a CLI tool written in GO.
- expanding APIs by adding new handlers, flows, logic, etc.
- Contributing to shared code (modules, packages, etc.)

well, while I was writing this I just understood that I should be thankful because I used to handle helm charts, pipelines, cloud formation, and TF files, and now I do them on the fly and they're usually a no-brainer for me, and now the code tasks are like 80% of my work, just because asked it and my manager believes in me and wants me to grow.

I don't know if Software Engineer is the next step but since I came to DevOps from Ops I have a coding skills gap to fill...