Jump to content

danc

Members
  • Content Count

    3
  • Joined

  • Last visited

  • Days Won

    1

danc last won the day on July 13 2020

danc had the most liked content!

Community Reputation

1 Neutral

My Information

  • Agent Count
    3000 - 4000 Agents
  1. Never thought to use excel and CONCAT. Good call! I prepped an excel file with all the fields that I would be replacing in the monitor. A1=IPAddress, B1=Circuit Name, etc. I ended up creating 1 monitor as a template and exported it to a sql file. That way I didn't have to rebuild the INSERT INTO statement. Then I just replaced the text with my CONCAT variables. 192.168.1.1 became ",A1," and so on. I ended up having to split the INSERT INTO statement into multiple chunks to support the 255 char limit. The last Cell is basically =CONCAT("",H2," ",I2,"",J2,"",K2,""). Once everything in place
  2. Great post! I like the idea of having 3 boards. It can be difficult separating actionable from non actionable alerts. A few questions... How do you handle alerts that are generated via email from outside of Automate? For example, Meraki alerting if an appliance is down. An email will generate a ticket for a failure notice, but then a separate ticket for a success notice. Do you automate these types of tickets as well? Do all of your techs look at the same service board? Or do they only work tickets that are dispatched / assigned to them? Are your workflows / reporting
  3. Giving them access to the thick client at all is going to be a security / privacy concern. For example, all script names and search names are visible regardless of permissions. I wouldn't call risk of SQL injection a small fear. Any level of script building access is a potential security risk. Monitoring won't help you if the damage is already done. If I were you, I would create a client in Automate and start building out the permissions for a test user account. Then you can log on and see everything they'll have access to.
×
×
  • Create New...