Few ideas to help you
When you define a "CodeBuild" project, you can specify which base image it will use to execute your commands. The one you are using is not Ubuntu yet you are trying apt-get. Try a different base image.
Provide us with a better log stream.
Exporting Logs from CloudWatch
I found that the easiest way is to export logs through command-...
So both have their place. On one hand, putting service definitions in the package helps to keep the number of "moving pieces" to a minimum. On the other, it also requires a more complex package build process to at least some degree (like you would have to build your own packages for things instead of using distro packages). If you have the capability to do ...
The typical approach is to use a folder per environment that contains identically named files:
Then parameterize the @PropertySource to use an environment variable such as "env":
I disagree with @levi, you should stick to the 12 factor app method. Leaving configs in the repo scusk. Simple changes to a password or a small setting requires a commit and a pipeline rebuild. That's too much work for something so simple.
The last 3 companies I've worked for are using 'single branch' repos. There is only the master branch, and developers ...
You can use a Jenkinsfile for this. You can add logic with groovy for every condition you've listed above.
You'll want to use a multi-branch pipeline build for sure, and just write in conditions / switches to determine what you want to do based on the current branch. Jenkins provides a global environment variable for all builds: BRANCH_NAME
The job will ...
The best way to deploy prometheus to kubernetes is with the helm chart:
If you haven't used helm yet, its a very simple install to your laptop/etc and the cluster (and the newest version doesn't even require a cluster side install). It takes like 30 seconds. It's a package manager for ...
Your next step will be to identify a solution for container orchestration. For a quick dev test solution, you could host your own docker registry, push your built image to the registry, and add a deployment step that stops the existing container and spins up a new one from your registry.
However, in a production setting there are many other aspects to ...
As far as I understand,
system.cpu.usage is host’s cumulative CPU usage in nanoseconds this includes user, system, idle CPU modes. (the sum of the /proc/stat CPU line)
process.cpu.usage is the cpu usage for the JVM process aka CPU time used by the JVM process
CPU usage aka CPU time is measured by counting the seconds that a CPU spends processing instructions ...
Seems like, because the application has security enabled, the health check was not able to hit the / endpoint and the health check was failing. When I removed the health check block I was able to access the application. I'll add a globally-open health check endpoint and that should fix the problem I think.