An HTTP API called Node API is available within each GEL binary, and each binary runs either as a microservice (such as an ingester) or in single-process mode where
target=all. The Node API fetches basic information about that microservice or single process.
Get debug information
This endpoint exports debug information from the GEL target. The response is a ZIP file with the following structure:
debug ├── config.default.yaml ├── config.actual.yaml ├── process-mappings.txt ├── version.json
The files contain:
config.default.yamlThe default configuration file for the requested service.
config.actual.yamlThe actual runtime configuration file for the requested service.
process-mappings.txtShows how memory is being used by the process from the operating system’s perspective.
version.jsonThe version information about the requested service.
Related Enterprise Logs resources
Grafana Enterprise Logs: Logging with security and scale
Join us for this webinar, which will cover: Challenges with logging as organizations scale and the volume of logs explodes, how Grafana Enterprise Logs enables organizations to make logs available to any team members who need them, features available in GEL and how to get access, a live product demo so you can see GEL for the first time
VIDEO: Watch this first-look demo of the new Grafana Enterprise Logs
Based on Loki, Grafana Enterprise Logs is part of the Grafana Enterprise Stack for composing and scaling observability on your own infrastructure.
Introducing Grafana Enterprise Logs, a core part of the Grafana Enterprise Stack integrated observability solution
Powered by the Loki open source project, the Enterprise Logs offering joins metrics and dashboards in our enterprise-ready stack for self-managed observability.