A freshly installed Message Processor on private cloud not logging API proxy logs. The Router and MP are on the same node.
Existing RMPs have log paths in this manner:
/opt/apigee/var/log/edge-message-processor/messagelogging/{organization}/prod/{api proxy}/{proxy revison}/LogPolicy
Newly installed RMPs have their logs paths as below hence missing the exact location where the logs should be generated.
/opt/apigee/var/log/edge-message-processor/messagelogging
What could have missed even during the installation? Any contribution will be of high assistance. @Dino @Anil Sagar @ Google
Solved! Go to Solution.
is the traffic flowing through the particular rmp?
To test this, you can shutdown all other rmps and check whether it's handling the traffic.
If not you have to associate the new rmps with particular pod and organisation.
Ref: https://docs.apigee.com/private-cloud/v4.18.01/adding-router-or-message-processor-node
Actually the new RMPs were still not associated with their corresponding pods and regions.I achieved that with the following steps:
1. Confirmed if the new RMPs are on the existing environments
curl -v -u username:password http://<MS_IP>:8080/v1/organizations/{organizations_name}/environments/{environments_name}/servers
2.Checked the UUID of the Message Processor
curl http://<MP_IP>:8082/v1/servers/self
3.Checked the UUID of the Router
curl http://<Router_IP>:8081/v1/servers/self
4.Associated Router with its pod and region
curl -v -u username:password -X POST http://<MS_IP>:8080/v1/regions/{region_name}/pods/{pod_name}/servers -d "action=add&uuid={router_UUID}&type=router"
5. Assocaited the Message Processor with its environement
curl -v -u username:password -H "Content-Type: application/x-www-form-urlencoded" -X POST "http://<MS_IP>:8080/v1/organizations/{org_name}/environments/{env_name}/servers" -d "action=add&uuid={MP_UUID}"
The link you shared above has the materials. Thanks it worked.
is the traffic flowing through the particular rmp?
To test this, you can shutdown all other rmps and check whether it's handling the traffic.
If not you have to associate the new rmps with particular pod and organisation.
Ref: https://docs.apigee.com/private-cloud/v4.18.01/adding-router-or-message-processor-node
The RMPs are processing traffic well except for the logs that are missing .
In the meantime I will also check your recommendation.
Actually the new RMPs were still not associated with their corresponding pods and regions.I achieved that with the following steps:
1. Confirmed if the new RMPs are on the existing environments
curl -v -u username:password http://<MS_IP>:8080/v1/organizations/{organizations_name}/environments/{environments_name}/servers
2.Checked the UUID of the Message Processor
curl http://<MP_IP>:8082/v1/servers/self
3.Checked the UUID of the Router
curl http://<Router_IP>:8081/v1/servers/self
4.Associated Router with its pod and region
curl -v -u username:password -X POST http://<MS_IP>:8080/v1/regions/{region_name}/pods/{pod_name}/servers -d "action=add&uuid={router_UUID}&type=router"
5. Assocaited the Message Processor with its environement
curl -v -u username:password -H "Content-Type: application/x-www-form-urlencoded" -X POST "http://<MS_IP>:8080/v1/organizations/{org_name}/environments/{env_name}/servers" -d "action=add&uuid={MP_UUID}"
The link you shared above has the materials. Thanks it worked.
User | Count |
---|---|
7 | |
2 | |
2 | |
1 | |
1 |