[KONG] - Skywalking Kong agent parameters - more info

[andrewgkew]

Can I get get more of an explanation as to the parameters I can configure for the Kong agent

1. backend_http_uri
2. service_name
3. service_instance_name

I am assuming the backend http uri is the OAP server? But the example is using port 12800?
Also what the service name and instance name are so that I know in my use case what they should be set to

Thanks

[wu-sheng]

I am assuming the backend http uri is the OAP server? But the example is using port 12800?

Yes, it is 12800. Because there is no gRPC core in Nginx stack.

Service name and instance name are basically logic names, you could find the explanations here, https://skywalking.apache.org/docs/main/v8.8.1/en/concepts-and-designs/overview/#why-use-skywalking

[andrewgkew]

Thanks @wu-sheng I am going to put this together and hopefully use the Kong plugin with SkyWalking at another conference next week (Devoxx UK) this time in person but I think its virtual and in person too. Same topic as Kong Summit but just adding another dimension with the gateway in the spans.

[andrewgkew]

Sorry got that wrong here is what we are talking at is a MeetUp at Devoxx: https://www.meetup.com/Kong-LONDON/events/281516512/

[wu-sheng]

Good to see a new presentation about this. Look forward to your recorded video too.

[andrewgkew]

Just a quick one, got the plugin working on EKS cluster :)
Bit of a weird way to install it though (working with Kong engineers to get your 3rd party dependency added)
I might put a PR through for your README.md on how to install the plugin using helm when Kong is deployed with helm on k8s
But thanks for your help, can see kong now in my topology and in my traces 👍

[wu-sheng]

Good to know. If something missed in the doc, please send a pull request to fix.