Skip to content

Conversation

@kristinnardal2
Copy link
Contributor

According to the opentelemetry specification this should always be set
to client for database client libraries.

I've also removed the SetAttributes call and instead set the attributes
during creation of the span. This is what the library SHOULD be doing
according to the opentelemetry api specification.

@vmihailenco
Copy link
Collaborator

Thanks. Could you please fix the commit message? https://www.conventionalcommits.org/en/v1.0.0/

@kristinnardal2 kristinnardal2 changed the title [extra/redisotel] Set span.kind attribute to client fix(extra/redisotel): Set span.kind attribute to client Oct 27, 2021
@kristinnardal2
Copy link
Contributor Author

I've changed the pull request message, It seems to however be complaining about the actual commit message, I would have to do a force push if I need to fix that.

@vmihailenco
Copy link
Collaborator

I would have to do a force push if I need to fix that.

Yes, you need to force-push. We use commit messages to auto-generate the changelog.

According to the opentelemetry specification this should always be set to client for database client
libraries.

I've also removed the SetAttributes call and instead set the attributes during creation of the span.
This is what the library SHOULD be doing according to the opentelemetry api specification.
@kristinnardal2
Copy link
Contributor Author

I've fixed the commit message and force pushed.
I ran commitlint locally to see that it didn't give me any errors.

@kristinnardal2 kristinnardal2 changed the title fix(extra/redisotel): Set span.kind attribute to client fix(extra/redisotel): set span.kind attribute to client Oct 27, 2021
@vmihailenco
Copy link
Collaborator

Thanks

@vmihailenco vmihailenco merged commit 25378ca into redis:master Oct 27, 2021
@kristinnardal2 kristinnardal2 deleted the redisotel-span-kind branch October 27, 2021 08:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants