We have AKV instance which stores lots of secrets. We have enabled diagnostics settings as below to push logs to LogAnalytics workspace and we can see it pushes lots of logs/metrics to workspace.
Is it possible to only push selective metrics? I want to push only logs which are related to Event notification (e.g. secrets expiry etc) so that our LA workspace doesn’t get flooded with unnecessary logs.
Appreciate your help in this regard.
There is no option to filter logs by type for log analytics.
You can filter it in log analytics workspace with query.
Related
I've read about the Unified Logging Framework as well as the new iOS 14 API regarding logging on devices, but I can't find anything that would enable me to write a log on a user's device to troubleshoot an issue, and for me to be able to review it? What is the current state of the art for doing this inside the Apple framework, or 3rd party library?
What you have read is how to write a log on the user's device. When you use os_log or the new Logger, and you log with anything but the lowest level, it is written into the log. The user can extract it using the log command in the Terminal. Of course you need to give instructions, so practice on your own device first.
For instance, if I hook my phone, TheMattPhone, to the computer, and say in the Terminal
sudo log collect --device-name "TheMattPhone" --last 1h
...then the result is that my home directory now contains a file called system_logs.logarchive. The user can zip that up and send it to you.
There are much more sophisticated commands that can extract just your app's logs, or even particular logs, depending on how you've configured the logger.
Note that the log written to the file will be redacted unless you mark interpolated material as public.
User notifications are working properly and if I configure my own user notification it works. But team notifications from TFS are not working.
From my understanding with the first image configuration, when a build in the project fails the user that requested the build should receive a notification.
Am I losing anything?
On the second image is my user configuration that works properly.
Note: "Requested by" is when the users execute the build directly in TFS and "Requested for" is when the user do an action that triggers the build.
Team notification settings
User notification settings
Check whether you have correct Delivery settings:
Finally I figure out why is not working.
The problem is I was setting the notifications at project level, as you can see in the first screenshot of the post, it was set to Develop. So I found two solutions:
1- At projects page: https://MyTfsUrl.com/tfs/MyCollection/_projects You have to select a Team in your project, so then set the notifications and the members of that team will receive the notifications.
As you can see in the image, now is selected Develop/DevOpsDev that is a team and notifications set there are working.
2- Other solution I found, and finally is the one I am using, is to set the notification at collections level on https://MyTfsUrl.com/tfs/MyCollection/_admin/_notifications?tab=Subscriptions
As I want to set notifications for a build fail. I decided that is a good option to inform the user involved in a failed build of all the projects.
For Example, I have pull replication running, which is syncing documents of user login, but whenever user entering the username and logging in, the document of the particular user is not yet synced and it is showing no user found. So how to overcome this. Please help me out.
Thanks in advance!
To find out whether all the documents are synced or not one need to start the sync in one shot mode.
In this continuous is set to false for pull replication. Push is always in continuous mode. So when the sync is started in one shot then when the replication status changes to Stopped then it means either the sync have finished or there is an error while syncing data.
In case of an error haserror() function can be used to find out if the error is there or not. If there is an error then one need to restart one shot replication else the replication can be put in continuous mode and app can be used. Do note only one shot will have a status as Stopped
following is the link where it is stated :-
https://developer.couchbase.com/documentation/mobile/1.4/guides/couchbase-lite/native-api/replication/index.html
my team is implementing gerrit on their git repositories.
We liked the way it works.
As far as I understand (please, correct me if I am wrong) once gerrit is implemented it is kind of optional. If you use refs/for at the time you push, your push is sent to gerrit for review. But if you do not use refs/for it automatically pushes the code.
My question:
Is there a way to not give the user the opportunity to push directly? I want every push to be sent to revision because sometimes the user can get to forget to add refs/for to his/her push request.
It's optional but a person need to have a "special" permission to be able to push straight to the branch (bypassing Gerrit review). Have this permission is not the default for the most people in the most of Gerrit servers. Normally only Configuration Managers or Administrators have this permission:
Reference refs/heads/* Push
If someone who doesn't have this permission pushes straight to the branch the push will fail with "Prohibited by Gerrit" error (See here for more details).
I need to check audit logs for activities done between a timeperiod on my slack account. I couldn't find any API/methods which can help me with audit logs retrieval. I need to see what all users have been added, removed or invited between a given timeframe. Any help on how this can be done?
There are of course methods to download login (team.accessLogs) and integration activity (team.integrationLogs), but they only provide a part of the functionality you asked for and the first is only available on paid tier.
However you could develop a small custom app for logging all required activity using the new Event API. With the Event API your app can subscribe to any event type you like to log. Whenever an event of that type occures Slack will send a request to your app, with detailed context information. Your app can then store this info in a file for later retrieval and analysis.
e.g. users added: https://api.slack.com/events/team_join