Skip to content
Discussion options

You must be logged in to vote

The missing piece is the gRPC server. The socket source reads TCP data, and its Protobuf decoder decodes messages using your descriptor. It does not implement the Cisco gRPC service or unwrap its HTTP/2 transport.

Your Go server can act as a bridge: have it send each decoded JSON object as one compact, newline-terminated line over TCP to Vector:

sources:
  cisco_json:
    type: socket
    mode: tcp
    address: 0.0.0.0:9000
    framing:
      method: newline_delimited
    decoding:
      codec: json

sinks:
  console:
    type: console
    inputs: [cisco_json]
    encoding:
      codec: json

Telegraf's Cisco MDT input is another receiver that supports this protocol. You're welcome to open…

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by pront
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
source:socket Anything `socket` source related domain:networking Anything related to Vector's networking domain:codecs Anything related to Vector's codecs (encoding/decoding)
2 participants