jeffschaper opened a new issue, #8362:
URL: https://github.com/apache/incubator-devlake/issues/8362
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
## Question
Hello! 👋
My company primarily relies on the PagerDuty data connection to provide the
stability side of DORA metrics. We'd prefer to use the ServiceNow data
connection; however, it seems like the [issue was
closed](https://github.com/apache/incubator-devlake/issues/4234). As it stands
now, the PagerDuty data connection does not have a scope config, in fact, it
appears it did at one point, but perhaps wasn't full implemented and was
removed (See [PR 5326](https://github.com/apache/incubator-devlake/pull/5326)
and [PR 5369](https://github.com/apache/incubator-devlake/pull/5369). What's
not clear to me is why the scope config was removed or why the scope config
wasn't fully implemented.
The reason why I'm asking and why a scope config could be beneficial for the
PagerDuty data connection would be to include and/or exclude certain data from
going to DevLake. As it stands now, the PagerDuty data connection seems like an
all-or-nothing solution. There doesn't seem to be a way to filter the data.
This is an issue for us because it seems to be inflating our stability metrics
with lower priority incidents. For example, my company integrates ServiceNow
with PagerDuty, but only for S3/P1 or higher. Folks also use PagerDuty to alert
teams for lower priority incidents (lower than S3/P1). Perhaps this is a
company culture issue and not so much a DevLake issue; however, it would be
nice to remedy this with a PagerDuty scope config as opposed to using webhooks
to capture the filtered data from a ServiceNow API.
## Additional context
I thought I'd start with a question as a GitHub issue, then make a formal
feature request depending on what the maintainers say.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
