Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-8523

[fiware-stackoverflow] Log levels in IoT Agent UL

        Details

        • Type: Monitor
        • Status: Closed
        • Priority: Major
        • Resolution: Done
        • Affects Version/s: None
        • Fix Version/s: 2021
        • Component/s: FIWARE-TECH-HELP
        • Labels:

          Description

          Created question in FIWARE Q/A platform on 11-04-2017 at 15:04
          Please, ANSWER this question AT http://stackoverflow.com/questions/43346885/log-levels-in-iot-agent-ul

          Question:
          Log levels in IoT Agent UL

          Description:
          I'm using IoTA-UL in Fiware.

          I need to know what messages sent to IoTA-UL were well received and what don't (i.e. because of API KEY were invalid or ultralight message were malformed because the sender included some attribute that doesn't exist).

          Right know I'm using DEBUG log level, but the log it's eating my disk. Is there any way to log what I want? FATAL, ERROR, INFO and WARN log levels don't do it.

            Activity

            Descending order - Click to sort in ascending order
            fla Fernando Lopez made changes -
            Fix Version/s 2021 [ 12600 ]
            veronika Veronika Vlnkova made changes -
            HD-Enabler IoT Broker [ 10885 ]
            fla Fernando Lopez made changes -
            Resolution Done [ 10000 ]
            Status Answered [ 10104 ] Closed [ 6 ]
            fla Fernando Lopez made changes -
            Assignee Backlog Manager [ backlogmanager ]
            backlogmanager Backlog Manager made changes -
            Status In Progress [ 3 ] Answered [ 10104 ]
            backlogmanager Backlog Manager made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            backlogmanager Backlog Manager made changes -
            Field Original Value New Value
            Component/s FIWARE-TECH-HELP [ 10278 ]
            backlogmanager Backlog Manager created issue -

              People

              • Assignee:
                backlogmanager Backlog Manager
                Reporter:
                backlogmanager Backlog Manager
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: