flybywiresim / api Goto Github PK

VATSIM sometimes have a suffix on the ATIS now if arrival/departure ATIS are separated so e.g. instead of KATL_ATIS that we expect, it can be KATL_A_ATIS and KATL_D_ATIS.

Airports should have a transition altitude field. The transition altitude should be stored in a DB.

Not all data is being written to a volume currently.

Can the directories in /var/lib/docker/volumes just be renamed?

• External Volume
  Should all Docker volumes should be stored on a DO volume?
• Grafana
  • Find what needs to be persisted
  • Create a transition strategy
  • Use a Compose volume to persist the data
  • Add compose logging config
• MySQL
  • Create a transition strategy (Maybe to managed?)
  • Use Compose to either move to managed or persist data
  • Add compose logging config if not managed

For flybywiresim/installer, we need an API that can retrieve and cache mod releases and latest versions from GitHub.

To be elaborated further

What is this API repo? Is it something that I as a simmer can use? (I'm web programmer)

The Readme should say what it is and who it is for.

• Host Prometheus with compose
  • What needs to be persisted
  • Use Compose for volumes
  • Autodiscovery of other containers
  • Integrate into Grafana
• Prometheus Node Exporter
  • Run the Node Exporter with Compose
  • Integrate Grafana Dashboards
• API Prometheus Exporter
  • Find useful metrics to export
  • Integrate Exporter into API
• Nginx Prometheus
  • Possible with Proxy variant?
  • Enable Plugin
• Blackbox exporter
  • Monitor availability
  • Container or different VM
• Alerting
  • Enable alerts in Grafana which get sent to Discord

Hello, I wanted to first thank you for this API which I have found really useful and had a lot of fun playing with today.

Second, I wanted to flag to you that I have used this in an example project called https://FindMyPlane.live. This is a client which users can run on their own computers which sends their location sim data to my server which then displays it in a pretty nice graphical web interface viewable anywhere via a browser. I have used your api to include traffic of where other players are as well.

You can view an example of my flight tracking at https://findmyplane.live/view/DUMMY and all the traffic at https://findmyplane.live/view_world. The github repo is https://github.com/hankhank10/findmyplane-server

Finally, I have two feature suggestions if I may?

Option to strip out planes on the ground
The first is, as you can see from the below screenshot many of the planes displayed are in fact on the ground at airports.

This may be useful to some users but I think most would prefer to have the option to exclude from the view planes which are stationary on the ground. This would be particularly helpful given for performance reasons (and the fact that the API caps for a single request) I display only the first 100 planes in the map bounds. Given the altitude returned by the API is altitude above sea level (I presume?) there's no straightforward way to strip these out other than running each lat/lon to see if it's near an airport, pulling the altitude of that airport and comparing - which is a lot to run on the client side.

Could I suggest including a field in the JSON output called "stationary_on_ground" which returns true if the landing gear is down and speed is 0? And allowing users of the API to query against that field?

Ability for users to find their plane
I would love to give your users the option to follow their own flight in the same way that people running my client software can. At the moment there doesn't seem to be an easy way for users to identify their flight other than the id (which given it's long I presume is not meant to be user facing) or the "flight" field which doesn't necessarily seem to be unique and seems can be empty. Would you consider adding a user-friendly ident or code which they could use to identify their flight? For my client I use a random 5 character alpha/numerical code but you will of course have your own ideas about how best to implement this.

Thanks again for this great project!

Flight numbers that have been involved in accidents or hijackings should be blocked from being used.

Is your feature request related to a problem? Please describe.

No.

Describe the feature you'd like to see implemented

Self-descriptive. Needed for EFB perf optimization in flybywiresim/aircraft#2227.

Discord username (if different from GitHub): someperson#4953

Currently one has to connect to TELEX as though they are a plane with coordinates, alt, heading, etc. Would be great for other services to be able to connect as a non-plane without needing that info to send/receive TELEX messages to planes.

some ideas are automated company messages to send to the plane while in route...

To have more options when it comes to load balancing we should integrate health checks.
To monitor:

• TypeOrmHealthIndicator
• DNSHealthIndicator (to Redis maybe)

https://docs.nestjs.com/recipes/terminus

Our current pagination is not stable. A cursor-based approach would solve this issue. Our cursor would be the firstContact column since it is ordered and indexed.

Cursors at Slack

Storing of Pings for a full flight path:

• Separate Connection and Status
• Add new API endpoints (versioned)
• A32NX implementation
• Grafana Dashboard showing usage per Commithash

Report additional metrics

• Only report changed values
• Add additional metrics
  • Speed
  • Flight Phase
  • Squawk code
  • Registration
  • Estimated time of arrival
  • Commithash

The binlog_expire_logs_seconds value is set to 30 days. 7-day logs are already at 600MB.
For now, I will update this value manually to 7 days.

The value should be configured when starting the container.

Currently, the endpoint returns all users connected to the TELEX system. At the moment we have around 40 connections. This might increase a lot when it gets released. To still efficiently query the connections API pagination will be needed.

Something like GET /txcxn?limit=20&offset=100 with a set maximum limit.

With around 320 active connections, our API in connection with our non-managed DB gives up.

The Trying to logs are just before the DB calls.

For QA functionality in flybywiresim/installer, we need to have an endpoint that returns a list of open PRs in a repo.

For now, the following info is needed for each PR:

• Title
• Author username
• Labels
• Draft/Open state
• Number

It should also allow downloading of artifacts (by allowing to pass a GitHub personal token)

Caching should be very low at about 1 min max

TELEX not showing the origin/destination airport upon request.