FIWARE Lab, access to wirecloud log
How can I read information from FI-LAB WireCloud log?
I can read information from widgets logs, but how can I debug information from an operator?
Is there an way to detect if operator can't connect to source?
Solution
Currently, WireCloud displays an error icon when an operator logs an error message:
You can click on the alert icon for accessing log information. Also those errors should be displayed on the workspace view:
Currently WireCloud is missing an option for accessing those logs if the operator doesn't log any error. I've created a ticket in the WireCloud's issue tracker for adding such an option.
Note: The ticket was closed and now it is possible to access the logs without having to wait for an error.
- Orion context broker doesn't create tenant databases "on the fly"
- Connect system which includes OPC UA IoT Agent, Orion Context Broker. Cygnus and Historic data with Postgres
- ERROR: Pool overlaps with other one on this address space
- Displaying Irrelevant Sensor Data in FIWARE Orion When Using IoT Agent-JSON and Mosquitto
- Get all Fiware-ServicePath for a specific Fiware-Service
- FIWARE PEP Proxy Wilma server fails to start
- FIWARE Orion-LD upsert replace endpoint: only attributes or completely (including type)?
- FIWARE FIROS Publish cmd_vel from Non-ROS-World
- IoTAgent (JSON) over MQTT doesn't receive measurements from mosquitto
- Orion sending error message "connection failed, after 100 retries"
- Orion-ld fails to establish a connection with the MongoDB Community Operator due to a connection string issue
- How to get the missing table Schema while using quantumleap in cratedb using orion LD context broker though the subscriptions are working?
- yum error "Cannot retrieve metalink for repository: epel. Please verify its path and try again" updating ContextBroker
- Specifying attributes to be aggregated by STHSink
- Why Orion-ld after 0.8.0 is not supporting the formation of service/subservice in quantumleap logs?
- issues configuring a device via bidirectional attributes using IOT agent JSON and Orion LD
- Error downloading and installing Java JDK in CentOS (FIWARE)
- Context provider application: MongoDB connection unsuccessful
- How to maintain a FIWARE apikey?
- How to get the servicePath from /v2/entities GET call
- Orion APIs authentication through Keycloak
- My dockerized service doesn't receive the notification sent by Orion Context Broker
- How to send massive data of sensors in Orion
- Notify python orion/quantumleap subscription changes
- Can I send a notification in the creation and deletion of an entity?
- HTTP POST request gets transformed to GET request
- Orion APIs authorization through Keycloak
- Fiware orion /op/query endpoint working explaination
- Subscription between Orion context broker and Quantumleap works, but table is not created in CrateDB
- Calling external APIs through fiware orion context broker to validate using keyrock