Skip to content
  • There are no suggestions because the search field is empty.

How to View App Logs in gPanel

View app logs in gPanel to track actions, monitor integrations, and audit user activities.

Contents

Use the following step-by-step guide to view your organization's app logs via gPanel. 
 

Note: You must be a gPanel Enterprise subscriber in order to access the gPanel API. Please contact us to discuss upgrading your account.

Make an API call

  1. Navigate to the gPanel API developer portal

  2. Click on the APIs box to view the API documentation
    gPanel API Portal homepage for launching and managing developer APIs.

  3. Click on the API you wish to call

    gPanel API directory showing Application Log Viewer and Policy Invoker tools.

  4. Capture the URL of the API you wish to call.

    gPanel OpenAPI definition for GET applog endpoint with HTTP request details.

  5. Now form your API endpoint by concatenating your api as a query parameter at the end of your endpoint, like so: 

https://api.gpanel.promevo.com/v1/applog?apikey=INSERT INFO HERE

Now, use our endpoint to make an API request via HTTP GET. The easiest way is to paste it into a browser, like so: 

Raw JSON response data from the gPanel AppLog API showing application event logs.

Summary

Let’s examine our request and point out a few things.  First, if we visit our API documentation on the developer portal, we’ll see that our API request can take parameters.

gPanel API documentation showing query parameters and response types for the AppLog GET request.

Specifically, we could pass a cursor, a startTime, or endTime.  We didn’t pass either startTime or endTime in our request, which means we want all logs.

Let’s examine this json response, and take note of a few things.

Snippet of gPanel API JSON response showing application log schema and data fields.

Snippet of gPanel API JSON response showing application log schema and data fields.

The response contains a nextPageToken element.  Because our request could potentially return thousands of logs, they do not all get returned in a single response.  This API returns a paged response. This means that we get a subset of the response (200 items in this instance).  In order to get the rest, we use the nextPageToken to make subsequent calls.

If our next response contains a nextPageToken, then we use that one to make another call.  We continue making requests until the response no longer contains a nextPageToken.