Support setting `metrics_collection_enabled` during deployment

[brooklynbagel]

Summary

When deploying content to Posit Connect via Publisher, there is currently no way to configure metrics_collection_enabled for the content item. This means users must manually enable resource metrics collection after deployment via the Connect Dashboard or API.

Problem

Connect supports per-content resource metrics (CPU, memory, connection counts) via the metrics_collection_enabled field on content items. This can be set at creation time via POST /v1/content or updated afterward via PATCH /v1/content/{guid}. However, Publisher's configuration files (in .posit/publish/) don't expose this setting, so users deploying via Publisher cannot enable metrics collection as part of their deployment workflow.

Proposed Solution

Add support for a configuration option (e.g., in the .posit/publish/*.toml configuration file) that maps to the metrics_collection_enabled field in the Connect API. When deploying, Publisher would include this field in the content creation/update API call.

Example configuration:

[connect.runtime]
metrics_collection_enabled = true

Workarounds

• Set Applications.MetricsCollectionEnabled = true server-wide in rstudio-connect.gcfg
• Manually call PATCH /v1/content/{guid} after deployment
• Use the Connect Dashboard to enable metrics after deployment

References

• Connect API: Create content
• Connect Admin Guide: Per-content job metrics

[jonkeane]

@marcosnav will this flag be changing with your work? Or is it still the way?

[dotNomad]

Thanks for the issue @brooklynbagel!

I threw Claude at this locally and will have a draft PR up momentarily. I'll wait for @marcosnav to get back before marking it as ready to review.

[marcosnav]

@jonkeane @dotNomad

This will be superseded by content_telemetry soon. Still, since metrics_collection_enabled has been public for a while, very likely we will still support it if present.

BUT, if it will be deprecated soon, in the case of Publisher it might be better to use content_telemetry from the beginning.

[dotNomad]

Thanks for the update @marcosnav. If this metrics_collection_enabled is being deprecated for content_telemetry I think it makes sense to close up my draft, and when content_telemetry is added we can add support for it in Publisher in a similar way to #4202