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

[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 https://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

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        2h 58m 1 Backlog Manager 22/May/17 6:04 PM
        In Progress In Progress Answered Answered
        2h 59m 1 Backlog Manager 22/May/17 9:04 PM
        Answered Answered Closed Closed
        3d 12h 47m 1 Fernando Lopez 26/May/17 9:51 AM
        fla Fernando Lopez made changes -
        Fix Version/s 2021 [ 12600 ]
        fla Fernando Lopez made changes -
        Resolution Done [ 10000 ]
        Status Answered [ 10104 ] Closed [ 6 ]
        fla Fernando Lopez made changes -
        HD-Enabler IDAS [ 10884 ]
        Description
        Created question in FIWARE Q/A platform on 11-04-2017 at 15:04
        {color: red}Please, ANSWER this question AT{color} https://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.
        Created question in FIWARE Q/A platform on 11-04-2017 at 15:04
        {color: red}Please, ANSWER this question AT{color} https://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.
        HD-Chapter IoT [ 10839 ]
        fla Fernando Lopez made changes -
        Assignee Backlog Manager [ backlogmanager ]
        Hide
        backlogmanager Backlog Manager added a comment -

        2017-05-22 21:05|UPDATED status: transition Answered| # answers= 1, accepted answer= False

        Show
        backlogmanager Backlog Manager added a comment - 2017-05-22 21:05|UPDATED status: transition Answered| # answers= 1, accepted answer= False
        backlogmanager Backlog Manager made changes -
        Status In Progress [ 3 ] Answered [ 10104 ]
        Hide
        backlogmanager Backlog Manager added a comment -

        2017-05-22 18:05|UPDATED status: transition Answer| # answers= 1, accepted answer= False

        Show
        backlogmanager Backlog Manager added a comment - 2017-05-22 18:05|UPDATED status: transition Answer| # answers= 1, accepted answer= False
        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 ]
        Hide
        backlogmanager Backlog Manager added a comment -

        2017-05-22 15:07|CREATED monitor | # answers= 1, accepted answer= False

        Show
        backlogmanager Backlog Manager added a comment - 2017-05-22 15:07|CREATED monitor | # answers= 1, accepted answer= False
        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: