Ad Widget

Collapse

Web Scenario HTTP Proxy mass update

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Richie
    Junior Member
    • Jul 2017
    • 2

    #1

    Web Scenario HTTP Proxy mass update

    Hello,

    I'm still kinda new to using Zabbix and slowly adding devices and trying things out as a proof of concept, but I ran into a snag, I started working on setting up a few Web Scenarios and noticed that there is no way to perform Mass Update when it comes to Web Scenarios, so does anyone know of a way to perform this kind of task, since Passwords for HTTP Proxy are likely to change and it would not be fun updating each individually for 100+ scenarios? Or if it's possible to make it a variable so that I can update a single point when it comes time to change the password?

    Currently running on Zabbix 3.0 and in process of preparing for the upgrade to 3.2, since this is only a proof of concept type of deal, it's mainly a project I work on, in my spare time.
  • batchenr
    Senior Member
    • Sep 2016
    • 440

    #2
    Originally posted by Richie
    Hello,

    I'm still kinda new to using Zabbix and slowly adding devices and trying things out as a proof of concept, but I ran into a snag, I started working on setting up a few Web Scenarios and noticed that there is no way to perform Mass Update when it comes to Web Scenarios, so does anyone know of a way to perform this kind of task, since Passwords for HTTP Proxy are likely to change and it would not be fun updating each individually for 100+ scenarios? Or if it's possible to make it a variable so that I can update a single point when it comes time to change the password?

    Currently running on Zabbix 3.0 and in process of preparing for the upgrade to 3.2, since this is only a proof of concept type of deal, it's mainly a project I work on, in my spare time.
    can you use macro instead ?
    like {$HTTP_PASS}
    and then in Administration -> General -> drop down menu
    choose : Macros

    {$HTTP_PASS} someP@ss

    Comment

    • Richie
      Junior Member
      • Jul 2017
      • 2

      #3
      Ah, as I said I'm kinda new, didn't know that was a thing... I believe that method will work for me, now I just need to figure out the format I need to use to work with my company proxies, will take some tinkering around but so far just putting in the line below still gives me response code 407.

      http://domain\{$HTTP_USER}:{$HTTP_PASS}:@proxy.example.co mort

      Now I noticed in the field there are [] around certain parts, are those actually needed? I've been looking through the documentation and just can't find anything that states if it needs to be there or not

      Comment

      • batchenr
        Senior Member
        • Sep 2016
        • 440

        #4
        Originally posted by Richie
        Ah, as I said I'm kinda new, didn't know that was a thing... I believe that method will work for me, now I just need to figure out the format I need to use to work with my company proxies, will take some tinkering around but so far just putting in the line below still gives me response code 407.

        http://domain\{$HTTP_USER}:{$HTTP_PASS}:@proxy.example.co mort

        Now I noticed in the field there are [] around certain parts, are those actually needed? I've been looking through the documentation and just can't find anything that states if it needs to be there or not

        https://www.zabbix.com/documentation...web_monitoring
        just try and see whats work,
        i dont have much experience in web Scenario but just try what you feel and see

        Comment

        Working...