[GH-ISSUE #710] Feature: Syntax Highlighting in Request Body #511

Closed
opened 2026-02-25 23:42:43 +03:00 by kerem · 5 comments
Owner

Originally created by @rwjack on GitHub (Sep 28, 2022).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/710

Sometimes there's too much text to sift through in the Request Body of a check.

Perhaps it would be a cool feature to have some sort of syntax highlighting?

An idea is to have an option in settings for setting the default syntax (default syntax could be per check/project/account?), and also having a dropdown box to chose syntax highlighting language (bottom right of the image - in line with "Request Body")
image

Originally created by @rwjack on GitHub (Sep 28, 2022). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/710 Sometimes there's too much text to sift through in the Request Body of a check. Perhaps it would be a cool feature to have some sort of syntax highlighting? An idea is to have an option in settings for setting the default syntax (default syntax could be per check/project/account?), and also having a dropdown box to chose syntax highlighting language (bottom right of the image - in line with "Request Body") ![image](https://user-images.githubusercontent.com/59068073/192877835-83dc776f-51fe-4beb-8563-560886f765d9.png)
kerem closed this issue 2026-02-25 23:42:43 +03:00
Author
Owner

@cuu508 commented on GitHub (Oct 4, 2022):

Hi @rwjack, what syntax formats do you have in mind? JSON, XML, something like that?

<!-- gh-comment-id:1266932902 --> @cuu508 commented on GitHub (Oct 4, 2022): Hi @rwjack, what syntax formats do you have in mind? JSON, XML, something like that?
Author
Owner

@rwjack commented on GitHub (Oct 19, 2022):

Yeah I'm trying real hard, but I can't seem to remember where I was going this idea.

Anyways, most of my output isn't syntax, it's just basic echo commands with text, so not sure how highlighting that would work.

Is there some sort of standard for text output highlighting? Like "Logging syntax" or something?

In that case - to solve this idea:

  • users could modify their scripts to use a logging standard
  • healthchecks could have an option to highlight that type of logging syntax (also including options for JSON, XML, YAML - basically the most commonly used output languages)
<!-- gh-comment-id:1283666099 --> @rwjack commented on GitHub (Oct 19, 2022): Yeah I'm trying real hard, but I can't seem to remember where I was going this idea. Anyways, most of my output isn't syntax, it's just basic echo commands with text, so not sure how highlighting that would work. Is there some sort of standard for text output highlighting? Like "Logging syntax" or something? In that case - to solve this idea: - users could modify their scripts to use a logging standard - healthchecks could have an option to highlight that type of logging syntax (also including options for JSON, XML, YAML - basically the most commonly used output languages)
Author
Owner

@cuu508 commented on GitHub (Oct 19, 2022):

Anyways, most of my output isn't syntax, it's just basic echo commands with text, so not sure how highlighting that would work.

yeah, there are many log format standards. Users often define their own custom log formats. Command outputs sometimes mix logs from different sources, using different formats.

Sometimes there's too much text to sift through in the Request Body of a check.

In the "Ping details" dialog there is a "Download Original" link. Users can use it to download the body, and load it in their preferred log viewer, reformat it for readability, apply syntax highlighting, search in the document etc.

I suppose we could apply syntax highlighting in specific cases, for example if the ping body looks like JSON or JSON fragment. But I would first need to see clear demand – at least a few people saying "yes, I want that very much, it would be a game-changer, I'd be even happy to pay for that".

<!-- gh-comment-id:1284019898 --> @cuu508 commented on GitHub (Oct 19, 2022): > Anyways, most of my output isn't syntax, it's just basic echo commands with text, so not sure how highlighting that would work. yeah, there are many log format standards. Users often define their own custom log formats. Command outputs sometimes mix logs from different sources, using different formats. > Sometimes there's too much text to sift through in the Request Body of a check. In the "Ping details" dialog there is a "Download Original" link. Users can use it to download the body, and load it in their preferred log viewer, reformat it for readability, apply syntax highlighting, search in the document etc. I suppose we could apply syntax highlighting in specific cases, for example if the ping body looks like JSON or JSON fragment. But I would first need to see clear demand – at least a few people saying "yes, I want that very much, it would be a game-changer, I'd be even happy to pay for that".
Author
Owner

@rwjack commented on GitHub (Oct 19, 2022):

at least a few people saying "yes, I want that very much, it would be a game-changer, I'd be even happy to pay for that".

Sure, absolutely understandable

<!-- gh-comment-id:1284027419 --> @rwjack commented on GitHub (Oct 19, 2022): > at least a few people saying "yes, I want that very much, it would be a game-changer, I'd be even happy to pay for that". Sure, absolutely understandable
Author
Owner

@rwjack commented on GitHub (Nov 29, 2022):

@cuu508 Hey, I think I remembered why I opened this initially.

It's because I use runitor + healthchecks + ansible as an alternative to ansible tower, so I usually have ansible-syntax type output in my checks.

ansible + terminal = syntax highlighted

ansible + terminal + runitor = no highlighting

Since most of the jobs run as cron, there is no need to push for runitor to show the colors of the program it's running (though it would be a nice feature), but it would be great if healthchecks would color code the output somehow.

Let me know what you think!

<!-- gh-comment-id:1330432455 --> @rwjack commented on GitHub (Nov 29, 2022): @cuu508 Hey, I think I remembered why I opened this initially. It's because I use runitor + healthchecks + ansible as an alternative to ansible tower, so I usually have ansible-syntax type output in my checks. ansible + terminal = syntax highlighted ansible + terminal + runitor = no highlighting Since most of the jobs run as cron, there is no need to push for runitor to show the colors of the program it's running (though it would be a nice feature), but it would be great if healthchecks would color code the output somehow. Let me know what you think!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/healthchecks#511
No description provided.