Issues with marshaled config on status page

[grobie]

• Regular expressions are shown as {} instead of the actual regular expression.
• unset fields are shown as null or "" or their default value

Raw config

# ...
      routes:
      - match:
          alertname: MothershipHighErrorRate
        match_re: 
          controller: .*MediaController|.*StreamsController
        receiver: playback-crit
# ...

Printed config

# ...
      routes:
      - receiver: playback-crit
        match:
          alertname: MothershipHighErrorRate
        match_re:
          controller:
            regexp: {}
# ...

[brian-brazil]

@Conorbro

[stuartnelson3]

This is an issue we've dealt with before, I'm not sure why it keeps reappearing. Relevant code is here: https://github.com/prometheus/alertmanager/blob/master/config/config.go#L513-L518

[grobie]

@Conorbro The printed config also prints fields I have not set in the original config. For example smtp_auth_password: null.

[mxinden]

@grobie In regards to null or "" or their default value: This is due to the fact, that we parse the config and then marshall it again in order to elide secrets properly. See this comment.

[auhlig]

Same here. Regexp are shown as {}.
In addition the status page shows values that were never defined in my configuration, but the slack_api_url which is actually defined is null as shown in the snippet below.

global:
  resolve_timeout: 16m
  smtp_from: ""
  smtp_smarthost: ""
  smtp_auth_username: ""
  smtp_auth_password: null
  smtp_auth_secret: null
  smtp_auth_identity: ""
  smtp_require_tls: true
  slack_api_url: null
  pagerduty_url: https://events.pagerduty.com/generic/2010-04-15/create_event.json
  hipchat_url: https://api.hipchat.com/
  hipchat_auth_token: null
  opsgenie_api_host: https://api.opsgenie.com/
  victorops_api_url: https://alert.victorops.com/integrations/generic/20131114/alert/