You have setup a job in TeamCity that runs an http request using curl. The job shows green but you’re not seeing the data or expected outcome. In the logs it says “Could not resolve host”. That’s obviously a separate issue, but a disappointing issue is that despite this failure the job reports green as though it succeeded.
Sensu check hooks are a great tool for auto-remediation. There may be cases were you want to attempt multiple actions or scripts to resolve the issue. Say you’re trying to run two scripts from sensu check hooks on sensu 1.7 on Windows. The below does not run both, but will only execute the first script.
I leverage sensu alerts that flow through to PagerDuty and actually wake people up if necessary. This empowers us to respond quickly to customer issues. However for false positives it’s really frustrating to get a phone call for it. Even worse, false positives train team members to start ignoring alerts and not to worry about them. Then the presence of alerts becomes normal and it’s barely more useful than not having any alerts.
Ensure that your alerts are meaningful and actionable. Follow the steps below.
Export data from PagerDuty
Click Incident Volume
From there you can download csv’s to get your data
You’ve setup and configured (or inherited) a bacula installation on CentOS. It seems to be working and not starting fires. How can you check that everything is running as expected?
Look no further than our trusty service command
It will provide the following output.
bacula-dir (pid 2868) is running... bacula-fd (pid 2881) is running... bacula-sd (pid 2894) is running...
This stands for Bacula’s director. As the name implies, this service coordinates all backup and restore jobs that you’ve configured. It’s critical that it can reach out to the below services, which may or may not be co-located.
You’re configuring bacula but notice that there are multiple places to configure a Job and it’s properties. The challenge comes in creating the job or making the appropriate changes to FileSets without experiencing unintended consequences.
JobDefs = JobDefs-Resource-Name If a JobDefs-Resource-Name is specified, all the values contained in the named JobDefs resource will be used as the defaults for the current Job. Any value that you explicitly define in the current Job resource, will override any defaults specified in the JobDefs resource. The use of this directive permits writing much more compact Job resources where the bulk of the directives are defined in one or more JobDefs. This is particularly useful if you have many similar Jobs but with minor variations such as different Clients. A simple example of the use of JobDefs is provided in the default bacula-dir.conf file.
It’s important to remember the architecture of these two concepts. JobDefs were introduced as a way to template and avoid duplication. However every property can be overridden in the Job definition even if it exists in the JobDef definition. This is true for FileSets as well as any property.