Rest JSON endpoint missing

[Phil_Dewhirst]

Hi all

Im trying to find a way to get connection count to a real machine within the loadbalancer pool.

My platform is FortiADC v8.0.1

The closest method listed in the guides is 

/slb/all_vs_status_last_2

but this gives 404 page not found

Any suggestions?

[Jean-Philippe_P]

Hello Phil_Dewhirst, 

Thank you for using the Community Forum. I will seek to get you an answer or help. We will reply to this thread with an update as soon as possible. 

[Jean-Philippe_P]

Hello,

We are still looking for an answer to your question.

We will come back to you ASAP.

[Jean-Philippe_P]

Hello again Phil_Dewhirst,

I found this solution. Can you tell us if it helps, please?

To obtain the connection count to a real machine within the load balancer pool on FortiADC, you can use the FortiView feature. Here’s how you can do it:

1. Access FortiView: Navigate to the FortiView section on your FortiADC interface.

2. Server Load Balance Sub-menu: Within FortiView, go to the "Server Load Balance" sub-menu. This section provides insights into server load-balancing configurations.

3. All Sessions Page: Check the "All Sessions" page under the Server Load Balance sub-menu. This page should provide detailed session information, including connection counts.
   
   

If you encounter a 404 error with a specific URL or page, ensure that the FortiADC firmware version you are using supports that feature or page. If the issue persists, consider reaching out to Fortinet support for further assistance.

[Phil_Dewhirst]

Sorry this is no help.

I need to programmatically get the values via REST API.

There used to be a feature (and is still listed in the REST reference guide for V8.0.)

We are using FortiADC v8.0.1

Its expected usage would have been something like this:

curl -i -k GET http://fortinethost/slb/all_vs_status_last_2 

[Jean-Philippe_P]

Oh okay, sorry it didn't help.

I found this:

The issue you're encountering with the /slb/all_vs_status_last_2 endpoint returning a 404 error on FortiADC v8.0.1 is a known problem because this REST API endpoint is either deprecated, removed, or not enabled in your firmware version despite being listed in some reference guides.

From community reports and official documentation references, it appears that this specific endpoint is no longer supported or accessible in FortiADC v8.0.1, even though it remains mentioned in older or partial REST API documentation.

This discrepancy happens because Fortinet sometimes keeps legacy endpoints documented but removes or replaces them in newer firmware versions.

For programmatic access to real server connection counts within a load balancer pool on FortiADC v8.0.1, the recommended alternative approaches are:

• Use other REST API endpoints related to load balancing status, such as those under /slb/pool/ or /slb/realserver/, which might provide real-time statistics for real servers or pools. However, these endpoints are not always well documented or may require API discovery on your device to confirm availability.

• Leverage CLI commands via SSH scripting to retrieve connection counts. FortiADC's CLI supports commands like get load-balance pool or get load-balance realserver which show connection statistics, and you can automate these commands using SSH scripts if REST API support is incomplete.

• Check the FortiADC GUI for real-time connection counts under the load balancing sections, which could help identify the exact data points you want to extract programmatically.

To verify available REST API endpoints on your device, you can try querying the API root or a discovery endpoint (if available) to list supported paths. This helps confirm what is currently accessible in your firmware.

In summary, the /slb/all_vs_status_last_2 endpoint is not functional on v8.0.1 despite being listed in the reference. The best workaround is to explore other REST API endpoints related to pools or real servers or fall back to CLI commands for connection counts, then automate those via scripts

[Phil_Dewhirst]

Thanks for those.

Ill try the other slb endpoints mentioned (and criticise Fortinet for poor documentation and pointlessly deprecating items with no alternatives)

Those mentioned endpoints are not in the documentation btw.

We shall see if that works.

[Jean-Philippe_P]

Sorry again for this!

Hope it will fix your issue.

[Phil_Dewhirst · Accepted solution]

Im marking this as complete as I no longer am on this project so unfortunately cannot confirm.