Gateway Logs Service stores logs in one location, so you can discover and resolve issues when debugging. The gateway sends its logs to the service, which stores and filters them. You can then review the logs and sort them based on the filters Gateway Logs Service provides.
For example, the gateway sends logs from other Pelion Edge components, such as DeviceDB, to the service. You can then query the logs generated from DeviceDB. Filters include:
- Account ID.
- Application name.
- Device type.
- Log ID.
- Log type.
- Time stamp.
- Log level, such as info, debug, warning, error and fatal.
To use Gateway Logs Service, you need an access key to access Pelion Edge gateway services. A gateway must have a valid certificate.
Using the service
With Gateway Logs Service, you can:
- Add logs.
- List all logs.
- View logs based on filters.
How it works
Gateway Logs Service uses Elasticsearch as its underlying database. You can use Elasticsearch APIs to store or query the logs to the Elasticseach server.
- Gateway Logs Service only accepts HTTPS connections, which are secured by Secure Sockets Layer (SSL) protocol. It provides privacy and data integrity between two or more communicating applications.
- You can only talk to a gateway if you are part of the account tied to that gateway.
- For gateway domain requests, the gateway authenticaiton server has to confirm whether the request is from a valid gateway.
- All requests made to the API domain must pass through the API gateway, which ensures the request contains a valid access token. The Gateway Logs Service assumes the API gateway handles authentication for API domain requests.