Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[receiver/sqlserver] Request to add integration tests to show support for different SQL Server versions #34689

Closed
crobert-1 opened this issue Aug 14, 2024 · 3 comments

Comments

@crobert-1
Copy link
Member

Component(s)

receiver/sqlserver

Describe the issue you're reporting

It would be great to add integration tests to ensure recent versions of SQL Server are supported. We could use docker containers to spin up SQL Server instances, and then directly connect to them using the receiver to ensure all possible metrics are gathered from the SQL Server instance.

For now, it would be great to show SQL Server 2019 and 2022 are supported. I'm not sure if there's a need to show support for any further back than that.

@crobert-1 crobert-1 added the needs triage New item requiring triage label Aug 14, 2024
@crobert-1 crobert-1 changed the title [receiver/sqlserver] Add integration tests to show support for different SQL Server versions [receiver/sqlserver] Request to add integration tests to show support for different SQL Server versions Aug 14, 2024
Copy link
Contributor

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@crobert-1 crobert-1 added enhancement New feature or request receiver/sqlquery SQL query receiver receiver/sqlserver and removed receiver/sqlserver receiver/sqlquery SQL query receiver labels Aug 14, 2024
@open-telemetry open-telemetry deleted a comment from github-actions bot Aug 14, 2024
@open-telemetry open-telemetry deleted a comment from github-actions bot Aug 14, 2024
@djaglowski djaglowski removed the needs triage New item requiring triage label Aug 15, 2024
Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Oct 15, 2024
Copy link
Contributor

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants