feat: add automatic database span coverage to telemetry example

[krishankumar01]

📑 Description

RelatedTo goravel/goravel#726

Framework #1477 added automatic database instrumentation for both facades.Orm() and facades.DB(). The framework module has no SQLite driver, so a live database span can only be asserted end to end here, against a real database and the collector stack.

What is changing:

• The /telemetry handler now runs an automatically instrumented builder query (facades.DB().WithContext(ctx).Table("users").Limit(1).Get(...)). No manual tracing: the query emits a SELECT users client span nested under the request span, the same way facades.Orm() does.
• TestTraces asserts the SELECT users span alongside the existing HTTP, gRPC, manual, and consume spans.

Example:

var users []struct {
    ID   uint   `db:"id"`
    Name string `db:"name"`
}
facades.DB().WithContext(ctx).Table("users").Limit(1).Get(&users)

Depends on goravel/framework#1509:

The DB connection (and the tracer bound to it) is cached process-wide. The telemetry suite swaps telemetry.service.name via OverrideConfig, which restarts the app, so the connection must be rebuilt under the new service for the span to report correctly. goravel/framework#1509 makes app.Restart() reset database connections, so this suite needs no manual Orm().Fresh() / App().Fresh(binding.DB) workaround. CI here stays red until that framework PR merges into master.

✅ Checks

• Added test cases for my code

[Copilot]

Pull request overview

This PR extends the Goravel example app’s telemetry showcase to include end-to-end coverage for the framework’s new automatic database instrumentation (for facades.DB()), and updates the pinned framework commit accordingly.

Changes:

• Add an automatically-instrumented DB builder query to the /telemetry endpoint to emit a SELECT users span.
• Update the telemetry feature test setup to reset ORM state and refresh the database, and assert the new SELECT users span.
• Bump the framework replace pin (and go.sum) to the commit that includes the instrumentation change.

Reviewed changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated 2 comments.

File	Description
app/http/controllers/telemetry_controller.go	Adds a DB builder query intended to emit an automatic SELECT users span under the request trace.
tests/feature/telemetry_test.go	Resets ORM + refreshes DB in suite setup and asserts the additional DB span in Jaeger.
go.mod	Updates the replace pin for github.com/goravel/framework to the commit containing the instrumentation work.
go.sum	Aligns module checksums with the updated framework pin.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 5 changed files in this pull request and generated 1 comment.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 4 changed files in this pull request and generated 1 comment.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 4 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (1)

app/http/controllers/telemetry_controller.go:58

• PR description says the gRPC config key was restored from grpc.clients back to grpc.servers, but config/grpc.go in this branch still defines grpc.clients. If the framework client reads grpc.servers.<name>.host (as described), facades.Grpc().Connect("user") will still fail and /telemetry will return 500 before emitting the expected gRPC spans.

	resp, err := facades.Http().WithContext(ctx).Get("/grpc/user?token=1")
	if err != nil {
		return ctx.Response().Json(http.StatusInternalServerError, http.Json{
			"error": err.Error(),
		})
	}

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

[hwbrzzl]

LGTM, could you fix these two failures? And I had fixed the failed CI in master.

--- FAIL: TestTelemetryTestSuite (95.71s)
    --- FAIL: TestTelemetryTestSuite/TestTraces (60.08s)
        telemetry_test.go:54: telemetry not found at http://localhost:16686/api/traces?service=goravel-plain
            want: ["GET /telemetry" "HTTP GET" "user.UserService/GetUser" "GET /grpc/user" "users.process" "users.consume" "SELECT users"]

--- FAIL: TestTelemetryTLSTestSuite (72.78s)
    --- FAIL: TestTelemetryTLSTestSuite/TestTraces (60.07s)
        telemetry_tls_test.go:69: telemetry not found at http://localhost:16686/api/traces?service=goravel-tls
            want: ["GET /telemetry" "user.UserService/GetUser"]

[hwbrzzl]

Tested locally, awesome!