yivan-atl

This has been fixed

@nagarajuvemula789 while your suggestion makes sense, there's a way to override the default database settings: ``` jira: additionalEnvironmentVariables: - name: ATL_DB_POOLMAXSIZE value: "200" ``` and so on... You will find...

@knutejohKLP thanks for raising this one. Indeed, adding chmod looks like the right thing to do, but you can also override this init container cmd in your Helm values.

@mattj-relativity thanks for raising this issue. Indeed, metrics can be quite noisy and high cardinality can definitely be an issue. Did I get you right - your suggested excludeObjectNames did...

@atl-mk I wonder if you can help here.

Asked a question here https://github.com/prometheus/jmx_exporter/issues/904 As a workaround you can turn off Confluence specific JMX beans by passing `-Dconfluence.jmx.disabled=true` to JVM args. You will have JVM metrics only though (which...

Another possible workaround I can think of is `metricRelabelings` in a `ServiceMonitor`. https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/user-guides/running-exporters.md I haven't had a chance to verify it and see if it's possible to drop metrics by...

@mattj-relativity isn't it something that you have tried and it didn't work for you?