With Google Analytics you can download a program so Google knows when you go to your own site and does not track those stats but I can't find any settings for Azure Application Insights to do the same. I have been able to modify my web.config file so that the HTTP Modules are only configured when deployed to production preventing the stats from getting skewed by debugging but when I go to my live site I am not sure how to get my browsing stats to be ignored. Can anyone tell me how to do this?
There is no built-in functionality for that.
You can try this:
If your application uses some authentication create telemetry initializer that would assign context.user.id (instead of telemetry initializer that AI adds for tracking anonymous users). Then in the portal you can create a chart that would filter out you as a user. You would need to save this chart in favourites so customization is saved.(http://www.apmtips.com/blog/2014/12/01/telemetry-initializers/)
Same idea: add some custom properties on the base of something, e.g. start collecting ip or add some query string parameters in custom properties. Then create a chart that will filter that out.
Related
I've built an app in App Maker and deployed it, but the user I thought I had given permission to is getting this notification "Sorry, you don't have access to this application."
In the app, I added a role to the data source and added the user to the role from the deployment. I also added the role to each page's security. I verified that App Maker is turned on for all of our users. I've ensured that the user has access to the Google Sheet data tables (both what I imported into the App for preview and the data I exported from the deployment). I've even added the user as a Cloud Sql Viewer in our Cloud SQL instance (don't know if that was necessary). This is my first app and I feel like I'm flying blind. I'm obviously missing something but can't figure out what. Any help is much appreciated!
Make sure all the required models can be accessed by the role you assigned to the user.
If the user has another Google account in the same Chrome session, the browser may be switching them to this external user when opening the app. Sign-out from that account or try incognito.
Make sure the deployment has no restriction as shown here; or if it does, allow the username.
I am trying to optimize my app and have been using the profiler you get with app_dev to be very useful, especially the doctrine panel.
Is there any way to log this information to a file so I can see what is happening when I POST / PUT to a RESTful controller?
When you using development enviorment (app_dev.php) profiler works independend of the fact of displaying toolbar unless you force to disable it via config.
You can view all the profile data after successfull or failed request via http://your.app.address/_profiler/
If it is not enough there is a way to
Change profile storage engine
Access profile during local tests
I have a web application on a public facing web site that requires a username and password to log into. Users log in from locations in many different countries and depending on their login location different settings are applied.
Certain users have asked for integration from this web application to another running on the same machine as they are using. They require an XML file to be saved down to a specific folder whenever a transaction occurs on the web application. They don't want the user to have to click any button or have a save dialog appear.
Obviously this is not possible using normal browser functionality for security reasons. What I want to know is this: is it possible to write some application or service that runs on those users' computers that could somehow take the transaction information from the browser and generate the file? I can modify the web application to know when it needs to do this so there can be work on both ends.
One way of doing this that I was thinking of was to have a web service running locally on all PCs where this is required, and the application will call this service when required.(e.g. a localhost url that would be setup on all required pcs ) Has anybody any other suggestions?
I’m not an expert on programming but I don’t think that would be possible. It would create a security risk and if it were possible then anyone could have it download a virus to your computer.
It is said you cannot create apps automatically with the current facebook API.
Create and Configure Facebook Apps via API
How to programatically create a Facebook application via JS SDK or Open Graph API? (createApplication)
Yet woobox.com does it.
I have created a few photo contests in their portal. It didn't ask for extra permission. No dialogs showed up. I just got these links:
http://www.facebook.com/pages/-/105892812908965?sk=app_422118604517529&app_data=dlt-1
http://www.facebook.com/pages/-/105892812908965?sk=app_451684954848385&app_data=dlt-1
How did they create these apps?
app_422118604517529
app_451684954848385
I would expect
www.facebook.com/pages/-/105892812908965?sk=app_SAME_APP_ID&app_data=WOOBOX_ID_1
www.facebook.com/pages/-/105892812908965?sk=app_SAME_APP_ID&app_data=WOOBOX_ID_2
You are correct with the presumptions that Facebook apps/users/groups and pages can't be created dynamically. What woo box is what many other page tab applications are doing. They create a number of applications for different templates and then customize them according to your inputs. They don't create apps dynamically. And these dynamic apps get their required data from app_data field.
Another point to note is
An app can't be installed on a page twice
that is why many Service provider that provide page tab applications maintain a pool of applications to fulfill their user's desires.
I have been Googling a problem that I have with trying to integrate the web application that I am working on with SharePoint 2010.
The web application is a wiki style tool that allows users to log in via forms authentication or WIA against Active Directory and create content for themselves and others.
What we would like to do is to allow a user have a page with the content they have created in our web application mixed in with content that they have living on the SharePoint server. For example, they may want to see a list of documents that they have on the SharePoint server mixed in with some of their content.
To accomplish this, we would like to take the credentials the user has logged into our web application with (for example MYDOMAIN\jsmith) and be able to query SharePoint for the documents of that same user (MYDOMAIN\jsmith) WITHOUT the user being prompted to re-enter their credentials to access the SharePoint server (we are trying to avoid the double-hop problem)
We have come up with some options for how we want to do this, but we are unsure of what the best approach is.
For example, we could
- Have a global user, shared by all users to get information we need from SharePoint. The downside is that we cannot filter SharePoint content to a particular user
- We could store the users credentials when they log in, but that would only work for users authenticating via forms auth and would be a security issue that some users/clients would not like
- Writing a SharePoint extension using WCF to allow us to access the information we need, however we'd still have the issue of figuring out how to impersonate the user we want.
Neither of these options are ideal and in our investigation we came across the Claims Authentication/STS option which seems like it is trying to solve the problem we are having.
So my question is, based on what I have written, is Claims/STS the best approach for us? We have not been able to find much direction on how to use this method to call into SharePoint from a Web Application and pass along the existing credentials.
Does anyone have any experience with any of these issues?
It sounds like you may be overcomplicating the problem. The reason that the user gets asked for credentials twice is that the two parts of the system are on different servers. The easiest solution is probably to implement your custom web app as custom pages/web parts within SharePoint.
If that isn't an option, a smaller amount of code on the SharePoint server (maybe a custom web service) should give you a few more options for impersonating a particular user.