Windows Azure Integration Pack
Greetings!
Feel free to suggest stories and vote for the existing ones to help us determine what will go in the release of the Enterprise Library 5.0 Windows Azure Integration Pack.
Please note this list may not always represent the actual priority list for the patterns & practices development team. It also does not constitute any commitments.
There are at least 4 pages of stories. Make sure to review all of them.
10 results found
-
Access to Diagnostics Agent
The diagnostics agent is currently an distant service from which you can only retrieve data by sending it requests.
What I would like to see is that I can subscribe to either queues and topics or directly subscribe to an event which allows me to capture the diagnostics data as it happens. I would also like to see a solid logging API which reports directly to the diagnostics agent rather that to a custom data store. This allows me to to get unified diagnostics info which covers server, service and custom code messages.
It also allows for 3rd party service…4 votes -
Diagnostics: correlations
As an administrator, I'd like to correlate the logs generated with the performance counters I collect from the instances through Azure Diagnostics subsystem.
8 votes -
Diagnostics: Best Practices / Trend Analyzer
As a developer I would like the Azure service to be able to analyze my application and make recommendation for performance and productivity improvements based upon usage and trends.
7 votes -
Diagnostics: cleanup mechanism for WAD tables
As an administrator I want to have a policy-based mechanism to purge the entries in the WAD tables so that I can optimize the usage of storage. The policies should consider kind of entry, severity, age, etc.
13 votes -
Diagnostics: move older entries from Azure Storage
As a developer I want my log entries stored in Azure Storage to be transferred to a Remote Logging Service (or any other trace listener) based on the number of items OR age OR absolute size so that I could optimize my logging strategy AND archive my log entries to a on-premises data store.
9 votes -
Diagnostics: remote logging service
As a developer I want to easily forward my log entries to a remote service so that I can reuse my current remote logging service infrastructure.
8 votes -
Diagnostics: support formatter for system diagnostics listener
As a developer I want to specify a formatter for my log entries that are sent to Azure Diagnostics.
4 votes -
Diagnostics: send entries to queuing system
As a developer I want to send my log entries to a queuing system (Azure Queue, AppFabric Service Bus Queue/Topic, or others - please comment on which queue implementation you're interested in being supported).
4 votes -
Diagnostics: runtime change API
As a developer I want to have a change API for the Logging Application Block so that I can switch to different levels of logging verbosity (from being completely disabled, to logging every piece of debug info).
2 votes -
Diagnostics: rolling mechanism when logging to Azure Storage
As a developer I want to have a rolling mechanism for my log entries stored in Azure Storage based on the number of items OR age OR absolute size so that I can optimize my logging strategy.
1 vote
- Don't see your idea?