-
Notifications
You must be signed in to change notification settings - Fork 14
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
W-16935769 beta traffic inspection monitoring duke #305
base: latest
Are you sure you want to change the base?
W-16935769 beta traffic inspection monitoring duke #305
Conversation
…ssh://github.com/mulesoft/docs-monitoring into W-16935769-beta-traffic-inspection-monitoring-duke
//end::traffic-inspection-limitations[] | ||
// | ||
// | ||
// |
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.
@bin-shi-mulesoft The prerequisites are listed below
// | ||
//tag::traffic-inspection-limitations[] | ||
|
||
At this time, the Anypoint Monitoring agent that supports traffic inspection is available for Mule instances running on _Linux_. |
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.
Red Hat Linux 7 and onwards.
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.
Can you also add the "Validation" and "Troubleshooting" parts.
+ | ||
---- | ||
./bin/setup | ||
---- |
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.
updated step below, @bin-shi-mulesoft
// | ||
|
||
|
||
// |
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.
ignore this content in tag::NOT-USED-YET[]
Writer's Quality Checklist
Before merging your PR, did you: