Monitoring: add service URL manager

[0oM4R]

Updated

Description

• Add ServiceURLManager : a class managing service URLs with liveness checking pick the first reachable endpoint for each service
• Enhancements and Refactoring in service monitoring

Changes

• Refactor:

  • replace ws connection on RMB and TFChain ping with http using health endpoints,
  • replace axios with fetch.
  • Renamed sendGetRequest to sendRequest
  • fix GraphQl isAlive logic
  • replace serviceUrl and serviceName with getters
  • add update method that uses URL setter
  • Make all IServiceBase classes take an optional options on their contractor, add error handling for side effect
  • Grouped all RMB properties to RMB to RMBProps
  • ping url without change the service url, by passing optional url to isAlive

• Feat:

  • add error event handler on RMB direct client
  • add stats monitor class that monitors stats service
  • add activation monitor class that monitor activation service
  • Add serviceURLManager
    • Support silent mode settings
    • Implement constructor to handle URLManagerOptions
    • Add private handleErrorsOnSilentMode method for error handling based on silent mode
    • Implement getAvailableStack method to find reachable service URL
    • Implement getAvailableServicesStack method to fetch and store available service URLs for all services

• Examples: update service monitor example and add serviceURlManager Example, also update example command to take the example file path

• Fix: main and type paths in package.json

Related Issues

• sdk-ts : Support multiple stacks per network  #3078

Documentation PR

For UI changes, Please provide the Documetation PR on info_grid

Checklist

• Tests included
• Build pass
• Documentation
• Code format and docstrings
• Screenshots/Video attached (needed for UI changes)

[AhmedHanafy725]

do we still need this update method?

[0oM4R]

I guess I should replace it with normal setter, and use it here, with the reachable url

[Mahmoud-Emad]

Good job, Omar

[Mahmoud-Emad]

I noticed that you have multiple classes that share a significant amount of similar functionality. To improve code maintainability and reduce duplication, I suggest creating a Base class that encapsulates the common logic. Then, each of the existing classes can inherit from this Base class, allowing them to share the common behavior while still implementing any specific functionality they need.

class Base {
  get url(): string{}
  set url(name: string){}
  async isAlive(url: string): Promise<ServiceStatus> {}
  ....
}

class X extends Base {
  ping(url: string){
    ...
  }
}

class Y extends Base {
  pong(){
    ...
  }
}

[Mahmoud-Emad]

Suggested change

	try {
	const statusPromise = service.isAlive(url);
	const timeoutPromise = new Promise((resolve, reject) => {
	setTimeout(() => {
	reject(new Error("Timeout"));
	}, _timeout * 1000);
	});
	const result = await Promise.race([statusPromise, timeoutPromise]);
	if (result instanceof Error && result.message === "Timeout") {
	throw result;
	}
	const TIME_OUT = "Timeout";
	try {
	const statusPromise = service.isAlive(url);
	const timeoutPromise = new Promise((resolve, reject) => {
	setTimeout(() => {
	reject(new Error(TIME_OUT));
	}, _timeout * 1000);
	});
	const result = await Promise.race([statusPromise, timeoutPromise]);
	if (result instanceof Error && result.message === TIME_OUT) {
	throw result;
	}