We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Following-up #3043 we should add some end to end tests to validate that an APM Server is correctly associated with Kibana.
The text was updated successfully, but these errors were encountered:
I think we can implement the following scenario:
Create an agent configuration using the Kibana API, the API is officially documented from 7.7.0 but is available since 7.5.0
PUT https://x.x.x.x:5601/api/apm/settings/agent-configuration
The following HTTP body creates the default agent configuration (a.k.a. All) :
All
{ "service": {}, "settings": { "transaction_sample_rate": 1, "capture_body": "errors", "transaction_max_spans": 100 } }
Fetch the configuration from the APM Server with the Agent configuration API
GET https://y.y.y.y:8200/config/v1/agents?service.name=All
Compare the results:
{ "capture_body": "errors", "transaction_max_spans": "100", "transaction_sample_rate": "1" }
Sorry, something went wrong.
Very good idea!
barkbay
Successfully merging a pull request may close this issue.
Following-up #3043 we should add some end to end tests to validate that an APM Server is correctly associated with Kibana.
The text was updated successfully, but these errors were encountered: