Skip to content

Commit

Permalink
Update tips-and-troubleshooting.md
Browse files Browse the repository at this point in the history 
review - case
  • Loading branch information
@lbadenhop
lbadenhop authored Nov 28, 2023
1 parent 88ece55 commit bb856b3
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions ...n/docs/connect_manage_environ/connect_azure_gateway/tips-and-troubleshooting.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -17,8 +17,8 @@ This section describe the common error cases you can encounter when using agents
| Why can't my agents connect to Amplify? | Go to Amplify > Organization > Service Accounts and make sure that the Service Account is correctly named and valid (`CENTRAL_AUTH_CLIENTID`). Make sure that the organizationID (`CENTRAL_ORGANIZATIONID`) is correct. Verify the key's file name and path (`CENTRAL_AUTH_PUBLICKEY` and `CENTRAL_AUTH_PRIVATEKEY`). |
| I have the following error: `Amplify Central - FAIL (error creating request header. bad response from AxwayId: 400 Bad Request)` | Make sure that the Service Account set up is properly spelled (refer to `CENTRAL_AUTH_CLIENTID` property). Verify that the public/private key pair is the one corresponding to the Service Account (`CENTRAL_AUTH_PUBLICKEY` and `CENTRAL_AUTH_PRIVATEKEY`). |
| I have the following 403 error: `The client '11011f4a-67e9-4177-yyyy-xxxxx' with object id '11011f4a-67e9-4177-yyyy-xxxxx' does not have authorization to perform action 'Microsoft.ApiManagement/service/apis/read' over scope '/subscriptions/<SUBSCRIPTION_ID>/resourceGroups/<resourceGroupName>/providers/Microsoft.ApiManagement/service/<serviceName>' or the scope is invalid` | Make sure that the service principal the agent is using has the Contributor role available for the mentioned `<resourceGroupName>`. |
| Why don't I see traffic in Amplify Business Insights? | Make sure that the `TRACEABILITY_HOST` and `TRACEABILITY_PORT` are accessible from the machine where Traceability Agent is installed. If you are using a proxy (`TRACEABILITY_PROXYURL`), make sure the connections are opened correctly. Refer to [Communication ports](/docs/connect_manage_environ/connected_agent_common_reference/network_traffic/#communication-ports). |
| Why don't I see my Traceability agent picking up any transactions? | It is possible that there's another application accessing the same streaming data. Make sure that the Traceability Agent is the only agent accesing the `$Default` consumer group in the event hub. You can also take adavantage of the `AZURE_EVENTHUBCONSUMERGROUP` variable to configure another consumer group. Refer to [Azure Agent Variables](/docs/connect_manage_environ/connect_azure_gateway/#agent-variables). |
| Why don't I see traffic in Amplify Business insights? | Make sure that the `TRACEABILITY_HOST` and `TRACEABILITY_PORT` are accessible from the machine where Traceability Agent is installed. If you are using a proxy (`TRACEABILITY_PROXYURL`), make sure the connections are opened correctly. Refer to [Communication ports](/docs/connect_manage_environ/connected_agent_common_reference/network_traffic/#communication-ports). |
| Why don't I see my Traceability Agent picking up any transactions? | It is possible that there's another application accessing the same streaming data. Make sure that the Traceability Agent is the only agent accesing the `$Default` consumer group in the event hub. You can also take adavantage of the `AZURE_EVENTHUBCONSUMERGROUP` variable to configure another consumer group. Refer to [Azure Agent Variables](/docs/connect_manage_environ/connect_azure_gateway/#agent-variables). |
| Why isn't my agent status displayed in the environment details page? | It is possible that your agents and their corresponding resources are not linked together. Follow [this procedure](/docs/connect_manage_environ/environment_agent_resources) to ensure the correct usage of agent resources. |
| Why is my Traceability Agent receiving EOF errors while sending transaction events? | It is possible that the number of `TRACEABILITY_WORKER` is set too high. lower the number of configured workers. |

Expand Down

0 comments on commit bb856b3

Please sign in to comment.