Skip to content
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.

Sign up for GitHub

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

Jump to bottom

HPCC-32208 Properly report Grafana LogAccess Config problem #18853

Merged
merged 1 commit into from
Jul 17, 2024
Merged

HPCC-32208 Properly report Grafana LogAccess Config problem #18853

merged 1 commit into from
Jul 17, 2024

Conversation

rpastrana
Copy link
Member

@rpastrana rpastrana commented Jul 3, 2024 •
edited
Loading

  • Tracks and reports invalid config issue

Type of change:

  • This change is a bug fix (non-breaking change which fixes an issue).
  • This change is a new feature (non-breaking change which adds functionality).
  • This change improves the code (refactor or other change that does not change the functionality)
  • This change fixes warnings (the fix does not alter the functionality or the generated code)
  • This change is a breaking change (fix or feature that will cause existing behavior to change).
  • This change alters the query API (existing queries will have to be recompiled)

Checklist:

  • My code follows the code style of this project.
    • My code does not create any new warnings from compiler, build system, or lint.
  • The commit message is properly formatted and free of typos.
    • The commit message title makes sense in a changelog, by itself.
    • The commit is signed.
  • My change requires a change to the documentation.
    • I have updated the documentation accordingly, or...
    • I have created a JIRA ticket to update the documentation.
    • Any new interfaces or exported functions are appropriately commented.
  • I have read the CONTRIBUTORS document.
  • The change has been fully tested:
    • I have added tests to cover my changes.
    • All new and existing tests passed.
    • I have checked that this change does not introduce memory leaks.
    • I have used Valgrind or similar tools to check for potential issues.
  • I have given due consideration to all of the following potential concerns:
    • Scalability
    • Performance
    • Security
    • Thread-safety
    • Cloud-compatibility
    • Premature optimization
    • Existing deployed queries will not be broken
    • This change fixes the problem, not just the symptom
    • The target branch of this pull request is appropriate for such a change.
  • There are no similar instances of the same problem that should be addressed
    • I have addressed them here
    • I have raised JIRA issues to address them separately
  • This is a user interface / front-end modification
    • I have tested my changes in multiple modern browsers
    • The component(s) render as expected

Smoketest:

  • Send notifications about my Pull Request position in Smoketest queue.
  • Test my draft Pull Request.

Testing:

@github-actions GitHub Actions
Copy link

github-actions bot commented Jul 3, 2024

Jira Issue: https://hpccsystems.atlassian.net//browse/HPCC-32208

Jirabot Action Result:
Workflow Transition: Merge Pending
Updated PR
Assigning user: [email protected]

@rpastrana rpastrana requested a review from ghalliday July 3, 2024 21:00
ghalliday
ghalliday reviewed Jul 10, 2024
View reviewed changes
Copy link
Member

@ghalliday ghalliday left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rpastrana looks good. One question.

system/logaccess/Grafana/CurlClient/GrafanaCurlClient.cpp Outdated
catch(IException * e)
{
StringBuffer description;
IERRLOG("%s: datasource exception: (%d) - %s", COMPONENT_NAME, e->errorCode(), e->errorMessage(description).str());
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be an OERRLOG? Same for line 756?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given the below definitions, yes, OERRLOG is correct.

  • (ii) Messages for SysAdmins: *
  •    OERRLOG([LogMsgCode,] format,..)     - uses MCoperatorError                   *

  •                                                                                  *
  • (iii) Messages for platform developers: *
  •    IERRLOG([LogMsgCode,] format,..)     - uses MCdebugError

@rpastrana rpastrana requested a review from ghalliday July 11, 2024 16:54
ghalliday
ghalliday approved these changes Jul 16, 2024
View reviewed changes
Copy link
Member

@ghalliday ghalliday left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Please squash

@rpastrana
HPCC-32208 Properly report Grafana LogAccess Config problem
b5d2a39 
- Tracks and reports invalid config issue
- Routes config err messages to operators
- Cleans up error message wording

Signed-off-by: Rodrigo Pastrana <[email protected]>
@rpastrana rpastrana force-pushed the HPCC-32208-GrafanaFailureHandling branch from 753a1f9 to b5d2a39 Compare July 16, 2024 14:12
@rpastrana
Copy link
Member Author

@ghalliday squashed

@ghalliday ghalliday merged commit a44d51e into hpcc-systems:candidate-9.6.x Jul 17, 2024
49 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ghalliday ghalliday ghalliday approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@rpastrana @ghalliday