New component: Solarwinds APM settings extension

[jerrytfleung]

The purpose and use-cases of the new component

The Solarwinds APM settings extension component gets Solarwinds APM specific settings from Solarwinds APM proprietary collector and outputs a solarwinds-apm-settings.json file and a solarwinds-apm-settings-raw file to the temp folder periodically.

The use-case of this new component is for opentelemetry lambda extension layers (Python, Java, NodeJS, .Net) to read the file and perform head-based sampling at the opentelemetry lambda extension layer.

Example configuration for the component

extensions:
  solarwindsapmsettings:
    endpoint: "apm.collector.cloud.solarwinds.com:443"
    key: "<token>:<name>"
    interval: 1m

endpoint (Required)

The endpoint which this extension calls getSettings.

Default: apm.collector.cloud.solarwinds.com:443

key (Required)

The key in format <token>:<name> for getSettings from Solarwinds APM collector.

interval (Optional)

Periodic interval to get Solarwinds APM specific settings from Solarwinds APM collector.

Default: 1m

Telemetry data types supported

N/A

Is this a vendor-specific component?

• This is a vendor-specific component
• If this is a vendor-specific component, I am proposing to contribute and support it as a representative of the vendor.

Code Owner(s)

@jerrytfleung, @cheempz

Sponsor (optional)

@atoulme

Additional context

No response

[atoulme]

I don't follow the use case, but I guess since it's vendor specific that's not a blocker. You need to identify a sponsor for your use case, please read CONTRIBUTING.md and make sure to attend a SIG meeting to present your proposal.

[jerrytfleung]

I don't follow the use case, but I guess since it's vendor specific that's not a blocker. You need to identify a sponsor for your use case, please read CONTRIBUTING.md and make sure to attend a SIG meeting to present your proposal.

Thanks for your reply. We will attend a SIG meeting.