Add CallCounter details in telemetry docs

[azdagron]

No description provided.

[keeganwitt]

It might be a good enhancement to add a link to the gRPC status documentation (https://pkg.go.dev/google.golang.org/[email protected]/codes#Code I think).

[azdagron]

Good suggestion!

[keeganwitt]

Towards the top of this doc, where it mentions you can all RPC services and methods have a metric, should we mention that the server services are

• https://github.com/spiffe/spire/blob/main/pkg/server/api/svid/v1/service.go
• https://github.com/spiffe/spire/blob/main/pkg/server/api/agent/v1/service.go
• https://github.com/spiffe/spire/blob/main/pkg/server/api/debug/v1/service.go
• https://github.com/spiffe/spire/blob/main/pkg/server/api/entry/v1/service.go
• https://github.com/spiffe/spire/blob/main/pkg/server/api/bundle/v1/service.go
• https://github.com/spiffe/spire/blob/main/pkg/server/api/health/v1/service.go
• https://github.com/spiffe/spire/blob/main/pkg/server/api/trustdomain/v1/service.go

and the agent services are

• https://github.com/spiffe/spire/find/main
• https://github.com/spiffe/spire/blob/main/pkg/agent/api/debug/v1/service.go
• https://github.com/spiffe/spire/blob/main/pkg/agent/api/health/v1/service.go
• https://github.com/spiffe/spire/blob/main/pkg/agent/api/delegatedidentity/v1/service.go

At least I think these are the right lists. For someone unfamiliar with the codebase, it can be hard to figure out what the possible RPC calls are.

[azdagron]

For the available RPCs, I think we should refer to the (currently lacking) documentation in the SPIRE API SDK. I'll update this change with a link to that repository, but in my opinion that is the place where we should focus documentation efforts for the API.

[keeganwitt]

For the available RPCs, I think we should refer to the (currently lacking) documentation in the SPIRE API SDK. I'll update this change with a link to that repository, but in my opinion that is the place where we should focus documentation efforts for the API.

That'd be awesome. I suggested those only because I was unaware of where else to look.

[amartinezfayo]

Thanks, @azdagron!