You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/plugins/logging/gelf.md
+59-21Lines changed: 59 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,8 +11,6 @@ Graylog is a great option for Developers. We find that there are generally 2 cat
11
11
12
12
## Setup
13
13
14
-
15
-
16
14
## Local Debugging
17
15
18
16
Below is a sample docker file. You can use this to create a local Graylog stack using the [Graylog Docker image](https://hub.docker.com/r/graylog/graylog/). This can be useful for testing application logs locally. Requires [Docker](https://www.docker.com/get-docker) and Docker Compose.
@@ -22,37 +20,77 @@ Below is a sample docker file. You can use this to create a local Graylog stack
22
20
- Credentials: admin/admin
23
21
- Create a UDP input on port 12201 and set `GelfLoggerOptions.Host` to `localhost`.
24
22
23
+
> [!NOTE]
24
+
> The username and password are both `admin`. This should only be used for local testing. If putting this into production be sure to update the password.
Copy file name to clipboardExpand all lines: docs/plugins/logging/raygun.md
+3-5Lines changed: 3 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,8 +19,6 @@ Raygun offers a free Open Source version for Crash Detection that can be run in
19
19
To get started you can copy the following docker compose sample. You can set the localpath for the volumes to persist the crash data over time and ensure that the downloaded Ollama models are persisted and do not need to be downloaded again.
20
20
21
21
```docker
22
-
version: '3.8'
23
-
24
22
services:
25
23
raygun-aspire-portal:
26
24
image: raygunowner/raygun-aspire-portal:latest
@@ -31,7 +29,7 @@ services:
31
29
- "8080:8080"
32
30
restart: always
33
31
volumes:
34
-
- /localpath/raygun/errors:/app/raygun/errors
32
+
- /docker/raygun/data/errors:/app/raygun/errors
35
33
depends_on:
36
34
- ollama-service # Ensure Ollama service starts before this container
37
35
@@ -40,7 +38,7 @@ services:
40
38
container_name: ollama_local_aier
41
39
restart: always
42
40
volumes:
43
-
- /localpath/ollama:/root/.ollama # Mount local directory to container for data persistence
41
+
- /docker/raygun/data/ollama:/root/.ollama # Mount local directory to container for data persistence
44
42
```
45
43
46
44
To use Raygun for local development with your Docker image, you can use the special extension as shown below:
The Raygun Implementation of the Logger makes reference to the [Prism.Plugin.Essentials](xref:Plugins.Essentials.GettingStarted) library. This allows us to dynamically check if various Essentials interfaces have been registered. If they have we automatically tailor the Logger to include offline support with request caching. Additionally we will automatically update the configuration to make use of the [Application Context](xref:Plugins.Essentials.AppContext) from Essentials.
53
+
The Raygun Implementation of the Logger makes reference to the [Prism.Plugin.Essentials](xref:Plugins.Essentials.GettingStarted) library. This allows us to dynamically check if various Essentials interfaces have been registered. If they have we automatically tailor the Logger to include offline support with request caching. Additionally we will automatically update the configuration to make use of the [Application Context](xref:Plugins.Essentials.AppContext) from Essentials. In order to enable sending logs in the background with the offline store, be sure to Register Prism.Plugin.Essentials first.
0 commit comments