Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dashboard: "WatchbotService: RunningCapacity, DesiredCapacity" chart is empty #351

Closed
jseppi opened this issue Jan 22, 2021 · 2 comments · Fixed by #352
Closed

Dashboard: "WatchbotService: RunningCapacity, DesiredCapacity" chart is empty #351

jseppi opened this issue Jan 22, 2021 · 2 comments · Fixed by #352

Comments

@jseppi
Copy link
Contributor

jseppi commented Jan 22, 2021

Potentially relevant details:

  • using capacity: 'FARGATE_SPOT'

image

@jseppi
Copy link
Contributor Author

jseppi commented Jan 22, 2021

In CloudWatch metrics, I can find the DesiredTaskCount and RunningTaskCount service from the ECS/ContainerInsights namespace. Perhaps the dashboard should use those metrics for this chart?

image

@rclark
Copy link
Contributor

rclark commented Jan 22, 2021

Yeah, this is a bug.

['Mapbox/ecs-cluster', 'RunningCapacity', 'ClusterName', '${Cluster}', 'ServiceName', '${WatchbotService}', { period: 60 }],

['Mapbox/ecs-cluster', 'RunningCapacity', 'ClusterName', '${Cluster}', 'ServiceName', '${WatchbotService}', { period: 60 , yAxis: 'right' }],

These rely on a custom Mapbox metric namespace that (a) never should have been in here in the first place and (b) no longer exists. Switching to the container insights metrics is the right move.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants