From 3e8d87632c34e4d3c5a85fbd1ffae5a23b3c3e91 Mon Sep 17 00:00:00 2001 From: Reinhard Pilz Date: Sun, 28 Jan 2018 22:18:58 -0800 Subject: [PATCH] First checking all problems --- .../04-problem-processes/README.md | 8 ++ .../problem-process-map.html | 114 ++++++++++++++++++ .../01-topology-services/README.md | 10 ++ .../01-topology-services/service-map.html | 89 ++++++++++++++ .../02-topology-service-tagging/README.md | 7 ++ .../service-tagging.html | 95 +++++++++++++++ .../03-topology-processes/README.md | 9 ++ .../03-topology-processes/process-map.html | 89 ++++++++++++++ problem-api/README.md | 0 9 files changed, 421 insertions(+) create mode 100644 perform-problem-api/04-problem-processes/README.md create mode 100644 perform-problem-api/04-problem-processes/problem-process-map.html create mode 100644 perform-topology-api/01-topology-services/README.md create mode 100644 perform-topology-api/01-topology-services/service-map.html create mode 100644 perform-topology-api/02-topology-service-tagging/README.md create mode 100644 perform-topology-api/02-topology-service-tagging/service-tagging.html create mode 100644 perform-topology-api/03-topology-processes/README.md create mode 100644 perform-topology-api/03-topology-processes/process-map.html delete mode 100644 problem-api/README.md diff --git a/perform-problem-api/04-problem-processes/README.md b/perform-problem-api/04-problem-processes/README.md new file mode 100644 index 0000000..ada7ede --- /dev/null +++ b/perform-problem-api/04-problem-processes/README.md @@ -0,0 +1,8 @@ +Perform 2018 - Sample 4 + +This example is an extension of [Sample 3](../../perform-topology-api/03-topology-processes). + +Processes involved in ongoing (and for simplicity reasons also resolved) problems are colored in red. +The Dynatrace Problem API publishes the necessary REST calls that allow for querying for the problem feed, problem details and eventually the events containing the entities involved in the problem. + +To use this example with your own Dynatrace environment, just replace the placeholder with your own environment id and API key. \ No newline at end of file diff --git a/perform-problem-api/04-problem-processes/problem-process-map.html b/perform-problem-api/04-problem-processes/problem-process-map.html new file mode 100644 index 0000000..17d5c18 --- /dev/null +++ b/perform-problem-api/04-problem-processes/problem-process-map.html @@ -0,0 +1,114 @@ + + + + + + + + +
+ +
+
+ \ No newline at end of file diff --git a/perform-topology-api/01-topology-services/README.md b/perform-topology-api/01-topology-services/README.md new file mode 100644 index 0000000..221838b --- /dev/null +++ b/perform-topology-api/01-topology-services/README.md @@ -0,0 +1,10 @@ +Perform 2018 - Sample 1 + +This example is a slightly modified version of the [topology-smartscape](https://github.com/Dynatrace/dynatrace-api/tree/master/topology-smartscape) example. + +It represents a base solution that is able to visualize a service map. The required data is getting queried from via Dynatrace Topology and Smartscape API via REST Calls. +Visualization is taken care of by Sigma.js. + +Clicking on one of the nodes creates an alert box. + +To use this example with your own Dynatrace environment, just replace the placeholder with your own environment id and API key. \ No newline at end of file diff --git a/perform-topology-api/01-topology-services/service-map.html b/perform-topology-api/01-topology-services/service-map.html new file mode 100644 index 0000000..2fa65b5 --- /dev/null +++ b/perform-topology-api/01-topology-services/service-map.html @@ -0,0 +1,89 @@ + + + + + + + + +
+ +
+
+ \ No newline at end of file diff --git a/perform-topology-api/02-topology-service-tagging/README.md b/perform-topology-api/02-topology-service-tagging/README.md new file mode 100644 index 0000000..9649a71 --- /dev/null +++ b/perform-topology-api/02-topology-service-tagging/README.md @@ -0,0 +1,7 @@ +Perform 2018 - Sample 2 + +This example extends [Sample 1](../01-topology-services) by adding a custom tag to the service represented by a node when clicked. + +Adding a custom tag to an entity is possible by sending a POST request via REST call to the Dynatrace Topology and Smartscape API. + +To use this example with your own Dynatrace environment, just replace the placeholder with your own environment id and API key. \ No newline at end of file diff --git a/perform-topology-api/02-topology-service-tagging/service-tagging.html b/perform-topology-api/02-topology-service-tagging/service-tagging.html new file mode 100644 index 0000000..cbab8d8 --- /dev/null +++ b/perform-topology-api/02-topology-service-tagging/service-tagging.html @@ -0,0 +1,95 @@ + + + + + + + + +
+ +
+
+ \ No newline at end of file diff --git a/perform-topology-api/03-topology-processes/README.md b/perform-topology-api/03-topology-processes/README.md new file mode 100644 index 0000000..9e4b2da --- /dev/null +++ b/perform-topology-api/03-topology-processes/README.md @@ -0,0 +1,9 @@ +Perform 2018 - Sample 3 + +This example is a modification of [Sample 2](../02-topology-service-tagging). + +Instead of Services a map of dependent processes is getting displayed. +The required data is getting queried from via Dynatrace Topology and Smartscape API via REST Calls. +Visualization is still taken care of by Sigma.js. + +To use this example with your own Dynatrace environment, just replace the placeholder with your own environment id and API key. \ No newline at end of file diff --git a/perform-topology-api/03-topology-processes/process-map.html b/perform-topology-api/03-topology-processes/process-map.html new file mode 100644 index 0000000..66b201a --- /dev/null +++ b/perform-topology-api/03-topology-processes/process-map.html @@ -0,0 +1,89 @@ + + + + + + + + +
+ +
+
+ \ No newline at end of file diff --git a/problem-api/README.md b/problem-api/README.md deleted file mode 100644 index e69de29..0000000