Hello Skyline Team | Dojo Community,
DataMiner's C#-based automation, protocols, QAction framework and low-code capabilities have served the platform well over the years. However, Python has become the de facto language for automation, AI/ML integration, data engineering, orchestration and operational tooling across the wider industry.
What is Skyline's roadmap for introducing native Python support within DataMiner, either alongside or as an alternative to C# for Automation Scripts, Protocol Development, GQI extensions, connectors, low-code applications, and operational workflows?
Specifically:
- Is native Python execution currently being considered for future DataMiner releases?
- Would Skyline envisage Python as:
-
- A first-class scripting language within DataMiner?
- A supported runtime for Automation Scripts?
- A framework for Protocol/Connector development?
- An integration layer for AI and Data Science workloads?
- What are the primary technical challenges preventing broader Python adoption today? Security, performance, sandboxing, multi-agent execution, or backward compatibility challenges?
- Are there any plans to expose DataMiner APIs, GQI, DOM, Automation or Data Aggregator components through a Python SDK comparable to today's C# development model?
Thanks so much for your time to do real justice to my query Jan-Klass K.!!!
The availability of Python for connector-based data acquisition is encouraging, and the forthcoming Protocol Buffers-based API is particularly interesting from an integration and automation perspective.
While I appreciate the current focus on connector-based Python and the planned protobuf API, has Skyline considered introducing a controlled Python execution framework for Automation Scripts or GQI extensions, particularly for use cases such as data analytics, anomaly detection, AI workflows, orchestration, and operational automation?
I say this because many OSS organizations today have significantly greater Python expertise than.NET expertise, and lowering the barrier to operational scripting could accelerate innovation without necessarily replacing the existing C# framework.
For me, the protobuf announcement is the real headline. If delivered as described in 2027, it could ultimately have a bigger impact than native Python QActions because it would open DataMiner to Python services, AI agents, and external automation ecosystems through a language-neutral interface, without requiring Skyline to fundamentally re-engineer the platform around an additional runtime. It feels like a pragmatic approach that preserves the current development model while enabling broader adoption of modern automation and AI-driven workflows.