Apica LogFlow
  • Overview
  • EULA
    • End User License Agreement
  • Getting Started Guide
    • Deployment guides
  • Architecture
    • Never Block, Never Drop
    • InstaStore
    • Deployment
  • Flow Management
    • Overview
    • Forwarders
    • Mapping Applications
    • Data Transformation
  • Splunk Forwarding
    • Overview
    • Apica UF Proxy App Extension
      • Standalone Instance
      • List of Indexer instances
      • Indexer Discovery
    • Metric indexes
    • Non metric indexes
    • Syslog forwarding
  • Real-time Stream Forwarding
    • Overview
    • AWS Kinesis
    • Azure Eventhub
    • Google Pub/Sub
  • Forwarding To Data Warehouse
    • Overview
    • GCP Bigquery
  • Object Store Forwarding
    • Overview
    • S3 Compatible
    • Azure Blob Storage
  • Forwarding to monitoring tools
    • DataDog Forwarding
    • New Relic Forwarding
    • Dynatrace Forwarding
    • Elasticsearch Forwarding
    • Coralogix Forwarding
    • Azure Log Analytics Forwarding
    • JS Code Forwarding
  • Security Monitor Forwarding
    • Overview
    • Arc Sight
    • RSA New Witness
Powered by GitBook
On this page
  • Pre-requisites
  • Creating the forwarder
  • Enter forwarder configuration
  • Testing the Google PubSub forwarding

Was this helpful?

Export as PDF
  1. Real-time Stream Forwarding

Google Pub/Sub

Google Pub/Sub is the GCP managed service for real-time stream processing

Apica's LogFlow can be used to push data to a PubSub topic with just a few clicks. You can forward data as is, morph the data by stripping down attributes or pick and choose the fields that you want to be sent to the Google PubSub topic

Pre-requisites

You will need the following before you can configure forwarding to Google PubSub

  1. Name of the Google PubSub topic

  2. Project id ( full name not an integer ) for your GCP account project where you created the topic

  3. Service account access JSON

The service account must have pubsub.topics.publish permissions

You can check your service account json permissions with gcloud cli

$ gcloud auth activate-service-account --project=my-project-123 \
--key-file=sevice_account_key_file.json
$ gcloud pubsub topics publish my-gcp-topic-1 --message="hello"
messageIds:
- '6470211179713996'
$ gcloud pubsub subscriptions pull my-gcp-topic-1-sub --auto-ack
┌───────┬──────────────────┬──────────────┬────────────┬──────────────────┐
│  DATA │    MESSAGE_ID    │ ORDERING_KEY │ ATTRIBUTES │ DELIVERY_ATTEMPT │
├───────┼──────────────────┼──────────────┼────────────┼──────────────────┤
│ hello │ 6470211179713996 │              │            │                  │
└───────┴──────────────────┴──────────────┴────────────┴──────────────────┘

Creating the forwarder

We are now ready to create the forwarder

Enter forwarder configuration

Testing the Google PubSub forwarding

You can now test a data replay with a test stream to see if data went through

PreviousAzure EventhubNextOverview

Last updated 1 year ago

Was this helpful?

Create Google PubSub forwarder
Forwarder configuration
Replay data to Google PubSub
Replay status for Google PubSub forwarded data
Visualizing data forwarding to Google PubSub