Utilizing Sensu Plugins Offline

Is it possible to use dynamic assets/plugins offline? I’m trying to use the sensu-jira-handler (sensu-jira-handler versions) in an offline environment where our machines aren’t connected to the internet. However, I cannot get it working. I’ve tried downloading the tar file and placing it in a folder on my machine as well as under a file repo in Red Hat Satellite but both aren’t working.


I’m a little confused…
The jira handler itself probably requires internet access…since it needs to communicate with the publiclly hosted jira service. Oh i guess has atlassian does have self hosted data-center option…cool.

Running manually installed assets should work just fine, you just have to ensure the manually installed asset (and the filesystem location) has appropriate permissions for the sensu user to run the handler. You also have to make sure you have the correct tarball build for the sensu-backend host. You may need to update the sensu-backend service’s executable path to include the location of the handler. How much work you need to do to fix up the filesystem permissions and executable path really depends on where you plan to install the handler executable.

Alternatively, have you thought about running a local network asset server? Since Asset definitions are just sha512 checksums and a url, you have the ability to cache asset build locally and update the Sensu asset resource definition to point to your local asset server url. running in the local network.

Thanks for the response. Would Red Hat Satellite works as the the local network asset server like you had mentioned? I am able to curl and download the file from the repo which contains a URL but the handler still doesnt seem to be working.

What I did was download the tarball file for amd64, upload it to a file repo in red hat satellite, create an asset pointing to the tarball file in satellite as the URL and checksum, then create a handler pointing to the asset that I created.

All the local asset server needs to do is allow http url downloads. That’s it. I can’t tell you if RH Sat allows that or not for non-rpm files. I don’t know how optimized RH Sat is for rpm packages versus just random files. But if RH Sat can serve up a tarball at a static url… that’s all you need. You can get a way with a simple python http server really in a pinch.

Since I am able to download the tarball from red hat satellite I think that will suffice. Is there a way to see the logs for handlers? I’m not sure how to verify the handler works or not other than checking my jira service management project to see if theres any cases created.

right now,
if you bump up debug log output on the backend and should see messages about the handler firing. If the handler returns non-zero status I think it logs a warn or err level msg in the backend…i think.

We’ve got plans to make watching for handler errors easier, we just have to get there.

This might sound like a silly question but how can we bump up the debug log output?

There’s a log-level config setting exposed via cmdline arg and config file.