Ad Widget

Collapse

Description Filed is broken

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • jayapradha
    Junior Member
    • May 2017
    • 4

    #1

    Description Filed is broken

    Hi Team,

    Im created a web scenario and when i create a trigger i give the full URL in the description field .We have a ticketing tool in place and we have included the email id for ticketing tool in the notification section of an alert in zabbix. Now the problem is , the description comes broken in the ticketing console.

    for example: in the trigger section on zabbix: www.abcd.status.com
    in the ticket description it is: www.abcd.sta

    Its not complete. Not sure why. We recently upgraded zabbix server fom 2.2 to 3.1.

    please help me fixing this issue.
  • batchenr
    Senior Member
    • Sep 2016
    • 440

    #2
    Originally posted by jayapradha
    Hi Team,

    Im created a web scenario and when i create a trigger i give the full URL in the description field .We have a ticketing tool in place and we have included the email id for ticketing tool in the notification section of an alert in zabbix. Now the problem is , the description comes broken in the ticketing console.

    for example: in the trigger section on zabbix: www.abcd.status.com
    in the ticket description it is: www.abcd.sta

    Its not complete. Not sure why. We recently upgraded zabbix server fom 2.2 to 3.1.

    please help me fixing this issue.
    if you can see the full name at zabbix trigger- maybe the issue with the ticketing ?
    how do you send it to the ticketing service ?
    can you show the action trigger massage ?

    Comment

    • jayapradha
      Junior Member
      • May 2017
      • 4

      #3
      Hi Team,

      We have a mail ID set up for the ticketing section and we have mentioned that in the action field on zabbix. I have attached few snapshots for your verification.

      Thank you,
      Jayapradha

      Comment

      • jayapradha
        Junior Member
        • May 2017
        • 4

        #4
        Team,

        I havent heard back from you. Please clarify my questions. your response is awaiting.

        Thank you

        Comment

        • batchenr
          Senior Member
          • Sep 2016
          • 440

          #5
          Originally posted by jayapradha
          Team,

          I havent heard back from you. Please clarify my questions. your response is awaiting.

          Thank you
          im not sure what can cut this message.
          but you can try this :

          vi /etc/php.ini

          change this values:
          max_execution_time = 600
          max_input_time = 600
          memory_limit = 256M
          post_max_size = 32M
          upload_max_filesize = 16M
          date.timezone = Asia/Kolkata (your machine timezone)

          other that that.. idk seems like limit issue or in zabbix or in ticketing

          Comment

          • jayapradha
            Junior Member
            • May 2017
            • 4

            #6
            Description Filed is Broken

            Team,

            We tried changing these config values and it did not help. Please suggest the next course of action.

            Comment

            • batchenr
              Senior Member
              • Sep 2016
              • 440

              #7
              Originally posted by jayapradha
              Team,

              We tried changing these config values and it did not help. Please suggest the next course of action.
              look, if you navigate this action to your mail do you have cuts there ?
              if not its something to do with zabbix and this ticketing

              i think your ticketing program have subject limitation.
              check it out.

              Comment

              • status ocena
                Junior Member
                • Oct 2022
                • 1

                #8
                We have a mail ID set up for the ticketing section and we have mentioned that in the action field on zabbix. I have attached few snapshots for your verification.

                Comment

                Working...