wjordan
September 13, 2022, 5:53pm
21
While we don’t currently have published SLAs , it is a goal of this feature for customers to be able to create their own custom dashboards on this managed instance, and for those dashboards to persist. Data is stored on a Fly Volume so durability expectations are consistent with that feature.
That said, while this service is still in preview things are being changed around quickly, and we’re still working through some application-level bugs/issues that can impact custom settings or dashboard data. On Aug 27-28, a bug in the dashboard-provisioning logic caused all existing dashboards to get unexpectedly deleted, and we didn’t recover this lost data from the daily backups in time. Apologies to you and any other early-adopters who lost work as a result. Making sure something like that doesn’t happen again is a top priority for this feature.
1 Like
tj1
September 27, 2022, 12:05am
22
Hmmm…not sure where to report this, but it is unusual.
On the 22nd, for some reason all the VM’s moved to SJC. I restarted them and as you can see the concurrency has increased quite a bit. However, it is not due to traffic, nor does the open socket count on the application reflect this. For instance, there are not 150 sockets open i on f5c0bfef-dfw.
root@f5c0bfef:/# lsof -ni|grep 4000|grep EST|wc -l
36
root@f5c0bfef:/# lsof -ni|grep 4000|grep EST
beam.smp 516 nobody 106u IPv6 2427246 0t0 TCP 172.19.2.194:4000->172.19.2.193:47482 (ESTABLISHED)
beam.smp 516 nobody 107u IPv6 2422583 0t0 TCP 172.19.2.194:4000->172.19.2.193:37636 (ESTABLISHED)
beam.smp 516 nobody 110u IPv6 2425347 0t0 TCP 172.19.2.194:4000->172.19.2.193:57078 (ESTABLISHED)
beam.smp 516 nobody 111u IPv6 2179534 0t0 TCP 172.19.2.194:4000->172.19.2.193:60280 (ESTABLISHED)
beam.smp 516 nobody 112u IPv6 2418635 0t0 TCP 172.19.2.194:4000->172.19.2.193:33204 (ESTABLISHED)
beam.smp 516 nobody 113u IPv6 2424652 0t0 TCP 172.19.2.194:4000->172.19.2.193:44720 (ESTABLISHED)
beam.smp 516 nobody 114u IPv6 2425023 0t0 TCP 172.19.2.194:4000->172.19.2.193:36488 (ESTABLISHED)
beam.smp 516 nobody 115u IPv6 2358509 0t0 TCP 172.19.2.194:4000->172.19.2.193:32782 (ESTABLISHED)
beam.smp 516 nobody 117u IPv6 2419253 0t0 TCP 172.19.2.194:4000->172.19.2.193:38364 (ESTABLISHED)
beam.smp 516 nobody 119u IPv6 2370230 0t0 TCP 172.19.2.194:4000->172.19.2.193:46374 (ESTABLISHED)
beam.smp 516 nobody 120u IPv6 2370232 0t0 TCP 172.19.2.194:4000->172.19.2.193:46414 (ESTABLISHED)
beam.smp 516 nobody 121u IPv6 2370237 0t0 TCP 172.19.2.194:4000->172.19.2.193:46532 (ESTABLISHED)
beam.smp 516 nobody 122u IPv6 2370240 0t0 TCP 172.19.2.194:4000->172.19.2.193:46560 (ESTABLISHED)
beam.smp 516 nobody 124u IPv6 2272257 0t0 TCP 172.19.2.194:4000->172.19.2.193:53300 (ESTABLISHED)
beam.smp 516 nobody 125u IPv6 2387551 0t0 TCP 172.19.2.194:4000->172.19.2.193:45312 (ESTABLISHED)
beam.smp 516 nobody 126u IPv6 2358622 0t0 TCP 172.19.2.194:4000->172.19.2.193:38936 (ESTABLISHED)
beam.smp 516 nobody 127u IPv6 2425351 0t0 TCP 172.19.2.194:4000->172.19.2.193:57208 (ESTABLISHED)
beam.smp 516 nobody 128u IPv6 2395332 0t0 TCP 172.19.2.194:4000->172.19.2.193:42980 (ESTABLISHED)
beam.smp 516 nobody 129u IPv6 2404045 0t0 TCP 172.19.2.194:4000->172.19.2.193:38392 (ESTABLISHED)
beam.smp 516 nobody 130u IPv6 2427257 0t0 TCP 172.19.2.194:4000->172.19.2.193:48766 (ESTABLISHED)
beam.smp 516 nobody 131u IPv6 2339453 0t0 TCP 172.19.2.194:4000->172.19.2.193:48010 (ESTABLISHED)
beam.smp 516 nobody 132u IPv6 2315387 0t0 TCP 172.19.2.194:4000->172.19.2.193:51860 (ESTABLISHED)
beam.smp 516 nobody 133u IPv6 2420196 0t0 TCP 172.19.2.194:4000->172.19.2.193:34526 (ESTABLISHED)
beam.smp 516 nobody 134u IPv6 2419124 0t0 TCP 172.19.2.194:4000->172.19.2.193:62902 (ESTABLISHED)
beam.smp 516 nobody 135u IPv6 2370246 0t0 TCP 172.19.2.194:4000->172.19.2.193:46746 (ESTABLISHED)
beam.smp 516 nobody 136u IPv6 2370251 0t0 TCP 172.19.2.194:4000->172.19.2.193:46908 (ESTABLISHED)
beam.smp 516 nobody 137u IPv6 2419756 0t0 TCP 172.19.2.194:4000->172.19.2.193:39558 (ESTABLISHED)
beam.smp 516 nobody 138u IPv6 2432811 0t0 TCP 172.19.2.194:4000->172.19.2.193:55730 (ESTABLISHED)
beam.smp 516 nobody 139u IPv6 2340864 0t0 TCP 172.19.2.194:4000->172.19.2.193:33472 (ESTABLISHED)
beam.smp 516 nobody 140u IPv6 2432620 0t0 TCP 172.19.2.194:4000->172.19.2.193:40462 (ESTABLISHED)
beam.smp 516 nobody 141u IPv6 2370262 0t0 TCP 172.19.2.194:4000->172.19.2.193:47318 (ESTABLISHED)
beam.smp 516 nobody 142u IPv6 2432681 0t0 TCP 172.19.2.194:4000->172.19.2.193:44976 (ESTABLISHED)
beam.smp 516 nobody 144u IPv6 2431651 0t0 TCP 172.19.2.194:4000->172.19.2.193:41706 (ESTABLISHED)
beam.smp 516 nobody 145u IPv6 2431924 0t0 TCP 172.19.2.194:4000->172.19.2.193:59934 (ESTABLISHED)
beam.smp 516 nobody 146u IPv6 2431926 0t0 TCP 172.19.2.194:4000->172.19.2.193:59936 (ESTABLISHED)
beam.smp 516 nobody 151u IPv6 2312661 0t0 TCP 172.19.2.194:4000->172.19.2.193:42548 (ESTABLISHED)
Some decrement counter not being set somewhere?
dennis
September 28, 2022, 2:40am
23
Any plans for exposing the Grafana API? Specifically I would like to be able to have my application define my dashboards and send annotations whenever I deploy as per this: Monitoring Elixir Apps on Fly.io With Prometheus and PromEx · Fly
And I’m a +1 for alerting
2 Likes
Is there an API for retrieving billing and costs? I have a dashboard for our hourly costs for some other services and it would be neat to see hourly cost graphs as apps and things are created and destroyed
1 Like
Being able to connect our own data sources (database, loki, tempo, …) would be a great addition to managed grafana.
