helm charts: SPIRE server should be able to (optionally) enable telemetry

[v0lkan]

# telemetry: If telemetry is desired use this section to configure the
# available metrics collectors.
# telemetry {
#     Prometheus {
#         # host: Prometheus server host.
#         # host = ""

#         # port: Prometheus server port.
#         port = 9988
#     }

#     DogStatsd = [
#         # List of DogStatsd addresses.
#         { address = "localhost:8125" },
#         { address = "collector.example.org:1337" },
#     ]

#     Statsd = [
#         # List of Statsd addresses.
#         { address = "localhost:1337" },
#         { address = "collector.example.org:8125" },
#     ]

#     M3 = [
#         # List of M3 configurations.
#         { address = "localhost:9000" env = "dev" },
#         { address = "collector.example.org:9000" env = "prod" },
#     ]

#     InMem {
#     }
# }

[v0lkan]

from docs:

Export Metrics for Monitoring This configuration applies to the SPIRE Server and SPIRE Agent To configure a SPIRE Server or Agent to output data to a metrics collector, edit the telemetry section in server.conf or agent.conf. SPIRE can export metrics to Datadog (DogStatsD format), M3, Prometheus, and StatsD. You may configure multiple collectors at the same time. DogStatsD, M3, and StatsD support multiple declarations in the event that you want to send metrics to more than one collector. If you want to use Amazon Cloud Watch for metrics collection, review this document on retrieving custom metrics with the CloudWatch agent and StatsD. Below is an example of a configuration block for agent.conf or server.conf that exports telemetry to Datadog, M3, Prometheus, and StatsD, and disables the in-memory collector:

telemetry {
Prometheus {
port = 9988
}
DogStatsd = [
{ address = "localhost:8125" },
]
Statsd = [
{ address = "localhost:1337" },
{ address = "http://[collector.example.org:8125](http://collector.example.org:8125/)" },
]
M3 = [
{ address = "localhost:9000" env = "prod" },
]
InMem {
enabled = false
}
}

For more information, see the telemetry configuration guide.