Postgresql discovery config - add OTel native receiver

[greatestusername-splunk]

Description: Changes the bundled test and discovery configs for postgresql to the native OTEL receiver. Disables old smartagent postgresql discovery

Link to Splunk idea: <Link to Splunk idea, see https://ideas.splunk.com>

Testing: Bundled tests updated

[greatestusername-splunk]

This was strange. During testing I'd have a 50/50 shot of this postgresql.backends metric showing up or not when pulling metrics for comparison.
Tried longer startup times and different methods of generating connections to try to get this metric to consistently show up but couldn't find any real rhyme or reason.

Open to ideas if it is imperative we have this enabled for testing.

[greatestusername-splunk]

Should be all set to go unless there are more requested changes.

[rmfitzpatrick]

It'd be helpful to add an entry to https://github.com/signalfx/splunk-otel-collector/blob/main/cmd/otelcol/config/collector/config.d.linux/properties.discovery.yaml.example (I hope to automate this w/ the bundlegen process in the future)

[greatestusername-splunk]

It'd be helpful to add an entry to https://github.com/signalfx/splunk-otel-collector/blob/main/cmd/otelcol/config/collector/config.d.linux/properties.discovery.yaml.example (I hope to automate this w/ the bundlegen process in the future)

Do you want me to remove the smartagent/postgresql entry or just set it enabled: false in the example? I'd guess remove that smart agent one fully and replace it with the native postgresql one. But wanted to verify.

[rmfitzpatrick]

Do you want me to remove the smartagent/postgresql entry or just set it enabled: false in the example? I'd guess remove that smart agent one fully and replace it with the native postgresql one. But wanted to verify.

I'd just set the enabled to false instead of removing so that the file can be a quick place to look for the bundled components. I plan on using the tooling updates in #4066 as a base to automatically generate the example property content w/ that in mind, but if you'd prefer they not be included instead it'd be helpful to know why.

[greatestusername-splunk]

I think this is just a flakey test issue?

go: CreateFile C:\Users\RUNNER~1\AppData\Local\Temp\go-build1388815158\b2783\settings.test.exe: Access is denied.

https://github.com/signalfx/splunk-otel-collector/actions/runs/7213743861/job/19654281668?pr=3957

[rmfitzpatrick]

@greatestusername-splunk sorry, I've shifted things from under you. Do you mind ~rebasing and adding the receiver to the new https://github.com/signalfx/splunk-otel-collector/blob/main/internal/confmapprovider/discovery/bundle/components.go#L33 before running make bundle.d once more?

[rmfitzpatrick]

nit, alpha ordering plz

[greatestusername-splunk]

@greatestusername-splunk sorry, I've shifted things from under you. Do you mind ~rebasing and adding the receiver to the new https://github.com/signalfx/splunk-otel-collector/blob/main/internal/confmapprovider/discovery/bundle/components.go#L33 before running make bundle.d once more?

no prob! Should be all set

[rmfitzpatrick]

Suggested change

	version: <ANY>
	version: <VERSION_FROM_BUILD>

nit, though there's a handful of other instances as well

[rmfitzpatrick]

Mind adding a breaking change changelog item and update the discovery readme to include the component? https://github.com/signalfx/splunk-otel-collector/tree/main/internal/confmapprovider/discovery#discovery-mode

I'll look into automating a table along w/ the example properties automation work.

[rmfitzpatrick]

lgtm w/ final requests.

[greatestusername-splunk]

Mind adding a breaking change changelog item and update the discovery readme to include the component? https://github.com/signalfx/splunk-otel-collector/tree/main/internal/confmapprovider/discovery#discovery-mode

I'll look into automating a table along w/ the example properties automation work.

In and ready. 😄