Skip to content
This repository has been archived by the owner on Apr 8, 2024. It is now read-only.

Inject identifier to gRPC Client #98

Closed
jwulf opened this issue Oct 26, 2019 · 0 comments
Closed

Inject identifier to gRPC Client #98

jwulf opened this issue Oct 26, 2019 · 0 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@jwulf
Copy link
Member

jwulf commented Oct 26, 2019

At the moment, gRPC Client logs don't identify the task type of the worker, or if it is the gRPC Client for a ZBClient. In projects with multiple workers, they do not provide information about which parts are failing.

For example:

endpoint     | {"id":"gRPC Channel","level":50,"message":"GRPC ERROR: 14 UNAVAILABLE: GOAWAY received","pollMode":"Long Poll","taskType":"gRPC Channel","time":"2019 Oct-26 10:44:19AM","timestamp":"2019-10-26T10:44:19.354Z"}
endpoint     | {"id":"gRPC Channel","level":50,"message":"GRPC Channel State: IDLE","pollMode":"Long Poll","taskType":"gRPC Channel","time":"2019 Oct-26 10:44:19AM","timestamp":"2019-10-26T10:44:19.354Z"}
endpoint     | {"id":"gRPC Channel","level":30,"message":"gRPC Channel reconnected","pollMode":"Long Poll","taskType":"gRPC Channel","time":"2019 Oct-26 10:44:19AM","timestamp":"2019-10-26T10:44:19.355Z"}

The GRPCClient class should take an id string that is Worker: ${taskType} or ZBClient to add in debugging.

@jwulf jwulf self-assigned this Oct 26, 2019
@jwulf jwulf added this to the 0.21.3 milestone Oct 26, 2019
@jwulf jwulf changed the title Inject identifier to gRPC Client Feature: Inject identifier to gRPC Client Oct 26, 2019
@jwulf jwulf changed the title Feature: Inject identifier to gRPC Client Inject identifier to gRPC Client Oct 26, 2019
@jwulf jwulf added the enhancement New feature or request label Oct 26, 2019
@jwulf jwulf closed this as completed in ac2cef6 Nov 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant