-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Kong Mesh Integration #21278
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kong Mesh Integration #21278
Conversation
|
This PR does not modify any files shipped with the agent. To help streamline the release process, please consider adding the |
|
Created DOCS-11994 for docs team review 🙂 |
michaelcretzman
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved, with one minor suggestion.
Co-authored-by: Michael Cretzman <[email protected]>
Review from michaelcretzman is dismissed. Related teams and files:
- documentation
- kong_mesh/README.md
|
We ended up dropping this approach for now. See AI-5888. |
What does this PR do?
Kong Mesh is the enterprise version of Kuma.. The Kuma integration can get monitor Kong Mesh just like Kuma. Because of that, we'll use the Kuma integration on the Agent to collect metrics. We'll also use the Kuma logs pipeline to process Kong Mesh logs.

This integration only contains the tile, dashboards, monitors, and saved views. For the rest we're relying on the Kuma integration.
Needs to be merged together with #20876.
JIRA: AI-5888
Motivation
Review checklist (to be filled by reviewers)
qa/skip-qalabel if the PR doesn't need to be tested during QA.backport/<branch-name>label to the PR and it will automatically open a backport PR once this one is merged