Matthew Jacobson comments

Results 20 comments of


                                            Matthew Jacobson

Alerting: Incompatibilities with database - AWS RDS, `aurora_mysql` backend

Might be a good idea to update the [docs](https://grafana.com/docs/grafana/latest/setup-grafana/installation/#supported-databases) to mention that Aurora with MySQL compatibility is not supported. @brendamuir

Problem with deduplication of alerts between Grafana Internal alertmanager

Hi @mgronst, would it be possible to enable debug logging and give us a larger time range of logs? Also, seeing your configuration related to HA would help give us...

Alerting: Hook up GMA silence APIs to new authentication handler

/deploy-to-hg

Alerting: Hook up GMA silence APIs to new authentication handler

/deploy-to-hg

Alerting: Hook up GMA silence APIs to new authentication handler

/deploy-to-hg

Alerting: $to and $from does not work in alert rules

Seems like a solution has been found, going to close. Feel free to reopen if the issue persists.

Alerting Provisioning: Importing JSON not working

Hi @PhilippHomann, I have just tested a json export for an alert and json is indeed supported by file provisioning. I'm closing the issue for now, but feel free to...

Alerting: external alertmanager false resolve messages

>However, it is not clear from the documentation how exactly External Alertmanager should be configured now? Here is our recommended way of setting up an external alertmanager: https://grafana.com/docs/grafana/latest/alerting/set-up/configure-alertmanager/#add-an-alertmanager >I gave...

Grafana Alerting: Custom Annotation Variable doesn't get interpreted

For the above error, the template is missing a closing brace, try: ``` {{ if $.values.B.returncode 0 }} Running {{ else }} Unknown error {{ end }} ``` Another possibility...

Grafana Alerting: Custom Annotation Variable doesn't get interpreted

Hi @blackswan1, the experience around testing and creating label/annotation templates is lacking and we're hoping to improve upon this in future. That being said, this is likely a syntax issue...