Mariana Cavalcante
Mariana Cavalcante
@lpegoraro For this problem where the policy with error remains attached to the agent even after restart: I think the issue is that we reapply all the policies of policy...

We can add a prefix for agent tags before adding to Prometheus labels, for example: agent tag is policy:test and we will add the label as tag_policy:test As @manrodrigues suggested,...
We need to add one more statement pointing to mainflux's /token endpoint here: https://github.com/ns1labs/orb-website/blob/main/.github/workflows/ci.yml ``` - name: redoc-cli user-token uses: seeebiii/redoc-cli-github-action@v10 with: args: 'https://raw.githubusercontent.com/mainflux/mainflux/master/api/openapi/users.yml -o docs/api/token.html' ```
I believe we should think of a workaround or reconsider adding that to our docs since it's maintained by an external project and may change without our supervision removing or...
The issue is around the channel connection. The agent receives back which topic it has to subscribe to but fails because it isn't connected to the group channel. https://netdev-community.slack.com/archives/C041B9204CF/p1671126785235799
because the mainflux-sdk [Connect method](https://github.com/mainflux/mainflux/blob/57e3c25d3de3d07401b044d09f26200085f8d3c1/pkg/sdk/go/sdk.go#L177) `Connect(conns ConnectionIDs, token string) errors.SDKError` need a token which is why we can't call while handling capabilities or any other internal action only triggered by...