Skip to content
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

Fix: use metrics_path instead of path in system tests #14690

Merged
merged 1 commit into from
Nov 25, 2019

Conversation

mtojek
Copy link
Contributor

@mtojek mtojek commented Nov 21, 2019

Issue: #14605

The file test_dropwizard.py should use metrics_path instead of path in system test.

To be verified with CI:
With this approach, there is no breaking changes in any prod config files (metrics_path and path stay as is).

The other approach is to replace all path occurrences with metrics_path, but that requires breaking changes in config schemas.

@mtojek mtojek added :Testing Team:Integrations Label for the Integrations team labels Nov 22, 2019
@mtojek mtojek changed the title WIP: Fix: use metrics_path instead of path in system tests Fix: use metrics_path instead of path in system tests Nov 22, 2019
@mtojek
Copy link
Contributor Author

mtojek commented Nov 22, 2019

Tests are marked as skipped, but in the log you can "success" labels:
https://beats-ci.elastic.co/job/elastic+beats+pull-request+multijob-linux/4084/beat=metricbeat,label=linux-immutable/console

The PR can be either approved or I can go further and totally get rid of "path" config key in favor of "metrics_key". WDYT?

@mtojek
Copy link
Contributor Author

mtojek commented Nov 22, 2019

/cc @jsoriano as he had some thoughts about the approach

@mtojek mtojek force-pushed the 14605-inconsistent-keys branch from 92cf0ea to 5682405 Compare November 25, 2019 09:12
@mtojek mtojek merged commit 4db5135 into elastic:master Nov 25, 2019
mtojek added a commit to mtojek/beats that referenced this pull request Nov 26, 2019
mtojek added a commit that referenced this pull request Nov 26, 2019
* [Metricbeat] Create ActiveMQ module (#14580)

* Generate bootstrap for broker, queue, topic

* Update generated files

* Define metricsets in disabler

* Prepare docker image for ActiveMQ

* Define jolokia endpoint in disabler

* Convert to lightweight module

* Remove downloaded installation bundle

* Fill sample data.json

* Refactor metricset fields

* Update docs

* Fix: do not expose ActiveMQ port

* Fix: mage fmt update

* Dockerfile: define healthcheck

* Move module contents to x-pack

* Fix: move docker-compose definition to x-pack

* Add basic system test

* Fix: update docs

* System tests: topic metrics collected

* Fix: mage fmt update

* System tests: queue, topic metrics collected

* Update docs

* Fix: use compose_host

* Assert that fields are documented

* Fix: typo in metricbeat/docs/modules/activemq.asciidoc

Co-Authored-By: kaiyan-sheng <[email protected]>

* Add CHANGELOG.next entry

* Fix: mage fmt update

* Fix: import stomp in the function scope (#14703)

* Fix: use metrics_path instead of path in system tests (#14690)

* [Metricbeat] Create Kibana dashboards for ActiveMQ module (#14655)

* Kibana dashboard: ActiveMQ broker overview

* Fix: mage fmt update

* Fix: invalid dashboard JSON

* Kibana dashboard: ActiveMQ queues and topics overview

* Add dashboard screenshots

* Enable time units, pct in dashboards

* Adjust PR reference in CHANGELOG.next

* Fix: mage fmt update
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Integrations Label for the Integrations team :Testing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants