Recently my jobs logs in a job details view are full of entries such as:
"Worker configuration: [machine-type] in [zone]."
Jobs themselves seem to work fine, but these entries didn't show up before and I am worried I won't be able to spot meaningful log entries because of it.
Is it something I should be worried about? Do you know how to get rid of them?
Yes, those logs are spammy and are not to be worried about. I have submitted an internal bug to reduce these spammy logs (with this being the first). While it is being fixed, you can familiarize yourself with the Stackdriver Logs Exclusion feature. This allows you to create filters to exclude logs based on a user-defined query.
Here are the steps to exclude specific Datawflow logs:
Navigate to the logs ingestion page
Find the "Dataflow Step" row
Click the right-most button on the same row
Select the "Create Exclusion Filter..." option from the drop-down
Write the query to select which logs you want to exclude
(in your case: resource.type="dataflow_step" "Worker configuration")
Name your filter
Select your percent of logs to exclude (exclude 100% of selected logs is the default)
Click the "Create Exclusion" button
You can view your created exclusion filter in the "Exclusions" tab in the logs ingestion page
And you should not see such logs spamming for newly scheduled jobs now! We've added logic to prevent excessive logging of this kind of message.
Related
How can I (force) stop receiving the Sumo Logic alerts?
I have scheduled a Sumo Logic search, and started receiving the email alerts. However, after I unscheduled it (Run frequency = "Never") and even deleted it, I'm still receiving these alerts. It's been over 24 hours now.
I am looking at our org's "Library"; that's where I deleted the scheduled search. Is there anywhere else I can look to see why it's still running?
You may have multiple copies of the same query.
When you receive Alert email, it includes a link to query. Open the link and then “Edit” it, then change schedule to “Never”
With the help of Sumologic Support, I got to the bottom of this.
In short, I had saved my scheduled search elsewhere (duplicating it) by mistake, and it was this other instance (of which I was unaware) that was sending the alerts.
Looking back, this is where it had gone wrong:
first, I created a scheduled search by running a Sumo search and clicking "Save As"; I saved it to a team folder, where it really belonged
some time later, I must have run the query again and clicked "Save As" again
this is wrong; after a query is saved once, it should be modified via the "Edit" link, not "Save As"
what's worse, the "Save As" dialog offers my personal folder as the default save location, and I must have overlooked it, thus producing a copy of my scheduled search
at this point, I had two identical searches scheduled: one in the team folder, and one in my personal folder (which I didn't know about); no matter how I modified the scheduled search in the team folder, even deleting it, I never stopped being alerted (because the other search was still active)
I recommend using Sumologic Support; they accessed my account, looked around, and quickly figured out what was wrong.
I'm using Dataflow with a project with many users, and would like to be able to understand when jobs are created and by whom. Similarly, if a job is cancelled, I'd like to confirm the identity of the initiator of this action.
Google Cloud Platform records these events in a per-service audit log, which is viewable both in the Cloud Logging UI as well as the Activity section. To view an event in Activity, navigate to that page and view the relevant entry, as below:
To view an event in the Log Viewer, go to the Logging page and select 'Dataflow' and 'activity', which should filter results to the structured audit log entries. This will contain more information than the Activity entry, and can be exported to Pub/Sub as well:
i want to count how many issues are in status open, and in verify (our custom flow) per day.
if today 3 issues entered into status open, and 3 entered into status verify i would like to see the result of that field saying 6.
now sure how the script should be done in SCRIPT RUNNER.
thanks guys =)
It would help if you could tell what you want to solve. JIRA allows you to define filters, that will give all the time as result a list of issues found. You can then define / use reports and / or gadgets on dashboards to display the data based on those filters.
So a solution could be:
Define a filter that searches for the issues. Something like project = XYZ AND status in (open, verify).
Save that filter under a name (e.g. "Open and verified").
Use that filter then in a gadget that displays the issues as chart, ...
Problem
In jenkins, I cannot find the job creator for a specific task.
Tries
I tried looking in the changes log, do not display creation. Looked up in the user profiles and there is no such properties. Been fooling aroung for a while now trying to find it. Also most research on google with keyword "creator" will fetch results about how to create a job or other questions of people who searched things relative to this topic.
The JobConfigHistory Plugin is ought to display a column User. And so does it in my Jenkins (v1.609.1) when I select a job's Job Config History at the bottom of the sidebar menu immediately after creating a job.
(Though I agree: There's no Created there, just Changed. But, changing from non-existence to existence is a change, isn't it? ;-)
I am the SharePoint administrator for a company. Usually I can find how to fix problems rather easily but this time I am stumped. I have two problems. One of them is there is a person who has a MySite but when you use the people search she does not show up. The second problem is there is another whose job does not show correctly and when you search by job it doesn't show correctly. Its missing one word in the job title. To update profiles we use a data base that stores there information and sends it to a intermediate database when a specific job is run. We use AD groups to determine who gets a MySite.