wormhole-explorer/parser
walker-16 96ec327b74
Add opsgenie alertClient to parser (#496)
* Add opsgenie alertClient to parser

* Add metricsClient to processor

* Define critical opsgenie alert parser

* Add parser alert
2023-07-05 15:39:56 -03:00
..
bin Update parser Makefile (#501) 2023-07-04 17:48:47 -03:00
cmd Add opsgenie alertClient to parser (#496) 2023-07-05 15:39:56 -03:00
config Change to deploy prometheus metrics for parser and pipeline (#497) 2023-07-04 15:23:26 -03:00
consumer
http
internal Add opsgenie alertClient to parser (#496) 2023-07-05 15:39:56 -03:00
parser
processor Add opsgenie alertClient to parser (#496) 2023-07-05 15:39:56 -03:00
queue
.env.example
.gitignore Update parser Makefile (#501) 2023-07-04 17:48:47 -03:00
Dockerfile
Makefile Update parser Makefile (#501) 2023-07-04 17:48:47 -03:00
README.md
go.mod Change to deploy prometheus metrics for parser and pipeline (#497) 2023-07-04 15:23:26 -03:00
go.sum Change to deploy prometheus metrics for parser and pipeline (#497) 2023-07-04 15:23:26 -03:00

README.md

Parser

This component is in charge of parsing the VAA payload and persists it.

VAA parsing is delegated to external service so that users can add custom parsers in the external service without affecting this service.

Usage

Service

parser service

Backfiller

parser backfiller [flags]

Command-line arguments

  • --end-time string maximum VAA timestamp to process (default now)
  • --log-level string log level (default "INFO")
  • --mongo-database string mongo database
  • --mongo-uri string mongo connection
  • --page-size int VAA payload parser timeout (default 100)
  • --start-time string minimum VAA timestamp to process (default "1970-01-01T00:00:00Z")
  • --vaa-payload-parser-timeout int maximum waiting time in call to VAA payload service in second (default 10)
  • --vaa-payload-parser-url string VAA payload parser service URL

Running parser as service with localstack

Here are some aws commands to configure localstack with the necessary resources

Config sns topic

aws --profile localstack --endpoint-url=http://localhost:4566 sns create-topic --name vaas-pipeline.fifo  --attributes FifoTopic=true,ContentBasedDeduplication=false

Config SQS FIFO with dead letter queue localstack

aws --profile localstack --endpoint-url=http://localhost:4566 sqs create-queue --queue-name=wormhole-vaa-parser-dlq-queue.fifo --attributes "FifoQueue=true"
aws --profile localstack --endpoint-url=http://localhost:4566 sqs create-queue --queue-name=wormhole-vaa-parser-queue.fifo --attributes FifoQueue=true,MessageRetentionPeriod=3600,ReceiveMessageWaitTimeSeconds=5,VisibilityTimeout=20,RedrivePolicy="\"{\\\"deadLetterTargetArn\\\":\\\"arn:aws:sqs:us-east-1:000000000000:wormhole-vaa-parser-dlq-queue.fifo\\\",\\\"maxReceiveCount\\\":\\\"2\\\"}\""

Subscribe SQS FIFO to vaas-pipeline.fifo topic

aws --profile localstack --endpoint-url=http://localhost:4566 sns subscribe --topic-arn arn:aws:sns:us-east-1:000000000000:vaas-pipeline.fifo --protocol sqs --notification-endpoint http://localhost:4566/000000000000/wormhole-vaa-parser-queue.fifo

Check message in the dead letter queue localstack

aws --profile localstack --endpoint-url=http://localhost:4566 sqs receive-message --queue-url=http://localhost:4566/000000000000/wormhole-vaa-parser-dlq-queue.fifo