-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Datafactory #242
Datafactory #242
Conversation
docs/severity.md
Outdated
|
||
|Detector|Critical|Major|Minor|Warning|Info| | ||
|---|---|---|---|---|---| | ||
|Azure DataFactory Activity Rate Status|X|X|-|-|-| |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No heartbeat detector for this resource?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
most of the formula seem not correct or at least there is a useless signal in them.
I see you define Critical / Major everywhere, are you sure all detectors here are all equally important ? (and require a critical severity?).
Also you use lasting everywhere, is there really necessary / wanted ?
Can you please the detectors generation from yaml files as its easier to read and to maintain ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can also add a detector that checks the resources count against the max since metrics are available.
modules/integration_azure-datafactory/conf/01-adf-activity-run.yaml
Outdated
Show resolved
Hide resolved
modules/integration_azure-datafactory/conf/01-adf-activity-run.yaml
Outdated
Show resolved
Hide resolved
modules/integration_azure-datafactory/conf/01-adf-activity-run.yaml
Outdated
Show resolved
Hide resolved
modules/integration_azure-datafactory/conf/02-adf-pipeline-run.yaml
Outdated
Show resolved
Hide resolved
name: "adf integration available memory" | ||
filtering: "filter('resource_type', 'Microsoft.Storage/factories') and filter('primary_aggregation_type', 'true')" | ||
aggregation: ".sum(by=['azure_resource_name', 'azure_resource_group_name', 'azure_region'])" | ||
transformation: ".min(over='5m')" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems quite short since low memory is not critical for this use case.
modules/integration_azure-datafactory/conf/01-adf-activity-run.yaml
Outdated
Show resolved
Hide resolved
modules/integration_azure-datafactory/conf/02-adf-pipeline-run.yaml
Outdated
Show resolved
Hide resolved
modules/integration_azure-datafactory/conf/03-adf-trigger-run.yaml
Outdated
Show resolved
Hide resolved
5637a87
to
1ac407a
Compare
module: "Azure DataFactory" | ||
name: "activity error rate" | ||
filtering: "filter('resource_type', 'Microsoft.DataFactory/factories') and filter('primary_aggregation_type', 'true')" | ||
aggregation: ".sum(by=['name'])" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hum, is this enough? what if you have multiple pipeline with the same name il multiple rg/regions?
6248542
to
9df06c2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
overall seems good for me, see comments for requested changes including:
- useless rollup to delete
- undesirable changes out of scope (e.g. main readme)
- rename modules file
also I doubt that all percentage based detectors have the same combination of thresholds and severity but I cannot say it is up to you.
modules/integration_azure-datafactory/conf/02-adf-pipeline-run.yaml
Outdated
Show resolved
Hide resolved
modules/integration_azure-datafactory/conf/02-adf-pipeline-run.yaml
Outdated
Show resolved
Hide resolved
modules/integration_azure-datafactory/conf/03-adf-trigger-run.yaml
Outdated
Show resolved
Hide resolved
modules/integration_azure-datafactory/conf/04-adf-integration-available-memory.yaml
Outdated
Show resolved
Hide resolved
modules/integration_azure-datafactory/conf/05-adf-integration-cpu-percentage.yaml
Outdated
Show resolved
Hide resolved
modules/integration_azure-datafactory/conf/05-adf-integration-cpu-percentage.yaml
Outdated
Show resolved
Hide resolved
modules/integration_azure-datafactory/conf/05-adf-integration-cpu-percentage.yaml
Outdated
Show resolved
Hide resolved
82e7fe6
to
27d41cf
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good for me thanks
- adding datafactory v1.0 - adding rg and region filter, and some docs - updating detectors for datafactory part
adding some datafactory detectors