Loggly with YAML

YAML parameters for Loggly

You can find the list with common parameters for all Buddy actions here.

NameTypeDescription
action
Required		StringThe name of the action.
integration_id
Required		IntegerThe ID of the integration.
tags
Required		String[]The list of Loggly tags used for segmentation and filtering.
contentStringThe content of the notification.
type
Required		StringThe type of the action. Should be set to LOGGLY.
trigger_conditionStringDefines when the build action should be run. Can be one of ALWAYS, ON_CHANGE, ON_CHANGE_AT_PATH, VAR_IS, VAR_IS_NOT or VAR_CONTAINS.
trigger_condition_pathsString[]Required when trigger_condition is set to ON_CHANGE_AT_PATH.
trigger_variable_keyStringRequired when trigger_condition is set to VAR_IS, VAR_IS_NOT or VAR_CONTAINS. Defines the name of the desired variable.
trigger_variable_valueStringRequired when trigger_condition is set to VAR_IS, VAR_IS_NOT or VAR_CONTAINS. Defines the value of the desired variable which will be compared with its current value.
disabledBooleanWhen set to true the action is disabled. By default it is set to false.
variablesVariable[]The list of variables defined for this action.

YAML example for Loggly

actions:
  - action: "Loggly notification"
    type: "LOGGLY"
    trigger_time: "ON_EVERY_EXECUTION"
    content: "Notification content"
    tags:
    - "buddy"
    - "${workspace.domain}"
    - "${project.name}"
    - "${execution.pipeline.name}"
    integration_id: 1
variables:
    - key: "ftp_login"
      value: "userLogin123"
      description: "The name of user to FTP."
    - key: "ftp_password"
      value: "secure!14ivLMxPgv7TX6c9+ITX/g=="
      encrypted: true
      description: "The password for ftp."
Questions?

Not sure how to configure a pipeline for your process? Reach out on the live-chat, contact support, or ask our community on our forum.

Sign up for Buddy Digest

Best practices on CI/CD and fresh changelogs delivered weekly to your inbox.