(Migrated) Zato 2.0.0pre0.rev-cd82c9b6 - zato default services no longer listed in admin gui -> services

(This message has been automatically imported from the retired mailing list)

user@zatoTest:~/zato$ zato --version
Zato 2.0.0pre0.rev-cd82c9b6

The admin gui do not list the zato standard services anymore.

I seem to remember that being so on 1.1.
Is this intentional?

Thanx

On 17/10/14 19:49, Baad Sequel wrote:

The admin gui do not list the zato standard services anymore.

I seem to remember that being so on 1.1.
Is this intentional?

Hi Baad,

yes, it is.

The reason is that there are over 200 internal services and listing all
of them along with actual user services would mean people waiting for
200+ items they are pretty much never interested in.

If you’d like to bring the old behaviour back, please open server.conf,
set misc.return_internal_objects to True and restart the server.

A related aspect that has changed recently is that there are no
sparklines displayed in the service list.

Picture the situation:

  • 230 services (internal + yours)

  • For each web-admin needs to AJAX grab the JSON representing the
    sparklines and actually display them

  • The request goes from web-admin to a server to Redis and back

  • Let’s say a single request takes 0.2 sec

  • Let’s say your are on FF and can issue 8 concurrent request
    (https://stackoverflow.com/a/7456934)

  • This gives us almost a minute during which the web-admin is completely
    unusable and everyone complains that it freezes

Thus, doing away with listing internal services + not displaying
sparklines (they are still available in statistics, as usual) makes
web-admin work faster even though in the latter case what limits it
really is the browser itself.

On 17/10/14 19:49, Baad Sequel wrote:

The admin gui do not list the zato standard services anymore.

I seem to remember that being so on 1.1.
Is this intentional?

Hi Baad,

yes, it is.

The reason is that there are over 200 internal services and listing all
of them along with actual user services would mean people waiting for
200+ items they are pretty much never interested in.

If you’d like to bring the old behaviour back, please open server.conf,
set misc.return_internal_objects to True and restart the server.

A related aspect that has changed recently is that there are no
sparklines displayed in the service list.

Picture the situation:

  • 230 services (internal + yours)

  • For each web-admin needs to AJAX grab the JSON representing the
    sparklines and actually display them

  • The request goes from web-admin to a server to Redis and back

  • Let’s say a single request takes 0.2 sec

  • Let’s say your are on FF and can issue 8 concurrent request
    (https://stackoverflow.com/a/7456934)

  • This gives us almost a minute during which the web-admin is completely
    unusable and everyone complains that it freezes

Thus, doing away with listing internal services + not displaying
sparklines (they are still available in statistics, as usual) makes
web-admin work faster even though in the latter case what limits it
really is the browser itself.

Ah, I see.

Thank you for clarifying. Much appreciated!

On Fri, Oct 17, 2014 at 11:19 PM, Dariusz Suchojad dsuch@zato.io wrote:

On 17/10/14 19:49, Baad Sequel wrote:

The admin gui do not list the zato standard services anymore.

I seem to remember that being so on 1.1.
Is this intentional?

Hi Baad,

yes, it is.

The reason is that there are over 200 internal services and listing all
of them along with actual user services would mean people waiting for
200+ items they are pretty much never interested in.

If you’d like to bring the old behaviour back, please open server.conf,
set misc.return_internal_objects to True and restart the server.

A related aspect that has changed recently is that there are no
sparklines displayed in the service list.

Picture the situation:

  • 230 services (internal + yours)

  • For each web-admin needs to AJAX grab the JSON representing the
    sparklines and actually display them

  • The request goes from web-admin to a server to Redis and back

  • Let’s say a single request takes 0.2 sec

  • Let’s say your are on FF and can issue 8 concurrent request
    (https://stackoverflow.com/a/7456934)

  • This gives us almost a minute during which the web-admin is completely
    unusable and everyone complains that it freezes

Thus, doing away with listing internal services + not displaying
sparklines (they are still available in statistics, as usual) makes
web-admin work faster even though in the latter case what limits it
really is the browser itself.