- 최신
- 최다 투표
- 가장 많은 댓글
Sorry about that.
Are you still seeing it? In any particular regions or all regions? Can you provide a matchmaker configuration id that is impacted?
I've pinged the GameLift service team about this to see if they are aware. I don't see any status reports on https://status.aws.amazon.com/ so it may be just localized to you sadly.
In the future, if this is impacting your game, you may want to open an issue through AWS Support as they can talk directly to GameLift.
Sure. We run our match making out of us-west-2. The configuration is BattleArena-Default-Latest. Happy to open an issue if that's the preferred route. Thanks for the quick response.
Any updates the this issue? I'm still not seeing the missing metrics in our matchmaking dashboard. Should I open a support issue? Thanks.
Apologies, I missed your responses. I have pinged the GameLift Service team for help in understanding whats going on.
Do you have any sample ticket ids? Or the Matchmaking config id? Or fleet/queue id this is tied to? Would help identify your resource as "BattleArena-Default-Latest" may not be unique enough to identify your account and config.
Sure! The matchmaking configuration in question uses queue: arn:******
I'm not actually sure where in the dashboard I can see individual ticket ids...?
Checking in again. The issue still persists and I'd be curious to know if the GameLift team has had an opportunity to look into it. Thanks for any updates!
Also, I did look into creating a case in the AWS support center but apparently I have to upgrade to a higher paid tier to do so. Think I'm not clear of the preferred method to open an issue. Surely I don't have to pay for an upgraded support plan just to file a bug...?
I can confirm that I am facing a similar issue with the matchmaking configuration dashboard in the us-east-1 region.
Looks like the situation may have been resolved as of around 1:30PM PST. My thanks to anyone involved in resolving the issue (and to chrisgong for the bump).
