Dual Data Center Analytics Group Setup - Page 2

ccovney · 03-25-2016 12:06 PM

Hi everyone,

I have just set up a Dual data center Apigee Edge on-prem deployment, wherein our preexisting DC was expanded to encompass another. We created another environment, prod-2, so that there could be targetserver and virutalhost config independence via the add-env.sh script.

When I ran the enable-ax.sh script for this new env, I saw this message at the end:

--> curl -X POST http://mgmt-svr:8080/v1/organizations/org/environments/prod-2/analytics/admin?type=organizations [...]
{
  "code" : "PG e670d246-bf7e-4217-bf26-15cd8ddb8eff Not registered with any group",
  "message" : "PG e670d246-bf7e-4217-bf26-15cd8ddb8eff Not registered with any group",
  "contexts" : [ ]
}
==> 400

Whenever I try to look any anything analytics related in the management ui, I see the red error box with "Could not resolve scope <orgname>.<envname>."

We also see the following error in the PG system logs:

2016-03-25 14:15:18,058  pool-30-thread-1 WARN  c.a.a.m.MessageConsumerBuilder - MessageConsumerBuilder.isQpidInSameRegionAsSelf() : Not opening consumers to 71be1378-b2ac-4e1d-b68f-f60afcf2ed6e, from this server 39213ee3-dbfa-4c49-bdc8-26851e1e542b as they are in different regions dc-1/dc-2

All that being said, I have a more general question: If we want to have separate analytics in the mgmt ui for our prod and prod-2 environments, should we create a different analytics group? What are the best next steps here for enabling analytics for our new prod-2 env which are separate in the ui from the prod env analytics?

Thanks a lot!

Best,

Chris