I show how I create the dashboards
Hello everyone. I have an app (v3.9.1) running on aws and I'm trying to setup the jhipster console to monitoring. I was able to install the docker image, but when I try to login I only have one page (the menus don't work) and I have the message
Unable to connect to Elasticsearch at http://jhipster-elasticsearch:9200/.. May be is something simple, but I've been trying to sort this out since yesterday.
not sure the current console support this old version
but it should
@ricardocorassa_gitlab I need details about your app configuration and the commands you use to start the jhipster console in order to help you
@maruthi-adithya I tried but always loads the same page
it also help the question/answers to be correctly formulated and searchable through google in the future
@aluckens hi, there is a Optional Configuration for add frontend-maven should you follow that https://github.com/eirslett/frontend-maven-plugin
When running my jhipster app in dev mode AND with logstash forwarding turned on AND the jhipster-console dockers spun up I get this error
Caused by: com.github.vanroy.springdata.jest.exception.JestElasticsearchException: Cannot execute jest action , response code : 400 , error : {"root_cause":[{"type":"resource_already_exists_exception","reason":"index [user/EugWgt89SFmIpJj0IVFuUg] already exists","index_uuid":"EugWgt89SFmIpJj0IVFuUg","index":"user"}],"type":"resource_already_exists_exception","reason":"index [user/EugWgt89SFmIpJj0IVFuUg] already exists","index_uuid":"EugWgt89SFmIpJj0IVFuUg","index":"user"} , message : null
I’m trying to run the console by following this https://www.jhipster.tech/monitoring/#jhipster-console
when running the yml file, I get the following error:
ERROR: for jhipster-alerter Cannot start service jhipster-alerter: b'OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:402: container init caused \\"rootfs_linux.go:58: mounting \\\\\\"/Users/alejandro/IdeaProjects/jhipster-alerter/config.yaml\\\\\\" to rootfs \\\\\\"/var/lib/docker/overlay2/88d45f6803afafd0f0f1b13e1d922a0b915c6b1c07b40b5cab4c57b76806cfa2/merged\\\\\\" at \\\\\\"/var/lib/docker/overlay2/88d45f6803afafd0f0f1b13e1d922a0b915c6b1c07b40b5cab4c57b76806cfa2/merged/opt/elastalert/config.yaml\\\\\\" caused \\\\\\"not a directory\\\\\\"\\"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type’
Hi, I am new working with Jhipster and working with micro-service. I have done some test with Elk and sipkin and i could registered all the trace and with kibana I can wathched everything, but everything locally, now i am working with a server with basic Auth in ELK. My question is. How could I config the basic Auth with username and password on the application-dev.yml?
thank!!!
thank!!!
Hello everyone, running https://github.com/jhipster/jhipster-console/blob/master/bootstrap/docker-compose.yml I could successfully access jhipster-console. Although I can see instances running on dashboard and metrics- are present with data, the "jvm-dashboard" does not show data about jvm memory, threads...
As far as I could understand jhipster.metrics.jmx.enabled properties is used only for third-party monitoring systems (such as Prometheus). In fact, setting that property causes microservice springboot fail because no other third party monitoring system in in the classpath.
I'm running with jhipster-framework.version 3.0.5.
Did anybody got the same problem?
As far as I could understand jhipster.metrics.jmx.enabled properties is used only for third-party monitoring systems (such as Prometheus). In fact, setting that property causes microservice springboot fail because no other third party monitoring system in in the classpath.
I'm running with jhipster-framework.version 3.0.5.
Did anybody got the same problem?
Hello Guys, I am trying to create the microservice with spring web flux using Jhispter generate with version 6.10.1.
generation works fine, however, when I start service and try to call it from the registry swagger UI, I get "Forbidden /services/reactivemicroservice/reactivemicroservice:75f727caed86aac2799c3322a21b0261/v2/api-docs". I tried with plain microservice(without spring web flux) it works absolutely fine. Can anyone guide me on this ti slove it?.
Thanks,
Kiran
Or is this project deprecated?
[INFO] ESLint: 6.8.0.
[INFO]
[INFO] ESLint couldn't find the config "jhipster" to extend from. Please check that the name of the config is correct.
[INFO]
[INFO] The config "jhipster" was referenced from the config file in "C:.eslintrc.json".
[INFO]
[INFO] If you still have problems, please stop by https://gitter.im/eslint/eslint to chat with the team.
[INFO]
[INFO] npm ERR! code ELIFECYCLE
[INFO] npm ERR! errno 2
[INFO] npm ERR! sandboxreg@0.0.1-SNAPSHOT lint:
[INFO] npm ERR! Exit status 2
[INFO] npm ERR!
[INFO] npm ERR! Failed at the sandboxreg@0.0.1-SNAPSHOT lint script.
[INFO] npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
[INFO]
[INFO] ESLint couldn't find the config "jhipster" to extend from. Please check that the name of the config is correct.
[INFO]
[INFO] The config "jhipster" was referenced from the config file in "C:.eslintrc.json".
[INFO]
[INFO] If you still have problems, please stop by https://gitter.im/eslint/eslint to chat with the team.
[INFO]
[INFO] npm ERR! code ELIFECYCLE
[INFO] npm ERR! errno 2
[INFO] npm ERR! sandboxreg@0.0.1-SNAPSHOT lint:
eslint . --ext .js,.ts[INFO] npm ERR! Exit status 2
[INFO] npm ERR!
[INFO] npm ERR! Failed at the sandboxreg@0.0.1-SNAPSHOT lint script.
[INFO] npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
I try execute with comand jhipster aws
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
C:\WORKSPACE\sandboxreg\node_modules\generator-jhipster\generators\generator-base.js:1590
throw new Error(${msg});
^
Error: Error: Command failed: mvnw -ntp verify -B -Pwar -Pprod
at module.exports.error (C:\WORKSPACE\sandboxreg\node_modules\generator-jhipster\generators\generator-base.js:1590:15)
at C:\WORKSPACE\sandboxreg\node_modules\generator-jhipster\generators\aws\index.js:119:30
at ChildProcess.exithandler (child_process.js:310:5)
at ChildProcess.emit (events.js:311:20)
at ChildProcess.EventEmitter.emit (domain.js:482:12)
at maybeClose (internal/child_process.js:1021:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)C:\WORKSPACE\sandboxreg>eslint . --ext .ts --quiet --fix
'eslint' não é reconhecido como um comando interno
ou externo, um programa operável ou um arquivo em lotes.