OSGeo.org › OSGeo Software and Data Projects › MapGuide Open Source › MapGuide Internals

Server status/Ping API

18 messages

Server status/Ping API

Reply Threaded

Hi All,

The existing Server Admin service has the following APIs that are not officially published but are available to use:

GetSiteVersion() - returns the exact MapGuide server version
GetSiteInfo() - returns MapGuide server information and OS information

Both of these require authentication credentials because of the information returned.

I was wondering about adding a new API that would not require authentication credentials.

Example: GetSiteStatus()

I would like it to return the server status as either "Offline" or "Online" as some of the information.

This API could be used as a sort of "ping" if needed.

What other non sensitive information do you think we could include with this API?

Thanks,
Bruce
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

Trevor Wekel

RE: Server status/Ping API

Reply Threaded

Hi Bruce,

Would information similar to "uptime" from Linux be appropriate?

03:38:49 up 2 days, 17:29, 1 user, load average: 0.00, 0.00, 0.10

This would roughly translate to system time, MapGuide Server uptime, offline/online, and current user load.

We could also include server process memory utilization but that would take longer to generate.

Thanks,
Trevor

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Bruce Dechant
Sent: October 22, 2009 1:36 PM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] Server status/Ping API

Hi All,

The existing Server Admin service has the following APIs that are not officially published but are available to use:

GetSiteVersion() - returns the exact MapGuide server version
GetSiteInfo() - returns MapGuide server information and OS information

Both of these require authentication credentials because of the information returned.

I was wondering about adding a new API that would not require authentication credentials.

Example: GetSiteStatus()

I would like it to return the server status as either "Offline" or "Online" as some of the information.

This API could be used as a sort of "ping" if needed.

What other non sensitive information do you think we could include with this API?

Thanks,
Bruce
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

Jason Birch

Re: Server status/Ping API

Reply Threaded

In reply to this post by Bruce Dechant

I think it would be cool to return API version (2.1, 2.2, etc) as part
of this, but not rev/build.

Would be hesitant to return performance metrics through a non-authenticated api.

Jason

On 2009-10-22, Bruce Dechant <[hidden email]> wrote:

> Hi All,
>
> The existing Server Admin service has the following APIs that are not
> officially published but are available to use:
>
> GetSiteVersion() - returns the exact MapGuide server version
> GetSiteInfo() - returns MapGuide server information and OS information
>
> Both of these require authentication credentials because of the information
> returned.
>
> I was wondering about adding a new API that would not require authentication
> credentials.
>
> Example: GetSiteStatus()
>
> I would like it to return the server status as either "Offline" or "Online"
> as some of the information.
>
> This API could be used as a sort of "ping" if needed.
>
> What other non sensitive information do you think we could include with this
> API?
>
> Thanks,
> Bruce
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>

_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

Martin Morrison

RE: Server status/Ping API

Reply Threaded

In thinking back to some hung services over the past few years, I would think we would want to verify that a SMALL mapimage can be returned. This would be a better test to verify MapGuide is actually working for a client.

Martin

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Jason Birch
Sent: Sunday, October 25, 2009 1:00 PM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] Server status/Ping API

I think it would be cool to return API version (2.1, 2.2, etc) as part
of this, but not rev/build.

Would be hesitant to return performance metrics through a non-authenticated api.

Jason

On 2009-10-22, Bruce Dechant <[hidden email]> wrote:

Bruce Dechant

RE: Server status/Ping API

Reply Threaded

In reply to this post by Jason Birch

The API version would be nice to have.

I have to agree that performance metrics without credentials I'm not sure I like.

Bruce

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Jason Birch
Sent: Sunday, October 25, 2009 11:00 AM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] Server status/Ping API

I think it would be cool to return API version (2.1, 2.2, etc) as part
of this, but not rev/build.

Would be hesitant to return performance metrics through a non-authenticated api.

Jason

On 2009-10-22, Bruce Dechant <[hidden email]> wrote:

Trevor Wekel

RE: Server status/Ping API

Reply Threaded

No problem on the performance metrics.

Martin's suggestion of doing a lightweight render is a good idea. Perhaps we can make this an optional item with the render only occurring if a map definition resource id is supplied as an input parameter. We could just render a small image at the map extents. The various pieces - API version, offline/online, and image could be returned as an xml document with the image returned as a base64 blob. Something like this perhaps:

<Ping>
<Status>Online</Status>
<ApiVersion>2.2</ApiVersion>
<ImageSize>8061</ImageSize>
<Image>[8061 base64 encoded bytes]</Image>
</Ping>

Thanks,
Trevor

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Bruce Dechant
Sent: October 26, 2009 7:55 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

The API version would be nice to have.

I have to agree that performance metrics without credentials I'm not sure I like.

Bruce

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Jason Birch
Sent: Sunday, October 25, 2009 11:00 AM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] Server status/Ping API

I think it would be cool to return API version (2.1, 2.2, etc) as part
of this, but not rev/build.

Would be hesitant to return performance metrics through a non-authenticated api.

Jason

On 2009-10-22, Bruce Dechant <[hidden email]> wrote:

Martin Morrison

RE: Server status/Ping API

Reply Threaded

Key word being SMALL...<G> This could even be a single color sample image. Just something to make the render engine works...

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Trevor Wekel
Sent: Monday, October 26, 2009 10:08 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

No problem on the performance metrics.

Martin's suggestion of doing a lightweight render is a good idea. Perhaps we can make this an optional item with the render only occurring if a map definition resource id is supplied as an input parameter. We could just render a small image at the map extents. The various pieces - API version, offline/online, and image could be returned as an xml document with the image returned as a base64 blob. Something like this perhaps:

<Ping>
<Status>Online</Status>
<ApiVersion>2.2</ApiVersion>
<ImageSize>8061</ImageSize>
<Image>[8061 base64 encoded bytes]</Image>
</Ping>

Thanks,
Trevor

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Bruce Dechant
Sent: October 26, 2009 7:55 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

The API version would be nice to have.

I have to agree that performance metrics without credentials I'm not sure I like.

Bruce

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Jason Birch
Sent: Sunday, October 25, 2009 11:00 AM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] Server status/Ping API

I think it would be cool to return API version (2.1, 2.2, etc) as part
of this, but not rev/build.

Would be hesitant to return performance metrics through a non-authenticated api.

Jason

On 2009-10-22, Bruce Dechant <[hidden email]> wrote:

Dave Wilson

RE: Server status/Ping API

Reply Threaded

I would pre-define a default map image and settings as input values server side in the serverconfig: no point in having to remember this and supplying the path and stuff each time. Include a WithImage flag or something and make the map parameters optional or don't even bother supplying them to keep the signature light and the usability simple. Of course regardless if you supply the parameter or get it from the serverconfig it's possible the ResourceId is invalid and you'd get a rendering exception. Something to ponder.

To clarify a couple of points:

Do we include the Site Name as part of the results?
If we have a load balanced configuration do we return results for all sites and their status? This would be similar to the API we used to have for MG 6.5.

Dave

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Martin Morrison
Sent: Monday, October 26, 2009 8:25 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

Key word being SMALL...<G> This could even be a single color sample image. Just something to make the render engine works...

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Trevor Wekel
Sent: Monday, October 26, 2009 10:08 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

No problem on the performance metrics.

Martin's suggestion of doing a lightweight render is a good idea. Perhaps we can make this an optional item with the render only occurring if a map definition resource id is supplied as an input parameter. We could just render a small image at the map extents. The various pieces - API version, offline/online, and image could be returned as an xml document with the image returned as a base64 blob. Something like this perhaps:

<Ping>
<Status>Online</Status>
<ApiVersion>2.2</ApiVersion>
<ImageSize>8061</ImageSize>
<Image>[8061 base64 encoded bytes]</Image>
</Ping>

Thanks,
Trevor

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Bruce Dechant
Sent: October 26, 2009 7:55 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

The API version would be nice to have.

I have to agree that performance metrics without credentials I'm not sure I like.

Bruce

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Jason Birch
Sent: Sunday, October 25, 2009 11:00 AM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] Server status/Ping API

I think it would be cool to return API version (2.1, 2.2, etc) as part
of this, but not rev/build.

Would be hesitant to return performance metrics through a non-authenticated api.

Jason

On 2009-10-22, Bruce Dechant <[hidden email]> wrote:

Bruce Dechant

RE: Server status/Ping API

Reply Threaded

In reply to this post by Trevor Wekel

A ping is supposed to be fast - adding overhead to generate a map image could be slow, but having this optional would get around that. What about security risks of being able to render a map without credentials? Obviously if it is a tiny thumbnail of the map it is not very useful at all - other than to see if the server is there and can render it.

Thanks,
Bruce

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Trevor Wekel
Sent: Monday, October 26, 2009 8:08 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

No problem on the performance metrics.

Martin's suggestion of doing a lightweight render is a good idea. Perhaps we can make this an optional item with the render only occurring if a map definition resource id is supplied as an input parameter. We could just render a small image at the map extents. The various pieces - API version, offline/online, and image could be returned as an xml document with the image returned as a base64 blob. Something like this perhaps:

<Ping>
<Status>Online</Status>
<ApiVersion>2.2</ApiVersion>
<ImageSize>8061</ImageSize>
<Image>[8061 base64 encoded bytes]</Image>
</Ping>

Thanks,
Trevor

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Bruce Dechant
Sent: October 26, 2009 7:55 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

The API version would be nice to have.

I have to agree that performance metrics without credentials I'm not sure I like.

Bruce

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Jason Birch
Sent: Sunday, October 25, 2009 11:00 AM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] Server status/Ping API

I think it would be cool to return API version (2.1, 2.2, etc) as part
of this, but not rev/build.

Would be hesitant to return performance metrics through a non-authenticated api.

Jason

On 2009-10-22, Bruce Dechant <[hidden email]> wrote:

Dave Wilson

RE: Server status/Ping API

Reply Threaded

If we assume the image is a test image only then I wouldn't be concerned about the map and credentials. We could even supply a default one that is a variation of Sheboygan or something with 1 or 2 layers max. Since the eventual request is server side it could use the server authentication to access and render the map.

I'm more concerned about how you get multiple results back from all sites. I'm guessing the request is a multipart post that processes each server one by one in a loop in the webtier or does it process them all, assemble the results (including any failures) and return one result set?

Dave

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Bruce Dechant
Sent: Monday, October 26, 2009 9:23 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

A ping is supposed to be fast - adding overhead to generate a map image could be slow, but having this optional would get around that. What about security risks of being able to render a map without credentials? Obviously if it is a tiny thumbnail of the map it is not very useful at all - other than to see if the server is there and can render it.

Thanks,
Bruce

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Trevor Wekel
Sent: Monday, October 26, 2009 8:08 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

No problem on the performance metrics.

Martin's suggestion of doing a lightweight render is a good idea. Perhaps we can make this an optional item with the render only occurring if a map definition resource id is supplied as an input parameter. We could just render a small image at the map extents. The various pieces - API version, offline/online, and image could be returned as an xml document with the image returned as a base64 blob. Something like this perhaps:

<Ping>
<Status>Online</Status>
<ApiVersion>2.2</ApiVersion>
<ImageSize>8061</ImageSize>
<Image>[8061 base64 encoded bytes]</Image>
</Ping>

Thanks,
Trevor

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Bruce Dechant
Sent: October 26, 2009 7:55 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

The API version would be nice to have.

I have to agree that performance metrics without credentials I'm not sure I like.

Bruce

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Jason Birch
Sent: Sunday, October 25, 2009 11:00 AM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] Server status/Ping API

I think it would be cool to return API version (2.1, 2.2, etc) as part
of this, but not rev/build.

Would be hesitant to return performance metrics through a non-authenticated api.

Jason

On 2009-10-22, Bruce Dechant <[hidden email]> wrote:

Walt Welton-Lair

RE: Server status/Ping API

Reply Threaded

How about reducing this to just a legend image? That will still exercise rendering, but it avoids the overhead of making FDO calls.

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Dave Wilson
Sent: Monday, October 26, 2009 12:09 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

If we assume the image is a test image only then I wouldn't be concerned about the map and credentials. We could even supply a default one that is a variation of Sheboygan or something with 1 or 2 layers max. Since the eventual request is server side it could use the server authentication to access and render the map.

I'm more concerned about how you get multiple results back from all sites. I'm guessing the request is a multipart post that processes each server one by one in a loop in the webtier or does it process them all, assemble the results (including any failures) and return one result set?

Dave

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Bruce Dechant
Sent: Monday, October 26, 2009 9:23 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

A ping is supposed to be fast - adding overhead to generate a map image could be slow, but having this optional would get around that. What about security risks of being able to render a map without credentials? Obviously if it is a tiny thumbnail of the map it is not very useful at all - other than to see if the server is there and can render it.

Thanks,
Bruce

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Trevor Wekel
Sent: Monday, October 26, 2009 8:08 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

No problem on the performance metrics.

Martin's suggestion of doing a lightweight render is a good idea. Perhaps we can make this an optional item with the render only occurring if a map definition resource id is supplied as an input parameter. We could just render a small image at the map extents. The various pieces - API version, offline/online, and image could be returned as an xml document with the image returned as a base64 blob. Something like this perhaps:

<Ping>
<Status>Online</Status>
<ApiVersion>2.2</ApiVersion>
<ImageSize>8061</ImageSize>
<Image>[8061 base64 encoded bytes]</Image>
</Ping>

Thanks,
Trevor

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Bruce Dechant
Sent: October 26, 2009 7:55 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

The API version would be nice to have.

I have to agree that performance metrics without credentials I'm not sure I like.

Bruce

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Jason Birch
Sent: Sunday, October 25, 2009 11:00 AM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] Server status/Ping API

I think it would be cool to return API version (2.1, 2.2, etc) as part
of this, but not rev/build.

Would be hesitant to return performance metrics through a non-authenticated api.

Jason

On 2009-10-22, Bruce Dechant <[hidden email]> wrote:

Martin Morrison

RE: Server status/Ping API

Reply Threaded

Works for me...

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Walt Welton-Lair
Sent: Monday, October 26, 2009 12:25 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

How about reducing this to just a legend image? That will still exercise rendering, but it avoids the overhead of making FDO calls.

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Dave Wilson
Sent: Monday, October 26, 2009 12:09 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

If we assume the image is a test image only then I wouldn't be concerned about the map and credentials. We could even supply a default one that is a variation of Sheboygan or something with 1 or 2 layers max. Since the eventual request is server side it could use the server authentication to access and render the map.

I'm more concerned about how you get multiple results back from all sites. I'm guessing the request is a multipart post that processes each server one by one in a loop in the webtier or does it process them all, assemble the results (including any failures) and return one result set?

Dave

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Bruce Dechant
Sent: Monday, October 26, 2009 9:23 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

A ping is supposed to be fast - adding overhead to generate a map image could be slow, but having this optional would get around that. What about security risks of being able to render a map without credentials? Obviously if it is a tiny thumbnail of the map it is not very useful at all - other than to see if the server is there and can render it.

Thanks,
Bruce

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Trevor Wekel
Sent: Monday, October 26, 2009 8:08 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

No problem on the performance metrics.

Martin's suggestion of doing a lightweight render is a good idea. Perhaps we can make this an optional item with the render only occurring if a map definition resource id is supplied as an input parameter. We could just render a small image at the map extents. The various pieces - API version, offline/online, and image could be returned as an xml document with the image returned as a base64 blob. Something like this perhaps:

<Ping>
<Status>Online</Status>
<ApiVersion>2.2</ApiVersion>
<ImageSize>8061</ImageSize>
<Image>[8061 base64 encoded bytes]</Image>
</Ping>

Thanks,
Trevor

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Bruce Dechant
Sent: October 26, 2009 7:55 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

The API version would be nice to have.

I have to agree that performance metrics without credentials I'm not sure I like.

Bruce

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Jason Birch
Sent: Sunday, October 25, 2009 11:00 AM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] Server status/Ping API

I think it would be cool to return API version (2.1, 2.2, etc) as part
of this, but not rev/build.

Would be hesitant to return performance metrics through a non-authenticated api.

Jason

On 2009-10-22, Bruce Dechant <[hidden email]> wrote:

_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

Dave Wilson

RE: Server status/Ping API

Reply Threaded

Works for me. Good suggestion Walt. If it's that quick to render do we need to make it optional?

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Martin Morrison
Sent: Monday, October 26, 2009 10:28 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

Works for me...

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Walt Welton-Lair
Sent: Monday, October 26, 2009 12:25 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

How about reducing this to just a legend image? That will still exercise rendering, but it avoids the overhead of making FDO calls.

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Dave Wilson
Sent: Monday, October 26, 2009 12:09 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

If we assume the image is a test image only then I wouldn't be concerned about the map and credentials. We could even supply a default one that is a variation of Sheboygan or something with 1 or 2 layers max. Since the eventual request is server side it could use the server authentication to access and render the map.

I'm more concerned about how you get multiple results back from all sites. I'm guessing the request is a multipart post that processes each server one by one in a loop in the webtier or does it process them all, assemble the results (including any failures) and return one result set?

Dave

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Bruce Dechant
Sent: Monday, October 26, 2009 9:23 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

A ping is supposed to be fast - adding overhead to generate a map image could be slow, but having this optional would get around that. What about security risks of being able to render a map without credentials? Obviously if it is a tiny thumbnail of the map it is not very useful at all - other than to see if the server is there and can render it.

Thanks,
Bruce

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Trevor Wekel
Sent: Monday, October 26, 2009 8:08 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

No problem on the performance metrics.

Martin's suggestion of doing a lightweight render is a good idea. Perhaps we can make this an optional item with the render only occurring if a map definition resource id is supplied as an input parameter. We could just render a small image at the map extents. The various pieces - API version, offline/online, and image could be returned as an xml document with the image returned as a base64 blob. Something like this perhaps:

<Ping>
<Status>Online</Status>
<ApiVersion>2.2</ApiVersion>
<ImageSize>8061</ImageSize>
<Image>[8061 base64 encoded bytes]</Image>
</Ping>

Thanks,
Trevor

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Bruce Dechant
Sent: October 26, 2009 7:55 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

The API version would be nice to have.

I have to agree that performance metrics without credentials I'm not sure I like.

Bruce

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Jason Birch
Sent: Sunday, October 25, 2009 11:00 AM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] Server status/Ping API

I think it would be cool to return API version (2.1, 2.2, etc) as part
of this, but not rev/build.

Would be hesitant to return performance metrics through a non-authenticated api.

Jason

On 2009-10-22, Bruce Dechant <[hidden email]> wrote:

Bruce Dechant

RE: Server status/Ping API

Reply Threaded

I think it should be optional regardless :)

Bruce

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Dave Wilson
Sent: Monday, October 26, 2009 10:44 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

Works for me. Good suggestion Walt. If it's that quick to render do we need to make it optional?

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Martin Morrison
Sent: Monday, October 26, 2009 10:28 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

Works for me...

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Walt Welton-Lair
Sent: Monday, October 26, 2009 12:25 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

How about reducing this to just a legend image? That will still exercise rendering, but it avoids the overhead of making FDO calls.

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Dave Wilson
Sent: Monday, October 26, 2009 12:09 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

If we assume the image is a test image only then I wouldn't be concerned about the map and credentials. We could even supply a default one that is a variation of Sheboygan or something with 1 or 2 layers max. Since the eventual request is server side it could use the server authentication to access and render the map.

I'm more concerned about how you get multiple results back from all sites. I'm guessing the request is a multipart post that processes each server one by one in a loop in the webtier or does it process them all, assemble the results (including any failures) and return one result set?

Dave

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Bruce Dechant
Sent: Monday, October 26, 2009 9:23 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

A ping is supposed to be fast - adding overhead to generate a map image could be slow, but having this optional would get around that. What about security risks of being able to render a map without credentials? Obviously if it is a tiny thumbnail of the map it is not very useful at all - other than to see if the server is there and can render it.

Thanks,
Bruce

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Trevor Wekel
Sent: Monday, October 26, 2009 8:08 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

No problem on the performance metrics.

Martin's suggestion of doing a lightweight render is a good idea. Perhaps we can make this an optional item with the render only occurring if a map definition resource id is supplied as an input parameter. We could just render a small image at the map extents. The various pieces - API version, offline/online, and image could be returned as an xml document with the image returned as a base64 blob. Something like this perhaps:

<Ping>
<Status>Online</Status>
<ApiVersion>2.2</ApiVersion>
<ImageSize>8061</ImageSize>
<Image>[8061 base64 encoded bytes]</Image>
</Ping>

Thanks,
Trevor

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Bruce Dechant
Sent: October 26, 2009 7:55 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

The API version would be nice to have.

I have to agree that performance metrics without credentials I'm not sure I like.

Bruce

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Jason Birch
Sent: Sunday, October 25, 2009 11:00 AM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] Server status/Ping API

I think it would be cool to return API version (2.1, 2.2, etc) as part
of this, but not rev/build.

Would be hesitant to return performance metrics through a non-authenticated api.

Jason

On 2009-10-22, Bruce Dechant <[hidden email]> wrote:

Jason Birch

Re: Server status/Ping API

Reply Threaded

In reply to this post by Walt Welton-Lair

In my experience, if a map isn't rendering it's often the FDO (connections)
layer that's hung.

2009/10/26 Walt Welton-Lair <[hidden email]>

> How about reducing this to just a legend image? That will still exercise
> rendering, but it avoids the overhead of making FDO calls.
>
> -----Original Message-----
> From: [hidden email] [mailto:
> [hidden email]] On Behalf Of Dave Wilson
> Sent: Monday, October 26, 2009 12:09 PM
> To: MapGuide Internals Mail List
> Subject: RE: [mapguide-internals] Server status/Ping API
>
> If we assume the image is a test image only then I wouldn't be concerned
> about the map and credentials. We could even supply a default one that is a
> variation of Sheboygan or something with 1 or 2 layers max. Since the
> eventual request is server side it could use the server authentication to
> access and render the map.
>
> I'm more concerned about how you get multiple results back from all sites.
> I'm guessing the request is a multipart post that processes each server one
> by one in a loop in the webtier or does it process them all, assemble the
> results (including any failures) and return one result set?
>
> Dave
>
> -----Original Message-----
> From: [hidden email] [mailto:
> [hidden email]] On Behalf Of Bruce Dechant
> Sent: Monday, October 26, 2009 9:23 AM
> To: MapGuide Internals Mail List
> Subject: RE: [mapguide-internals] Server status/Ping API
>
> A ping is supposed to be fast - adding overhead to generate a map image
> could be slow, but having this optional would get around that. What about
> security risks of being able to render a map without credentials? Obviously
> if it is a tiny thumbnail of the map it is not very useful at all - other
> than to see if the server is there and can render it.
>
> Thanks,
> Bruce
>
> -----Original Message-----
> From: [hidden email] [mailto:
> [hidden email]] On Behalf Of Trevor Wekel
> Sent: Monday, October 26, 2009 8:08 AM
> To: MapGuide Internals Mail List
> Subject: RE: [mapguide-internals] Server status/Ping API
>
> No problem on the performance metrics.
>
> Martin's suggestion of doing a lightweight render is a good idea. Perhaps
> we can make this an optional item with the render only occurring if a map
> definition resource id is supplied as an input parameter. We could just
> render a small image at the map extents. The various pieces - API version,
> offline/online, and image could be returned as an xml document with the
> image returned as a base64 blob. Something like this perhaps:
>
> <Ping>
> <Status>Online</Status>
> <ApiVersion>2.2</ApiVersion>
> <ImageSize>8061</ImageSize>
> <Image>[8061 base64 encoded bytes]</Image>
> </Ping>
>
> Thanks,
> Trevor
>
> -----Original Message-----
> From: [hidden email] [mailto:
> [hidden email]] On Behalf Of Bruce Dechant
> Sent: October 26, 2009 7:55 AM
> To: MapGuide Internals Mail List
> Subject: RE: [mapguide-internals] Server status/Ping API
>
> The API version would be nice to have.
>
> I have to agree that performance metrics without credentials I'm not sure I
> like.
>
> Bruce
>
> -----Original Message-----
> From: [hidden email] [mailto:
> [hidden email]] On Behalf Of Jason Birch
> Sent: Sunday, October 25, 2009 11:00 AM
> To: MapGuide Internals Mail List
> Subject: Re: [mapguide-internals] Server status/Ping API
>
> I think it would be cool to return API version (2.1, 2.2, etc) as part
> of this, but not rev/build.
>
> Would be hesitant to return performance metrics through a non-authenticated
> api.
>
> Jason
>
> On 2009-10-22, Bruce Dechant <[hidden email]> wrote:
> > Hi All,
> >
> > The existing Server Admin service has the following APIs that are not
> > officially published but are available to use:
> >
> > GetSiteVersion() - returns the exact MapGuide server version
> > GetSiteInfo() - returns MapGuide server information and OS information
> >
> > Both of these require authentication credentials because of the
> information
> > returned.
> >
> > I was wondering about adding a new API that would not require
> authentication
> > credentials.
> >
> > Example: GetSiteStatus()
> >
> > I would like it to return the server status as either "Offline" or
> "Online"
> > as some of the information.
> >
> > This API could be used as a sort of "ping" if needed.
> >
> > What other non sensitive information do you think we could include with
> this
> > API?
> >
> > Thanks,
> > Bruce
> > _______________________________________________
> > mapguide-internals mailing list
> > [hidden email]
> > http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> >
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>
>
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>

_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

zspitzer

Re: Server status/Ping API

Reply Threaded

my experience is the same as Jason, FDO is usually the problem ( hence
my orginal concerns about the pinned connections, but thats a different thread)

can i throw SNMP into the mix here? rather than re-inventing the wheel,
supporting SNMP would allow straight forward integration into
existing monitoring systems...

On Tue, Oct 27, 2009 at 7:17 AM, Jason Birch <[hidden email]> wrote:

> In my experience, if a map isn't rendering it's often the FDO (connections)
> layer that's hung.
>
> 2009/10/26 Walt Welton-Lair <[hidden email]>
>
>> How about reducing this to just a legend image? That will still exercise
>> rendering, but it avoids the overhead of making FDO calls.
>>
>> -----Original Message-----
>> From: [hidden email] [mailto:
>> [hidden email]] On Behalf Of Dave Wilson
>> Sent: Monday, October 26, 2009 12:09 PM
>> To: MapGuide Internals Mail List
>> Subject: RE: [mapguide-internals] Server status/Ping API
>>
>> If we assume the image is a test image only then I wouldn't be concerned
>> about the map and credentials. We could even supply a default one that is a
>> variation of Sheboygan or something with 1 or 2 layers max. Since the
>> eventual request is server side it could use the server authentication to
>> access and render the map.
>>
>> I'm more concerned about how you get multiple results back from all sites.
>> I'm guessing the request is a multipart post that processes each server one
>> by one in a loop in the webtier or does it process them all, assemble the
>> results (including any failures) and return one result set?
>>
>> Dave
>>
>> -----Original Message-----
>> From: [hidden email] [mailto:
>> [hidden email]] On Behalf Of Bruce Dechant
>> Sent: Monday, October 26, 2009 9:23 AM
>> To: MapGuide Internals Mail List
>> Subject: RE: [mapguide-internals] Server status/Ping API
>>
>> A ping is supposed to be fast - adding overhead to generate a map image
>> could be slow, but having this optional would get around that. What about
>> security risks of being able to render a map without credentials? Obviously
>> if it is a tiny thumbnail of the map it is not very useful at all - other
>> than to see if the server is there and can render it.
>>
>> Thanks,
>> Bruce
>>
>> -----Original Message-----
>> From: [hidden email] [mailto:
>> [hidden email]] On Behalf Of Trevor Wekel
>> Sent: Monday, October 26, 2009 8:08 AM
>> To: MapGuide Internals Mail List
>> Subject: RE: [mapguide-internals] Server status/Ping API
>>
>> No problem on the performance metrics.
>>
>> Martin's suggestion of doing a lightweight render is a good idea. Perhaps
>> we can make this an optional item with the render only occurring if a map
>> definition resource id is supplied as an input parameter. We could just
>> render a small image at the map extents. The various pieces - API version,
>> offline/online, and image could be returned as an xml document with the
>> image returned as a base64 blob. Something like this perhaps:
>>
>> <Ping>
>> <Status>Online</Status>
>> <ApiVersion>2.2</ApiVersion>
>> <ImageSize>8061</ImageSize>
>> <Image>[8061 base64 encoded bytes]</Image>
>> </Ping>
>>
>> Thanks,
>> Trevor
>>
>> -----Original Message-----
>> From: [hidden email] [mailto:
>> [hidden email]] On Behalf Of Bruce Dechant
>> Sent: October 26, 2009 7:55 AM
>> To: MapGuide Internals Mail List
>> Subject: RE: [mapguide-internals] Server status/Ping API
>>
>> The API version would be nice to have.
>>
>> I have to agree that performance metrics without credentials I'm not sure I
>> like.
>>
>> Bruce
>>
>> -----Original Message-----
>> From: [hidden email] [mailto:
>> [hidden email]] On Behalf Of Jason Birch
>> Sent: Sunday, October 25, 2009 11:00 AM
>> To: MapGuide Internals Mail List
>> Subject: Re: [mapguide-internals] Server status/Ping API
>>
>> I think it would be cool to return API version (2.1, 2.2, etc) as part
>> of this, but not rev/build.
>>
>> Would be hesitant to return performance metrics through a non-authenticated
>> api.
>>
>> Jason
>>
>> On 2009-10-22, Bruce Dechant <[hidden email]> wrote:
>> > Hi All,
>> >
>> > The existing Server Admin service has the following APIs that are not
>> > officially published but are available to use:
>> >
>> > GetSiteVersion() - returns the exact MapGuide server version
>> > GetSiteInfo() - returns MapGuide server information and OS information
>> >
>> > Both of these require authentication credentials because of the
>> information
>> > returned.
>> >
>> > I was wondering about adding a new API that would not require
>> authentication
>> > credentials.
>> >
>> > Example: GetSiteStatus()
>> >
>> > I would like it to return the server status as either "Offline" or
>> "Online"
>> > as some of the information.
>> >
>> > This API could be used as a sort of "ping" if needed.
>> >
>> > What other non sensitive information do you think we could include with
>> this
>> > API?
>> >
>> > Thanks,
>> > Bruce
>> > _______________________________________________
>> > mapguide-internals mailing list
>> > [hidden email]
>> > http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>> >
>> _______________________________________________
>> mapguide-internals mailing list
>> [hidden email]
>> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>> _______________________________________________
>> mapguide-internals mailing list
>> [hidden email]
>> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>>
>>
>> _______________________________________________
>> mapguide-internals mailing list
>> [hidden email]
>> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>> _______________________________________________
>> mapguide-internals mailing list
>> [hidden email]
>> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>> _______________________________________________
>> mapguide-internals mailing list
>> [hidden email]
>> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>> _______________________________________________
>> mapguide-internals mailing list
>> [hidden email]
>> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>>
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>

Martin Morrison

RE: Server status/Ping API

Reply Threaded

So let the image have an arg for an FDO connection. If the arg is present, read the FDO, if not use the legend image.

Being able to monitor Mapguide/Apache with SNMP would be the cat's meow...is it doable with the resources we have?

Martin

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Zac Spitzer
Sent: Monday, October 26, 2009 4:57 PM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] Server status/Ping API

my experience is the same as Jason, FDO is usually the problem ( hence
my orginal concerns about the pinned connections, but thats a different thread)

can i throw SNMP into the mix here? rather than re-inventing the wheel,
supporting SNMP would allow straight forward integration into
existing monitoring systems...

On Tue, Oct 27, 2009 at 7:17 AM, Jason Birch <[hidden email]> wrote:

--
Zac Spitzer -
http://zacster.blogspot.com
+61 405 847 168
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

Bruce Dechant

RE: Server status/Ping API

Reply Threaded

SNMP would be great, but far more then adding one API that doesn't require credentials :)

If someone in the community wants to take this on please feel free.

Bruce

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Martin Morrison
Sent: Monday, October 26, 2009 3:04 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

So let the image have an arg for an FDO connection. If the arg is present, read the FDO, if not use the legend image.

Being able to monitor Mapguide/Apache with SNMP would be the cat's meow...is it doable with the resources we have?

Martin

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Zac Spitzer
Sent: Monday, October 26, 2009 4:57 PM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] Server status/Ping API

my experience is the same as Jason, FDO is usually the problem ( hence
my orginal concerns about the pinned connections, but thats a different thread)

can i throw SNMP into the mix here? rather than re-inventing the wheel,
supporting SNMP would allow straight forward integration into
existing monitoring systems...

On Tue, Oct 27, 2009 at 7:17 AM, Jason Birch <[hidden email]> wrote: