We were unable to load Disqus. If you are a moderator please see our troubleshooting guide.

Vadim Khalimovskiy • 3 years ago

Hi there!
How it's working in 2022? Is it still a good option for Seq logging for production env in Azure eco-system or there is some better option for now?

Matt • 3 years ago

Hi
I have not tested this since back when I wrote the post. So I can not speak to it at the moment. Sorry.

Nicholas Blumhardt • 4 years ago

Hi Matteo! Kudos for posting this 😎

Since you wrote it, we've made some improvements aimed at better support for Azure Web Apps/Container Instances (ACI), and for container deployment in general.

There are a few more variables that we recommend setting on the initial deployment to Azure:

* `SEQ_API_CANONICALURI` - the public https:// URL for the Seq server
* `SEQ_FIRSTRUN_ADMINUSERNAME` - a username for the default admin user (`admin`, if not specified)
* `SEQ_FIRSTRUN_ADMINPASSWORDHASH` - a hash of the admin user's initial password, generated by typing into `seq config hash` (this avoids starting up with auth wide open)

* `SEQ_FEATURES_ENABLED` - the value should be `nativemetastore` to use the new metadata store that works better with Azure (Premium) Files storage

Azure Files unfortunately seems to be prone to corruptions with Seq's workload; we recommend Azure Premium Files for even moderately-loaded servers. As of 2022 VMs with managed disks are still the workhorse option in Azure, but Premium Files gets closer to what Seq needs for reliable operation and has fared better, according to reports from customers so far.

HTH!

Mike-E • 3 years ago

Even with Azure Premium Files, my instance not only got corrupted once but TWICE and it is beyond frustrating for me in having to play the role of Azure Architect to figure out how to properly install and configure your otherwise incredible and amazing product. I literally have/had no major traffic, with the average hits around 10-25 visits a day as I am in alpha preview mode. Please fix. :P

Nicholas Blumhardt • 3 years ago

Hi Mike! Unfortunately it looks like there are some differences between Azure Web Apps and Container Instances; although we've seen ACI working well in practice, it seems Web Apps allow some level of instance concurrency ("overlapped recycling"?), which is a problem for Seq (which needs exclusive access to its files).

We still have some more to learn in this space - we're keen to support a serverless hosting model in Azure but given the only filesystems available are SMB-based, it's no walk in the park :-)

Thanks for the note here, but if you're still keen to get this up and running without an MSSQL back-end, shall we pick up the support thread and work through it there?

Mike-E • 3 years ago

Thank you very much for the reply and support Nicholas Blumhardt. I appreciate you putting up with Grumpy McGrumpyfaces such as myself when things go wrong. One last note is that this is not specific to Seq but also other products with such configuration. Learning a bunch here along with you!

macky tolentino • 3 years ago

Hello from the future, I hope you havent turned into a craftsman. Did azure eventually address their SEQ issue or is it something thats still not production ready 8 months later?

Mike-E • 3 years ago

Hey there Future. I had to use an Azure Container Instance configured with Linux to work around this issue. It was a total pain but once I got it running there have been no problems. However that doesn't mean everything is unicorns and rainbows. If something happens w/ the configuration or server I am pretty much in the dark on how to address it as I am totally out of my element w/ *nix. 😬

Sean Tomlins • 4 years ago

We learnt the hard way that this is not suitable for production. We tried to scale up the App Service Plan and our app service died a horrible death. Leading up to this it was very slow compared to VMs. Fair warning to all

Mike-E • 3 years ago

Fair warning x2. I had my instance corrupted not once (which was recoverable) but TWICE (which was NOT recoverable). So frustrated with this and now am going to look into using Sql Server to get this sorted. Inefficient and therefore expensive with time and resources. If Seq wasn't so amazing I would have dumped it already. :P

Simon Holman • 4 years ago

Did you find a suitable alternative? When you say "slow compared to VM's", so you mean running SEQ in a container rather than a VM?

Andrew Allison • 4 years ago

Simple and elegant. Thank you so much for this. I was trying to do the VM version they had in the docs and getting no were. This saved me hours.

SandroRiz • 4 years ago

Great Job Matteo....
Any changes to have more info on how to have the installation with Authentication ?

Matt • 4 years ago

Sorry for the late reply.
I am not sure which part of the Authentication you mean. I think here you will have to consolidate the SEQ Docs for more information. https://docs.datalust.co/do...

I just enabled Username and Password for simple testing.

Marko Žlogar • 4 years ago

thank you. your gide was lifesaver

Matt • 4 years ago

I am glad that it helped :-)