> For the complete documentation index, see [llms.txt](https://docs.groundcover.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.groundcover.com/integrations/data-sources/json-logs.md).

# JSON Logs

{% hint style="info" %}
This feature is only available for BYOC and On-Prem deployment modes.
{% endhint %}

groundcover utilizes a generic HTTP endpoint for logs in JSON format. This can be useful for integration with 3rd party services and additional collectors, or for importing log files manually.

## Sending logs to the endpoint using the data source wizard

In the [data sources page](https://app.groundcover.com/data-sources), search for the JSON Logs entry. Click on it and open the wizard to see a step-by-step guidance.

<figure><img src="/files/mdUMTyax5lmMZP6B0RYi" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/xtcW4wn3j0tCvoT8ujma" alt=""><figcaption></figcaption></figure>

Endpoint and ingestion key are mandatory to get started. We highly recommend to add extra attributes to enrich the logs being sent, such as service name, environment, cluster and source.

Once these parameters will be filled, a cURL command will be available in the following format

```shellscript
curl -X POST "https://example.platform.grcv.io/json/logs" \
    -H 'Content-Type: application/x-ndjson' \
    -H 'Authorization: Bearer gcik_AAAAAAAA_BBBBBBBB_CCCCCCCC_DDDDDDDD' \
    -H 'x-groundcover-service-name: test' \
    --data-binary '{"timestamp": "2025-01-01T10:45:32.123456799Z", "msg": "log message"}'
```

### Monitoring your integration

Once the integration is live, you can check the logs in the [Logs](https://app.groundcover.com/logs) page or the [Explore](https://app.groundcover.com/explore/data-explorer) page, and can set up monitors.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.groundcover.com/integrations/data-sources/json-logs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.