In this short blog we explore LogDNA. LogDNA is a DevOps teams to aggregate all of their system and application logs into a single platform. Automatic parsing, natural language search and real-time alerts, let’s get LogDNA up and running with Travis.
Let’s register an account with LogDNA using the
logdna-cli, let’s first install LogDNA from the CLI:
brew install --cask logdna-cli
I’m using macOS for this install, now let’s signup for an account using the CLI:
logdna register (your email account)
You’ll then set your password and then get a confirmation email.
The example use case
Go the example use case I created here. You’ll want to go through some of the files specifically
package.json, and you’ll see my current
.travis.yml looks like this:
language: node_js node_js: "10" sudo: false env: CXX=g++-4.8 addons: apt: sources: - ubuntu-toolchain-r-test packages: - g++-4.8 cache: directories: - node_modules before_install: - npm config set spin false - npm install -g npm@^6 - export DEBUG=logdna* install: - npm install - npm install -g grunt-contrib-copy - npm install -g grunt-curl - npm install -g grunt-eslint - npm install -g grunt-exec - npm install -g grunt-line-remover - npm install -g grunt-mocha-cli - npm install -g grunt-zip - npm install --save-dev load-grunt-tasks - npm install grunt --save-dev script: - grunt test --force
Try and run a build, and if it’s successful you should see something like this:
Remember, this is just a quick example I used, but you can also use LogDNA with your project, I’ve found it very useful for the notifications. There’s various other pluses to add LogDNA to your Travis CI project, and it’s simple to integrate.
There you have it! You’ve just used LogDNA with Travis CI, again I’m glad to be showing the flexibility and ease of use with Travis CI.
As always if you have any questions, any questions at all, please email me at firstname.lastname@example.org.
Happy building, and Happy New Year!