Forum Discussion
Notebook Logs
- Anonymous2 years ago
Hi DennesTorres
Thanks for using Fabric Community.
You can add a code cell in your notebook as follows:// Test log4j MDC/NDC // https://github.com/mspnp/spark-monitoring/issues/28 import org.apache.log4j.MDC val LOGGER_PREFIX = "[Gluten]" val logger = org.apache.log4j.LogManager.getLogger(LOGGER_PREFIX + " " + "com.contoso.LoggerExample") logger.info("Hello, info message") logger.warn("Hello, warn message") logger.error("Hello, error message")
You can validate the log here:
Hope this helps. Please let me know if you have any further queries.
DennesTorres is the real king as always.
The only real pain is that (as of today) the tables are ingested in Azure Log Analytics as "Custom Table (classic)", and these tables cannot be added to an Azure Events Hub, which is the only "make-sense" real-time source to be used in a Fabric Eventstream pipeline.
- DennesTorres1 year agoImpactful Individual
Hi,
I never managed to make the code explained here work. But the support to a log analytics emmitter was included in Fabric some time ago. I made a video about it: https://www.youtube.com/watch?v=F8w59GYDEBA&list=PLNbt9tnNIlQ5TB-itSbSdYd55-2F1iuMK&index=17&t=15s
Kind Regards,
Dennes- vgiatti1 year agoFrequent Visitor
Your solution is gold, but still the solution creates Custom Tables into Azure Log Analytics, and that kind of tables as of today cannot be used to fuel Azure Event Hub. Therefore, it is not possible to stream those logs from Azure Log Analytics into a Fabric Lakehouse or Eventhouse.
The partial solution is to set the log retention period on Azure Log Analytics to 2 years, and query them with KQL queries on PBI or directly on ALA.
- HoneHealthMB1 year agoAdvocate I
I found this problematic as well as we've established a pattern in our architecture to get data to Eventhouses via Event Hub. Its clean, reliable, and repeatable.
Have you found any practical way to ingest from LA into eventhouse?