---
title: Charmhub | Deploy Grafana Cloud Integrator using Charmhub - The Open Operator
  Collection
description: Deploy the latest version of Grafana Cloud Integrator on any cloud.
url: https://charmhub.io/grafana-cloud-integrator/docs/external-logging
---

# Grafana Cloud Integrator

[Canonical Observability](https://charmhub.io/publisher/observability "View all packages from Canonical Observability")

* [Canonical Observability](https://charmhub.io/publisher/observability "View all packages from Canonical Observability")

Platform:

26.04

24.04

22.04

20.04

3.0/stable rev62-1-gbbf9604

```
juju deploy grafana-cloud-integrator --channel 3.0/stable
```

[Learn to deploy on juju >](https://juju.is/docs/juju/manage-applications)

---

#### Relevant links

* [Homepage](https://charmhub.io/grafana-cloud-integrator)

---

#### Contacts

* [Submit a bug](https://github.com/canonical/grafana-cloud-integrator/issues)

---

Share your thoughts on this charm with the community on discourse.

[Join the discussion](https://discourse.charmhub.io/)

The [**grafana-cloud-integrator**](https://github.com/canonical/grafana-cloud-integrator) charm can be configured to forward telemetry to not only Grafana cloud, but also to any Loki- (or Prometheus-) compatible endpoint. This is generally useful when running the stack on-premise isn’t desired, or when an additional off-premise storage is used for redundancy.

[Vector](https://vector.dev/) is a lightweight ultra-fast tool by the Datadog team written in Rust. It’s excellent for being able to build declarative observability pipelines on the fly. In this example, we’ll use it to send our Loki logs to Elasticsearch.

Using the **grafana-cloud-integrator** charm, we can have **grafana-agent** send logs to **vector**, which transforms it to elastic-compatible non-protobuf log lines with a simple setup!

## [Generate a `FileDescriptorSet` for Loki](https://charmhub.io/grafana-cloud-integrator/docs/external-logging#p-27963-generate-a-filedescriptorset-for-loki)

When setting up **Vector**, you should configure it to expose an http server using the [protobuf definitions](https://github.com/grafana/loki/blob/main/pkg/push/push.proto) of Loki’s PushApi. It’s vital that this protobuf file matches the one used in the version of Grafana Agent you’re using.

Once you have the definitions, you’ll need to generate a `FileDescriptorSet` from the `.proto` file. This can be accomplished using the following command:

```
$ protoc \
    --include_imports \
    --descriptor_set_out /path/to/write/proto.desc \
    --proto_path /path/to/proto/definition/ \
    /path/to/proto/definition/push.proto
```

You will then use the resulting `FileDescriptorSet`, or `.desc` file, to inform Vector how to decode the payload.

> Note: Prior to Loki v2.8.0, the protobuf definition for `PushRequest` is located at [`pkg/logproto/logproto.proto`](https://github.com/grafana/loki/blob/v2.7.7/pkg/logproto/logproto.proto).

## [Vector configuration for ElasticSearch](https://charmhub.io/grafana-cloud-integrator/docs/external-logging#p-27963-vector-configuration-for-elasticsearch)

You’ll need to have the [grafana-agent](https://charmhub.io/grafana-agent) machine charm up and running, with a subordinate relation to the charm you’re observing. If you don’t know how, you can find more information on the linked charm’s documentation.

Use the FileDescriptorSet created earlier (`proto.desc`  in the example above) to configure a Vector “source”:

```
[api]
enabled = true # completely optional, but allows you to use `vector top` and such.

[sources.in]
type = "http_server"
address = "0.0.0.0:8080" # use whatever port you prefer, this is your endpoint.
decoding.codec = "protobuf"
decoding.protobuf.desc_file = "/path/to/write/proto.desc"
decoding.protobuf.message_type = "logproto.PushRequest"

[sinks.my_elasticsearch]
inputs = ["in"]
type = "elasticsearch"
endpoints = [
  "https://user:password@example.com"
]
```

There are multiple additional configuration options for elasticsearch available in [the official docs](https://vector.dev/docs/reference/configuration/sinks/elasticsearch/).

Once that is set up, you’ll simply need to deploy **grafana-cloud-integrator**, configure the aforementioned loki endpoint in the charm, and relate it to **grafana-agent**:

```
juju deploy grafana-cloud-integrator cloud
juju config cloud loki-url=http://some.domain.name:8080
juju relate grafana-agent cloud
```

The logs will then start to seamlessly appear in your ElasticSearch!

## [Vector configuration for Splunk](https://charmhub.io/grafana-cloud-integrator/docs/external-logging#p-27963-vector-configuration-for-splunk)

Same as for ElasticSearch, except we need a “sink” section for splunk, for example:

```
[sinks.my_splunk]
type = "splunk_hec_logs"
inputs = [ "in" ]
endpoint = "https://example.com"
```

There are multiple additional configuration options for splunk available in [the official docs](https://vector.dev/docs/reference/configuration/sinks/splunk_hec_logs/).

---