-
Notifications
You must be signed in to change notification settings - Fork 25
Firehose Quickstart
nickstinemates edited this page May 18, 2021
·
12 revisions
- Explain some components, including why you'd want SSL
- -kentik_email field (optional)
- -how to get new relic api key
- -how to get nr account id
- Linux host
- Access to internet
- Docker running
Download the ktranslate image:
docker pull kentik/ktranslate:v2
Send flow data with:
docker run \
-e NEW_RELIC_API_KEY=NRII-$NR_TOKEN \
-e KENTIK_API_TOKEN=$KENTIK_TOKEN \
-p 8082:8082 \
kentik/ktranslate:v2 \
-nr_account_id $NR_ACCOUNT_ID \
-kentik_email [email protected] \
nr1.flow
Do we want to use -name?
sample output
Send VPC logs to New Relic with:
docker run \
-e NEW_RELIC_API_KEY=NRII-$NR_TOKEN \
-e KENTIK_API_TOKEN=$KENTIK_TOKEN \
-p 8082:8082 \
kentik/ktranslate:v2 \
-nr_account_id $NR_ACCOUNT_ID \
-kentik_email [email protected] \
nr1.vpc
Optional: generate SSL cert files via Lets Encrypt or other service.
An example using Certbot would be sudo certbot certonly --standalone
.
Run ktranslate, writing out into the influx format:
docker run \
-v /etc/letsencrypt/live/$MYHOST:/ssl \
-p 8082:8082
kentik/ktranslate:v2 \
-format influx \
-log_level=info \
-ssl_cert_file /ssl/fullchain.pem \
-ssl_key_file /ssl/privkey.pem
Point firehose at this endpoint:
https://kb.kentik.com/v0/Fc19.htm#Fc19-Firehose_Data_Sources
And you should see output. Next steps include sending data into New Relic.