ffe339ae31
- Moved all settings in Marvel from `marvel.*` to `xpack.monitoring.*` - Cleaned up marvel settings in general - they're all now under `MarvelSettings` class - fixed some integration tests along the way (they were configured wrong and never actually tested anything) - Updated the docs accordingly - Added `migration-5_0.asciidoc` under the Marvel docs to explain how to migrate from Marvel 2.x to XPack 5.0. - Replaced all `marvel` mentions in the logs to `monitoring` - Removed the `xpack.monitoring.template.version` setting from the templates - renamed the templates to `monitoring-es-data.json` and `monitoring-es.json` - monitoring indices are now `.monitoring-es-<version>-data` and `.monitoring-es-<version>-<timestamp>` Original commit: elastic/x-pack-elasticsearch@17f2abe17d |
||
|---|---|---|
| .. | ||
| .esvm-shield-config | ||
| .esvmrc | ||
| readme.txt | ||
readme.txt
Running ESVM with Shield Upgrade/Install: npm install esvm -g Running: 1) cd to elasticsearch-shield/dev-tools/esvm 2) run esvm a) For native users esvm b) For openldap users esvm oldap c) For active directory users esvm ad Users and roles are stored in .esvm-shield-config Troubleshooting: - elasticsearch is installed under ~/.esvm/<version> - turn on debug in ~/.esvm/1.4.1/config/logging.yml - esvm --fresh will reinstall ES - plugins will not re-install, you can remove them manually by ~/.esvm/1.4.1/bin/elasticsearch-plugin remove shield - errors during startup will not show up. If esvm fails startup look in ~/.esvm/1.4.1/logs/*