Keep up with Control D analytics log activity
Bring selected profile log entries into a regular review instead of searching for them manually.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get Profile Analytics Logs
Tool to list analytics log entries for a given profile. Use after confirming profile ID and optional date filters to fetch logs.
Why this helps
Log review gets pushed aside when it means remembering a profile, date filter, and separate analytics screen.
- Make log review a repeatable task
- Keep attention on a specified profile and date window
- Summarize returned entries for faster scanning
Setup
Build it in a few focused steps.
- 1Connect Control D once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel to create one.
- 3Give Notis one instruction to retrieve analytics logs for a chosen profile and date filter, then summarize entries without inferring unavailable context.
- 4Pick a recurring schedule trigger and choose where run reports should go.
- 5Test with one profile and date filter that returns log entries.
Questions about this workflow
What does the schedule control?
The schedule controls when the workflow runs. Specify the profile and date filter for the analytics log request in the instruction.
Will the report explain the cause of each event?
It can summarize the returned log details, but it should not infer causes or context that the logs do not provide.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Control d. A trigger fires from one place; an action lands in another.
Jira triggers
Control d actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Device by ID
Tool to delete a Control-D device. Use when you need to remove a device by its identifier after confirming the device_id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Profile by ID
Tool to delete a profile. Use when you need to remove a profile by its ID after ensuring it is not enforced by any device.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Delete Profile Rule by Hostname
Tool to delete a specific custom rule by hostname from a profile. Use after confirming profile_id and hostname.
New Project
Triggered when a new project is added in Jira
Delete Profile Rule by Rule ID
Tool to delete a specific custom rule by its ID within a profile. Use after confirming profile_id and rule_id.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Delete Profile Rule in Folder
Tool to delete a specific custom rule within a folder. Use after confirming profile_id, rule_id, and folder_id.
Delete Profile Schedule
Tool to delete a specific schedule within a profile. Use after confirming profile_id and schedule_id.
List Known Access IPs
Tool to list known IPs associated with the account. Use when you need to retrieve recent access IPs for device resolver queries.
Get Analytics Endpoints
Tool to list analytics storage regions and their endpoints. Use after authenticating to retrieve available analytics regions.
Connect any two apps with Notis in the middle.
Jira and Control d, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Control d.