I have installed package for snapshot debugger and also made changes to applicationinsight.config. but when i see exception there is showing Collect debug snapshots.
I'm also facing this issue. followed this link for installation https://learn.microsoft.com/en-us/azure/application-insights/app-insights-snapshot-debugger. but in Azure portal, not showing "open Debug snapshot". only showing "collect snapshots" and on clicking this link redirecting to above mentioned url.
Managed to get this working by following these steps:
Install the SnapshotCollector nuget package in your website (Config can be found in the end of this post) https://www.nuget.org/packages/Microsoft.ApplicationInsights.SnapshotCollector
(IMP) - Publish in debug mode, make sure that the pdb files are deployed (You can check from the 'preview' option)
<Add Type="Microsoft.ApplicationInsights.SnapshotCollector.SnapshotCollectorTelemetryProcessor, Microsoft.ApplicationInsights.SnapshotCollector">
<!-- The default is true, but you can disable Snapshot Debugging by setting it to false -->
<IsEnabled>true</IsEnabled>
<!-- Snapshot Debugging is usually disabled in developer mode, but you can enable it by setting this to true. -->
<!-- DeveloperMode is a property on the active TelemetryChannel. -->
<IsEnabledInDeveloperMode>true</IsEnabledInDeveloperMode>
<!-- How many times we need to see an exception before we ask for snapshots. -->
<ThresholdForSnapshotting>1</ThresholdForSnapshotting>
<!-- The maximum number of snapshots we collect for a single problem. -->
<MaximumSnapshotsRequired>3</MaximumSnapshotsRequired>
<!-- The maximum number of problems that we can be tracking at any time. -->
<MaximumCollectionPlanSize>50</MaximumCollectionPlanSize>
<!-- How often to reset problem counters. -->
<ProblemCounterResetInterval>24:00:00</ProblemCounterResetInterval>
<!-- The maximum number of snapshots allowed per day. -->
<SnapshotsPerDayLimit>30</SnapshotsPerDayLimit>
<!--Whether or not to collect snapshot in low IO priority thread.-->
<SnapshotInLowPriorityThread>true</SnapshotInLowPriorityThread>
</Add>
Related
I want to Share the AppDynamic's Dashboards in an external website under an <iframe> so that the reports(statistics) can be visible without logging into the AppDynamic tool on an external website.
Requirements :
Need to get the Dashboard's Public URL (so that it can work under iframe without asking the login ID/pass )
I tried doing this "Sharing a Custom Dashboard"
By clicking the "copy shared URL" I got the AppDynamics' particular dashboard's URL
Whenever I run that URL on Chrome, it gives the following error :
Uncaught Error: Load timeout for modules: shared/SharedModuleCode
http://requirejs.org/docs/errors.html#timeout
and when I try on IE (Internet Explorer) , it throws this error :
Content was blocked because it was not signed by a valid security certificate.
For more information, see “About Certificate Errors” in Internet Explorer Help."
On Other tools like Splunk and Sitecatalyst there is a concept of Sharing the reports by embedded URLs. Not sure how AppDynamic works
Thanks.
I am not exactly sure what the problem is, but I just tried it with AppDynamics Controller Version 4.2 to share a custom dashboard and open the shared Link in a different browser and I didn't need to put in any credentials. Maybe AppDynamics Version 3.9 had a bug (assuming you used version 3.9 according to the docs link you posted)
Here is what I did:
Toolbar --> Dashboard & Reports --> Chose a dashboard --> Switch to edit mode -->
Actions --> Share Dashboard --> Action (again) --> Open Shared URL in new window -->
Make Browser full screen
I'm using Sitecore 7.0 and there is an publishing ribbon.
If I select item on the left panel and click big ribbon on the top of tool box, it shows two options, Publish site and Publish Item.
I'd like to make sure the difference between "Republish" in Publish Site and "Republish" in Publish Item.
Also, I know that if site publishes, it clears all caches.
Does the cache clear when I use "Republish" in Publish Item option as well??
Both you do the same thing, the difference is only as the name says, Republish Site will republish all items while republish item will only republish the selected item.
The difference between smart, incremental and republish you can see here:
http://www.sitecoreinsight.com/sitecore-publish-site-tool-publishing-modes/
And about the cache, yes, it always clear the cache :)
You can check that in a event handler on your web.config file. That is the proccess responsible for it and it is fired when any type of publish ends.
<event name="publish:end">
<handler type="Sitecore.Publishing.HtmlCacheClearer, Sitecore.Kernel" method="ClearCache">
<sites hint="list">
<site>website</site>
</sites>
</handler>
</event>
UPDATE:
It clears all HTML cache for the list of sites you see in the configuration above. Publishing does not affect the items cache, I actually don't know what Sitecore does to renew such cache.
There is a tool where you can check the cache status:
http:// your domain /sitecore/admin/cache.aspx
Also take a look at this post, it has a good overview about Sitecore caching
http://sitecorebasics.wordpress.com/2011/03/05/sitecore-caching/
There is another tool that is also incredibly helpful for investigating what's being cached. It's on the Marketplace and is called "Cache Admin":
https://marketplace.sitecore.net/Modules/Sitecore_Cache_Admin.aspx?sc_lang=en
We have an Azure web site with a daily scheduled job. In our case, the scheduled job runs a stored procedure that takes about 10 minutes so there is no local processing. Our web job is terminating after about 4 minutes with this error.
Command 'cmd /c ...' aborted due to no output and CPU activity for 121 seconds.
You may increase SCM_COMMAND_IDLE_TIMEOUT setting to solve the issue.
We've tried adding the following app settings to the web job's app.config file:
<appSettings>
<add key="SCM_COMMAND_IDLE_TIMEOUT" value="100000" />
<add key="WEBJOBS_IDLE_TIMEOUT" value="100000" />
</appSettings>
Those files are referenced in this document https://github.com/projectkudu/kudu/wiki/Web-jobs but they don't seem to have any effect. (still timing out after adding the settings to the app.config file)
Are we adding the configuration settings to the right place?
Thanks for the help.
Login to Microsoft Azure portal
Go to App Services,
Select your website
Go to settings --> Application settings tab
Create a key “WEBJOBS_IDLE_TIMEOUT” under App settings section
Save
You need to set SCM_COMMAND_IDLE_TIMEOUT from the portal to your desired timeout value in seconds. For example, set it to 3600 for a one hour timeout.
Go to your website's config section, find the app settings section, and add the setting.
As this is the first stack overflow error that comes up when searching for the timeout problem i want to update it from my perspective;
If expecting a CONTINUOUS webjob, this isn't something that happens by default (Even though the webjob appears to run by the rules until timeout). This is something that has to be selected in the Visual Studio Publish properties as detailed here:
https://learn.microsoft.com/en-us/azure/app-service/webjobs-dotnet-deploy-vs
Once continuous is selected and the webjob is published, this error goes away
I'm working on creating a scorm package (2004 3rd Edition) that has several pages within it. I'm creating a home page that lets you choose which item to navigate to. However, I'm running into the issue that no form of javascript navigation will work to change to any page.
Using this package example (manifest only) from the scorm site I've done some testing. According to the manifest choice mode is enabled.
<imsss:controlMode choice="true" flow="true"/>
However, whenever I go to the etiquette page then get the API object and attempt any form of navigation, it fails.
API.GetValue("adl.nav.request_valid.choice.{target=playing_item}");
API.SetValue("adl.nav.request", "{target=playing_item}choice");
After setting the adl.nav.request then the Terminate("") call fails. The diagnostic is:
"Failure calling the Terminate remote callback: the server replied with HTTP Status <div class="notifyproblem">Target Activity does not exist or is unavailable</div>true"
Choice mode is enabled, but this rule is likely overriding it.
<!--
'Disabled' will cause the SCO to be visible in the course tree, but not accessible via choice or flow.
-->
<imsss:ruleAction action="disabled"/>
Why not try this feature out with this simple golf example first?
http://scorm.com/wp-content/assets/golf_examples/PIFS/RuntimeMinimumCalls_SCORM20043rdEdition.zip
We have limit on number of concurrent sitecore users. We are facing a unique issue, where sitecore is creating a new session when user is trying to upload an image from Medial Library. Due to this we are reaching our license limit quickly and someone has to manually kick user session using sitecore/shell/Applications/Login/Users/kick.aspx page.
Any help would be highly appreciated.
We are using Sitecore 6.4.1
Thanks,
I've been here too. This is a known issue fixed in CMS 6.4.1 rev. 110928 (6.4.1 Update-4). :
"Multi-browser support
[Firefox, Chrome and Safari] When using the Flash-based upload, a new Sitecore user session would be registered for each upload, causing the number of concurrent user sessions to grow unexpectedly. (344158)"
http://sdn.sitecore.net/Products/Sitecore%20V5/Sitecore%20CMS%206/ReleaseNotes/ChangeLog.aspx
As the issue is with the flash-based uploader, the quick work-around is to enable the classic media uploader instead which will not invoke a new session.
In web.config :
<!-- UPLOAD CLASSIC
Indicates if uploading runs in classic (no flash) mode.
Default: false
-->
<setting name="Upload.Classic" value="true" />