Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

Service Fabric

Do you have an idea, suggestion, or feedback based on your experience with Azure Service Fabric? We would love to hear from you.

Please take a few minutes to submit your feedback in one of the forums available on the right or vote up an idea submitted by another Azure Service Fabric customer. All the feedback shared in these forums are being monitored and reviewed by the Microsoft Azure Service Fabric team.

Please remember this forum is for Azure Service Fabric, and if you have feedback on other Microsoft products, services or platforms, please submit your feedback in the appropriate forum (found on the right hand side).

Thanks for your feedback – we look forward to improving your satisfaction with Azure Service Fabric

  1. Add load balancing for statless service

    With Reverse proxy, we can only work with random chose of instance. It would be good if there is some load balancing strategies. For example round robin. It would be useful for small on premise clusters.

    25 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  2. Fix Disk Space Usage

    Create a setting that will allow users to toggle how many or how long to keep log/trace files. They are growing out of control and taking up gigabytes of space.

    23 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  3. 22 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  4. Be able to add node types after deployment

    When wanting to add new nodetypes to a cluster after deployment either updating the arm template or making the put calls to the provider with new node types the error

    {
    "error": {

    "code": "ManualScaleUpOrDownNotAllowed",
    
    "message": "VMInstance count cannot be modified."

    }
    }

    is returned. The count is not changed for any of the existing nodes,so the error is also a bit misleading.

    21 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Add chaos testing capabilities to the Service Fabric Explorer

    Having the possibility to start basic integrated chaos testing from within the Service Fabric Explorer without having to write any lines of code.

    Feasible ideas would be to shutdown random nodes to see how your system reacts to it.

    21 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Security Groups for Service Fabric Explorer

    For multiple teams that would share Service Fabric clusters it would be nice to set security groups for the applications. This would not allow another team to create and delete another application

    21 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  7. Show current service fabric version on Cluster Essential Page.

    It would be really helpful to see the version of the current Service Fabric version on the Essential Page of the Explorer page.

    20 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Allow multiple configurations of the same service

    We have services that are abstracted well enough that, if the ApplicationManifest allowed it, we could configure the same service with different ConfigOverrides (potentially having different instance/partition counts of each configuration) to handle different workloads. It seems the only way we can accomplish this is to essentially duplicate the entire service with a different name (yes, they can be mostly shared code via a library assembly, but this is more cumbersome than it needs to be) so that it can be imported/configured separately.

    Here is a suggestion that maybe helps illustrate what I am asking for: Suppose that in the…

    20 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Application Parameters Override in VSTS Deploy Task

    The Azure Resource Group Deployment Task in Visual Studio Team Services (VSTS) has a nice Override parameters feature.

    Add a similar parameter called "Application parameter override" to the Service Fabric Application Deployment task for VSTS.

    With the recent additions in VSTS to link Key Vaults to Variable Groups and to scope VSTS Release variables per environment, it becomes more and more common to use VSTS variables for app param overrides.

    20 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Custom Actor's Queue Extesibility

    Custom Actor's Queue Extensibility

    the Actor's message queuing is one of the model's fundamentals

    Exposing extensibility point for Actor's queue replacement
    will allow to developers to address scenario that may not supported on
    the current Actor queuing model.

    developers can use it to alter the queue strategy using
    Azure Service Bus or Azure Queue.

    by doing so the queue will become reliable for cluster crash
    or mistakable deployment (without upgrade)

    the current implementation rely on WCF which may
    make it relative easy by replacing the WCF transport channel
    (similar to the Net MSMQ binding)

    the Actor class can use virtual…

    20 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Stop VMs

    Need the ability to shut down a cluster's VM's to save cost when not in use. For a development/QA environment, it'd make sense to be able to deprovision VM's to save on cost

    19 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Rebalance partitions for stateful services and actors when adding nodes

    Currently, you cannot change the partitioning of a stateful service/actor. I'm forced to anticipate future horizontal scale and create that many partitions, so that when nodes are added to the cluster, load is moved off of hot nodes to the new ones.

    NoSQL databases, such as MongoDB, rebalance the partitions when adding a node. If I"m doing a range partition and have 5 nodes, the range is sliced up into 5 equal(ish) shards. If I add node later, data is migrated until I have 6 equal(ish) shards.

    Having this functionality in Service Fabric for stateful services/actors would allow better horizontal…

    19 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Visual Studio Event Log for Standalone SF Cluster like Azure Clusters and Dev Clusters

    For a StandAlone cluster there isn't an easy way to access the event logs of the whole cluster like when running the services on the development machine or on Azure, it would be good for monitoring to be able to access the live log of a Standalone Cluster.

    19 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  14. Singleton actor-like compute units

    I can see a use for both stateful and stateless units of business logic that are similar to actors, but singletons. I'll call these Units. These would be accessible to clients, Actors and other Units and would be used in a similar way. Some simple examples:

    Stateless:
    var dateProvider = UnitProxy.Create<DateProviderUnit>();
    var date = dateProvider.NowAsync();

    Stateful:
    var idProvider = UnitProxy.Create<IdProviderUnit>();
    var id = idProvider.NextAsync();

    This can be emulated at the moment by using Actors, and using Create with a known ActorId to access the same instance.

    The benefit of making them a 'first class citizen' is that the code would…

    18 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Allow a single machine cluster configuration

    Please remove the requirement of having a cluster of 3 machines on-premise. Some of our clients do not have the need for scaling or reliability. They just want one machine just like a developer has a local cluster to test. It's for deployment to smaller customers of our product.

    17 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Add process id/thread id in details of partition, replica view in explorer

    Add process id/thread id in details of partition, replica view in explorer so that it helps in debugging and also allow taking dump

    17 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  17. virtualMachineScaleSets osProfile certificateUrl should suport URL with default KeyVault secret version.

    Certificate common name often is used with certificate autorotation when we get certificate by subject (Common Name) when Thumbprint may be different. When KeyVault generates new certificate it will provide a new KeyVault secret version and certificate Thumbprint. We use following setting (described in documentation) to set KeyVault certificate URL:
    virtualMachineScaleSets/properties/virtualMachineProfile/osProfile/secrets/vaultCertificates/certificateUrl. However if we set certificate URL without KeyVault version then during Resource Manager template deployment we get the following error: "https://ourproductserver.vault.azure.net/secrets/sslcert/ is not a valid versioned Key Vault Secret URL. It should be in the format https://<vaultEndpoint>/secrets/<secretName>/<secretVersion>."

    From key vault documentation we know that Key Vault Secret…

    17 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Python SDK & Samples

    Support for Python within the templates would be phenominal.

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Option to disable service/app deletion confirmation on local/test clusters

    It would be useful to be able to disable confirmations for deleting/unprovisioning when doing local development. it could just be an option in the cluster

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Execute service fabric .net client code on hosts (build machines) without installing the runtime and sdk

    Short version:

    Provide a nuget package with all of the needed assemblies to run service fabric client applications without installing the whole service fabric runtime and sdk on the host machines. This is especially useful when executing service fabric client code on build servers. Installing the whole sdk and runtime creates unnecessary overhead when working on Continuous Integration/Deployment/Delivery pipelines.

    Long version:

    We have written several tests that check the health status of some service fabric applications. The tests are executed on VSTS hosted agents. All worked well until we decided to upgrade to service fabric version 6.0. Then it turned…

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Service Fabric

Categories

Feedback and Knowledge Base